Risk Management

Question 1

risk adjusted backlog

Answer 1

1) focuses on where investment needs to be undertaken, based on risk
2) decreasing list of priorities from the risk calculation
3) Potential Consequence x Likelihood
4) rectify all high and significant risks

Question 2

risk burn down graphs

Answer 2

1) Risk Burndown graphs are very useful for seeing if the total project risk is increasing or decreasing over time.
2) Whether individual risks are increasing in severity over time and whether new risks are being introduced.

Question 3

risk-based spike

Answer 3

Spikes are a really good way for teams to figure out stuff that they don’t know and need to know in order to understand the complexity so that it can be properly estimated, or quoted on or simply to find out if something is technically possible or not.

Question 4

architectural spike

Answer 4

architectural spike

Question 5

Why use spike

Answer 5

1) basic research to familiarize the team with a new technology of domain
2) story may be too big to be estimated appropriately and the team may use a spike to analyze the implied behavior so they can split the story into estimable pieces.
3) story may contain significant technical risk and the team may have to do some research or protoryping to gain confidence
4) The story may contain significant functional risk, not clear how the system needs to interact with the user to achieve the benefit implied.

Question 6

Alternatives to Agile Spikes

Answer 6

1) increases the scope of possible error
2) For stories that you can’t estimate accurately, an alternative to scheduling a spike story is to provide a high estimate