Understanding and Apply Scrum [P4]: Scrum Events - Planning in scrum

Question 1

What is the difference between the Sprint Backlog and the Product Backlog?

Answer 1

** sprint backlog is the refined stuff that the team has committed to

** product backlog is the prioritized stuff that may need to be refined further

Question 2

Do we plan in scrum?

Answer 2

Yes - more effectively

Question 3

What is the difference between Scrum and traditional methods e.g. waterfall?

Answer 3

• Emphasis planning activity over plan in Scrum
• “plans are useless, planning is indispensable”
• we know plan is going to change - honoring the value of adapting to change over a plan

Question 4

Key aspects of planning in scrum

Answer 4

• collaborative planning in all aspects
• people own the plan
• predictions are difficult

Question 5

Explain the collaborative aspect in scrum (not in traditional approaches)

Answer 5

• collaborative - collaborative negotiation of what we want to achieve in the sprint, represented as our sprint goal, and then how are we going to do it
• Dev team create sprint backlog i.e. the refined parts
• Daily Scrum - like a daily planning session for the team - inspect and adapting plan to meet sprint goal
• sprint review - collaborate and get into for next sprint
• sprint retro - collaborative discussion on how we are working together in regards to process, tools and interactions

Question 6

Explain the “people own the plan” aspect in scrum (not in traditional approaches)

Answer 6

• team working on product, so they know the most about how to get stuff done
• requires collaboration due to accountabilities - everyone must be transparent and work together to show progress towards sprint goal

Question 7

Explain the “predictions are difficult” aspect in scrum (not in traditional approaches)

Answer 7

• Scrum is a way to reduce waste in planning - plan is out of date as soon as it is done
• make plan light weight and easy to update
• minimize time we spend analyzing things that are far in the future
• minimize super accurate estimations - false hope
• recognize inherent unpredictability - build more trust and transparency