Agile for Humans with Ryan Ripley and Todd Miller YDS: How Does a Scrum Team Handle Carryover Work?
7 snips
Aug 31, 2021 Explore how a Scrum team handles carryover work in a Sprint, understanding the risks and solutions. Learn about the flaws of 'plan versus actual' metric in Scrum teams and the importance of embracing emergence and sprint goals for success.
AI Snips
Chapters
Transcript
Episode notes
Don't Auto-Carry Unfinished Work
- Put unfinished sprint work back on the Product Backlog rather than auto-carrying it into the next Sprint.
- Let the Product Owner re-order and the team re-plan those items during the next Sprint Planning.
Plans Fail In Complex Work
- Long-range fixed sprint plans clash with complex product development and create phantom dependencies.
- Embrace emergence and use Scrum's inspect-and-adapt approach to reveal real priorities and risks.
Scrum Makes Reality Visible
- Scrum reveals where you truly are and what you must change by exposing work completion and impediments.
- Use that empirical information to adapt rather than force a predetermined release train.