Alias: Mini Waterfalls in Scrum
A Scrum team should work on only a couple of Product Backlog Items (or User Stories) at a time. Most of the work should be done in a collaborative, and not isolated, process. When starting out, many Scrum teams reinvent a waterfall style approach, affectionately called ScrummerFall or WaterAgile or WAgile, because that’s what they’re most familiar with and comfortable practicing. There are two versions of this:
One version is staggered Sprints, where the Business Analysts work one Sprint ahead of the developers and the Quality Assurance people work one behind, as illustrated here with this image by Martin Hinshelwood of Naked Agility:
The other version is where everyone pretends to work in the same Sprint but the business analysts are in the lead and QA is at the end.
Both versions lead to:
- Lack of Flexibility – changes after the business analysts kick into gear will be harder to accommodate. Worse, usability issues discovered in QA are easier to ignore than fix.
- Reduced Quality – the longer there is in delay between doing the work and finding a problem, the harder it is to fix.
- Delayed Feedback – longer work cycles for each individual item means a longer time from the start of work until the customer gives feedback.
Both these approaches are a train wreck in slow motion.
A better approach is to watch the work product and not the worker. Help the team focus on getting items to finished, not maximizing the number of stories through a pipeline.
Scrum by Example – Is Your Scrum Team a Victim of Scrummerfall?
Collaboration, Over Work in Isolation
Scrum by Example – The Story of an Incomplete Sprint
Resource Links:
Mark Levison has been helping Scrum teams and organizations with Agile, Scrum and Kanban style approaches since 2001. From certified scrum master training to custom Agile courses, he has helped well over 8,000 individuals, earning him respect and top rated reviews as one of the pioneers within the industry, as well as a raft of certifications from the ScrumAlliance. Mark has been a speaker at various Agile Conferences for more than 20 years, and is a published Scrum author with eBooks as well as articles on InfoQ.com, ScrumAlliance.org an AgileAlliance.org.
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.« Back to Glossary Index