Tag Archives: planning
In the next edition of this blog series highlighting excerpts from our upcoming book, we will tackle the tricky subject of Technical Debt. To be honest, I had a hard time choosing a single topic from this chapter because there are so many great topics covered – Definition of Done, Planning Poker, Value Stream Mapping, the Kano Model, Velocity, the XP Planning Game – and much more in this chapter on Grooming and Planning. And it includes an interview with none other than Mike Cohn! If this post, or any of the previous ones on Roles or Requirements or our guest blog from co-author Sondra Ashmore inspire you to want to purchase the book, please visit Amazon and search on Introduction to Agile Methods.
Back to Planning and Grooming, here are the Learning Objectives for the chapter.
- Understand the elements of a product backlog and what traits lead to the strongest deliverables
- Dive into prioritization and learn different methods for understanding what is the most important feature or item to work on
- Explore estimation and the different practices and measures that are used today
- Understand story points and planning poker as ways to discern the level of effort and complexity of the user stories/requirements
- Learn the other inputs that affect the planning process, such as team velocity, definition of “done,” technical debt, and bugs/defects
- Evaluate Sprint planning and the XP planning game to learn how commitments are made and work is planned
- See how maintenance work can be incorporated into Agile teams
- Review the triple constraints model and how it is handled within the Agile framework
There are a handful of meetings that the Scrum Methodology includes as part of the cadence and this blog addresses each one and why they are important.
The first meeting is called Sprint Planning and this is a two-part meeting. The first part is where the Product Owner has the opportunity to clarify and answer questions regarding the highest priority items in the backlog. The Scrum team and Product Owner then set the Sprint Goal by deciding which stories will be included in this Sprint. This is sometimes referred to as the “What” part of the meeting when we determine what we are going to build. The second part of the meeting is for the Scrum team to discuss the individual tasks that will be required to execute the stories and any technical considerations or dependencies. This is referred to as the “How” part of the meeting when the Scrum team decides how they are going to accomplish the what. The team also usually picks the tasks that each individual is going to work on and estimates the amount of time that each task will take to complete.