full-stack agile - Sprint Planning
•
10 likes•8,709 views
A presentation by full-stack agile on Sprint Planning. What the meeting is, how it should be conducted and some tips on making it an effective scrum meeting.
Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
full-stack agile - Sprint Planning
- 1. Ashley-Christian Hardy Sprint Planning: Remember it’s a Sprint, not a Marathon
- 2. Hi, I’m Ashley-Christian Hardy In Progress… full- stackagile.com achardy@fullstackagile.com @achardypm facebook.com/ fullstackagile medium.com/@achardypm pinterest.com/achardypm instagram.com/achardypm linkedin.com/in/achardypm
- 3. Sprint Planning Sprint planning is a time-boxed meeting that is conducted at the beginning of the sprint, where the team and the product owner discusses and decides on the work that will be completed in the sprint. Generally, the meeting is split into two: What & How. What? How? The Product Owner brings a list or prioritized user stories, and explains to the team WHAT should be built. The development team then discusses how the work will be completed, by splitting the user stories into smaller tasks. Outcome = An agreed upon goal of what will be completed by the end of the sprint, and a list of task to be completed called the ‘Sprint Backlog’.
- 4. Product Backlog Capacity / Velocity Current Product Status Constraints 1. 2. What? How? Sprint Goal Sprint Backlog Input Sprint Planning Output
- 5. What are the common problems? PO dictates and deciding what work will be completed The product backlog is not healthy, prioritized or ready to be discussed At the end of the sprint, everything is in too much detail and all work is assigned No one understands what is actually meant by “done”. The meeting is too long The meeting is not engaging Some people do not have a voice Poor environment and the team do not feel support or safe No trust or respect on both sides The team does not actually understand why they do this meeting
- 6. Before the Sprint Planning Dependant on preparation & healthy Product Backlog Healthy team built on trust & respect Set time, short and importance of meeting known Consensus on how to estimate Everyone who need to be there, is there.
- 7. Length of the Meeting One-week sprint – 2 hours Two-week sprint – 4 hours One-month sprint – 8 hours Goals of the Meeting Agreed and committed sprint goal & backlog A Sprint Backlog that is able to adapt and grow Enough detail and understanding to start work on the product
- 8. Meeting Structure Breaking Down the Tasks Basic structure and agenda, who speaks and when Understanding of capacity / velocity Plan for collaborative tasks Don’t fill 100% of capacity Good understanding of the “Definition of Done” Discuss all the work to be done Don’t spend too much time estimating, use story points Don’t assign all the tasks Don’t plan for 8 hour work days
- 9. Meeting Environment Stopping the Meeting Safe environment with trust. Allot the team to self organize and be autonomous Listening and focus Lots of questions and clarifying requirements Try to use a board or tools to facilitate and prepare Its time-boxed – end it on time Have the confidence to know when is enough and start the work Reflect and review at the end to agree and commit
- 10. Thank you! Full-stackagile.com achardy@full-stackagile.com @achardypm facebook.com/ fullstackagile medium.com/@achardypm pinterest.com/achardypm instagram.com/achardypm linkedin.com/in/achardypm slideshare.net/ ashlychrstn tumblr.com/ blog/achardypm https://plus.google.com/ achardypm