Please enable JavaScript.
Coggle requires JavaScript to display documents.
Proving the Point ("How can you be managing risk? You don't even…
Proving the Point
"How can you be managing risk? You don't even have a risk register!"
Transparency. Artifacts are visible in scrum. Look at the product backlog - the order reflects risk, and can be inspected by anyone
Sprints. Working in sprints means that the risk is contained to two weeks.
What do MDLZ mean by "risk"?
Financial exposure
Technical risk
The biggest risk? Consumers won't buy our product...the best way to reduce risk in general is: build potentially releasable increments for users.
With Scrum, we build the it up empirically, because that's the best way to control the future in complex environments.
Within Scrum, defining what is meant by "done" is important to be in control of technical risk. This can enhance the quality and maintainability of the overall product. Technical skills, tools and improvements can be adopted in a good definition of done. The right testing, validation, documentation etc. can reduce the technical risk.
Scrum values - all have an impact on risk
Turn risks into PBIs: e.g. "Risk is that the product does not meet shelf life" into "As a team, we want to ensure that the product meets shelf life" and then prioritise it.
This was seen at the snackathon event as a "How Might We" exercise = "How might we..." + increase/decrease/maintain + description of risk"
Multi-tasking is killing our productivity
Gerald Weinberg showed that at 5 x projects, a team member loses up to 80% of their effort due to context switching (Quality Software Management: Systems Thinking, 1975)
Linking this to real life - imagine 3 tasks being run simultaneously. Weinberg predicts that there will be a 40% effort loss due to context switching. That's the equivalent of two days per week.
Imagine how much more we could get done if we organised the work differently!
Multi-tasking gets you there later
Prioritisation of portfolio is what matters
Making sure everything is resourced (in a spreadsheet) is a waste of time and encourages multi-tasking. Prioritising and then working down the list encourages unitasking.