Managing Products with Agility [P1]: Managing Products with Agility/Forecasting and Release Planning - Scrum Myths: There is No Planning in Scrum

Question 1

Two negative consequences of believing scrum has no planning

Answer 1

1. The people in organizations responsible for budgets, product management, sales, and marketing may be unwilling to try Scrum.
2. Scrum Teams may not be effective in their use of Scrum.

Question 2

Key quote from Dwight D. Eisenhower about planning

Answer 2

Plans are useless, but planning is indispensable

Question 3

Explain the part planning plays in scrum

Answer 3

• emphasize the activity of planning over the plan itself
  
  • know plan will change and will adapt to that change
• activity of planning is collaborative
  
  • Sprint planning → collaborative negotiation to determine a valuable outcome the team wants to achieve
  • Daily Scrum → [collaborative planning session] for the Development Team to inspect progress and adapt the plan to meet the Sprint Goal
  • Review → collaborative session to gather input needed to help plan the next Sprint
  • Retro → collaborative session to enable and plan for continuous improvement
• In every Event, we are both inspecting and adapting → every sprint
• The way planning is done reduces waste
  
  • plan is out of date a minute after you discuss it → do lightweight plan
• still recognize the inherent unpredictability in complex software development
  
  • being honest about this, we can be transparent about the current progress and likely completion dates → build trust
  • enables us usean empirical process to enable[business agility], make difficult decisions and do professional work

Question 4

Some ways that we reduce waste related to planning include

Answer 4

1. We minimize time spent analyzing things that may never happen
2. We minimize time spent analyzing to an impossible level of accuracy
3. We incorporate meaningful feedback every time we plan