Many Agile teams get some fantastic training and then go off to work wonders with their new knowledge. But all too often, the results can be like a crash diet. The team forgets the new information and reverts to old habits or falls into new bad habits.
This talk will help teams to think hard about the process of sizing: what makes it work well and how to fix it when it goes wrong.
Outline/Structure of the Experience Report
- Size the Honey-Do List
- Size common household chores using dog breeds as a scale. Lead a discussion on how experience/risk/complexity played a role in the size of the task.
- Sizing Basics
- What is sizing?
- How is sizing different from a level of effort estimate?
- What does sizing include?
- Common sizing measures
- Address the Causes of Sizing Breakdown
- Improve User Stories (acceptance criteria, appropriate scope)
- Decompose Stories into Tasks
- Include all Work
- Facilitate until the Team Adopts the Process
- New Project Challenges
- Get Creative
- Size Often to maintain a backlog of sized stories ready for Sprint Planning
- Use asynchronous communication for pre-meeting communication
- Get away from the numbers for a reset
- Rotate responsibility for sizing meeting facilitation
Provide concrete tools for Agile practitioners to leverage with their own teams to improve outcomes. Distribute tip cards with the Sizing the Honey-Do list came and sizing process reminders.
Beginning and Intermediate Agile practictioners
Prerequisites for Attendees
schedule Submitted 1 month ago
People who liked this proposal, also liked:
Joyce Carr Schwab - Adapting Agile to Plan for the UnpredictableJoyce Carr SchwabScrumMaster / Project ManagerDev Technology Group
schedule 1 month agoSold Out!
Many projects face the challenge of operating in an environment that does not have all the ingredients for Agile success. Perhaps your team works in a highly regulated environment or with a customer who is transitioning to Agile principles. How can you help your team be successful and work with Agility when faced with these challenges? This presentation addresses two challenges I've encountered and shares solutions that worked for our teams. Maybe they'll work for you!
- Managing capacity with the unpredictable nature of user support and maintenance tasks
- Adapting Sprint planning to "gates" in the development process to maximize flexibility while maintaining velocity