Sprint Planning is one of five events in Scrum. It helps the Scrum Team understand the work to be performed in the Sprint.
Like every event in Scrum, Sprint Planning is all about empiricism. Its purpose is for the team to inspect the Product Backlog and to create the Sprint Backlog. The Sprint Backlog represents the plan to achieve the Spring Goal and to create a potentially releasable Increment of work.
Sprint Planning is attended by the entire Scrum Team – the Product Owner, the Development Team and the Scrum Master. The Development Team may also invite other people to attend to provide technical, domain or business subject matter expertise.
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches the Scrum Team to keep it within the time-box.
Sprint Planning answers the following:
The Product Owner can help to clarify the selected Product Backlog items and make trade-offs. If the Development Team determines it has too much or too little work, it may renegotiate the selected Product Backlog items with the Product Owner.
By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organising team to accomplish the Sprint Goal and create the anticipated Increment.
How do you write great User Stories?
Understanding the value stream’s attributes and how the enterprise serves its customers, allows us to look at ways to optimise the operational value stream. This is why measuring flow metrics such as Ability to Innovate and Time to Market based on mapping the value stream are key.
When building Agile OKRs I start with the strategy and then ask if the attribute we are measuring, increased or decreased, and by what percentage? This is why flow metrics around ability to innovate and get to market as well as customer outcomes are where I start to build my Agile OKRs.
Facilitators can use many techniques, but this does guarantee that the outcome will be reached. Ultimately linking the facilitation pattern to the objective of the interaction, makes the event more effective and helps contribute to team success in achieving their goals.
An effective Product Owner is a strategic agile product manager that ties the Product Vision into the daily work by having a product management entrepreneurial mindset.
People complain that agile has too many meetings. To be effective, agile events need to be focused, productive, collaborative with a clear purpose
Copyright © Zen Ex Machina® and ™ (2021). All rights reserved. ABN 93 153 194 220