Developing and Delivering Products Professionally [P2]: Managing Technical Risk - Manage Risk

Question 1

Comment on risk being personal

Answer 1

• Everyone interprets it differently
• Something will have a different risk level for me vs someone else

Question 2

Scrum is a way of managing ___

Answer 2

risk

Question 3

What is the best way to reduce risk in general?

Answer 3

build potentially releasable increments for customers

Question 4

Which Scrum Values apply to risk management?

Answer 4

All Scrum values!

Question 5

What are different types of risks within work related environments?

Answer 5

• Financial risk - can we pay for it?
• Business risk - will it be used? Does it solve the problem?
• Technical risk - can it be made/build? (often in relation with finance, when a product becomes possible to build, but too expensive).

Question 6

How does Scrum help manage financial risk?

Answer 6

• Project costs are hard to estimate up front
• Scrum - build up the scope, finances and resources empirically - best way to control the future in complex environments
• Clear roles and accountabilities → PO, self-managing Dev Team, SM
• Ask Devs to estimate for the first short period - short to save money if building the wrong thing
• Fund and inspect first few sprints - convos with ROI
• Once release goes out, the financial risk decreases

Question 7

How does Scrum help manage business risk?

Answer 7

• Business risk is the risk of people (users) not actually using your product, thus not solving the problem that the product needed to fix in the first place.
• Customer doesn’t know what they need
• Product Backlog refinement, requirements engineering, talking to users, doing surveys etc. doesn’t take away risk of people not actually using your product
  
  • Need one cross functional team asking
    
    • who is the customer?
    • what problem are we trying to solve?
    • is the current hypothesis for our product any good?
• PO keeps tabs on stakeholders and Devs to ensure right thing is built → business representative in the team to manage and monitor that business risk, to create the best possible outcome
• Reviewing with stakeholders every sprint and pivot or preserve from there
• COLLABORATIVE

Question 8

What two categories can technical risk be sub-divided into?

Answer 8

• Can it be built with a good ROI?
• Can we maintain the product during and afterwards?

Question 9

How does Scrum help manage technical risk?

Answer 9

• Check in with two questions everyday ^
• Communication is key
• Keep tabs on technical quality and make it better
• Clear DoD - improve quality and maintainability
  
  • includes right testing, validation, documentation etc

Question 10

Why are Scrum Values important to risk management?

Answer 10

Scrum values are extremely important to make sure that overall risk is transparent and dealt with at the right time, by the right person, with proportional effort