Abstract
Normally, when we talk about sprint planning, many only consider it as a meeting to form the sprint backlog. Sometimes the backlog comes pre baked, sometimes, teams race to form the backlog in the shortest time possible, and sometimes, takes pride in it.So the “How work should be done”
Now this is actually deterrent to the scrum spirit as it expects a lot of thinking and analysis should go into the proceedings. Team should not just say yes to a backlog, rather analyse each story, technically and from a business standpoint, ask probing questions to the Product owner, identify how the work could be done, by breaking the stories into small tasks, a collaborative estimation, some form of built in design and most importantly forming the Sprint goal and the Forecast of Delivery.
Hence this session of mine is targeted towards dissecting the sprint planning in details, understand the importance of each step and how it could add value and my interpretation of the Scrum guide on the various facets of Sprint Planning.
Also the session comes with an activity on Sprint Planning. We will work on a live product backlog, analyse it, break it into task, estimate it and build the sprint backlog along with the goal and forecast , all in an interactive manner
Takeaways
- Hands on learning on effective sprint planning through activity
- An insight on the different moving parts in Sprint Planning
- Help them to organise Sprint Planning better in their real life
- Better recognition of the guidelines provided in the Scrum Guide for Sprint Planning
- Learn techniques which could add value to their team.
- Date:27/07/2019
- Time:11:00
- Event:Scrum Day @Kolkata
