Multiplicity: All about Expanding your Product Line
Waterfall + Scrum = WaterScrumFall?
July 17, 2015
What happens when Waterfall and Scrum collide with each other? Out comes the WaterScrumFall.
What is WaterScrumFall?
Water-Scrum-fall is a hybrid approach to software development life cycle (SDLC) management that combines Waterfall and Agile/Scrum development methodologies.
It is used to describe a situation where a company runs their development teams in an agile (scrum) fashion with scrum ceremonies, artifacts and roles, but follows a sequential waterfall or quasi-waterfall methodology both outside of the scrum team and within the scrum team itself. In essence, it's waterfall software delivery using an incremental scrum-style release cycle rather than either a pure "big project" waterfall approach or a pure "agile prioritization" scrum approach.
WaterScrumFall presents a flexible approach that embraces both traditional and Agile development principles allows development teams to use practices and techniques best meet the needs of the problem being solved.
How does WaterScrumFall work?
Generally, a development team that uses a waterfall approach regards the development process for a software product as one large project. At the end of the project, the team releases working software to an operations team for installation and maintenance. Typically, the business owner (also called the product owner) only sees the finished product.
In contrast, a development team that uses Scrum, or some other Agile methodology, would approach the same development project as a series of very small projects called Sprints. Working software is released periodically in an iterative manner until the entire software product is complete. The project’s business owner plays an active role throughout the process and joins the development team's retrospective after each release.
Many organizations use Agile principles and Scrum communication techniques in their day-to-day product development but employ traditional waterfall methodologies for planning, budgeting or documenting the project’s progress.
Who needs to be involved?
Essentially, anyone who is a stakeholder, i.e., an individual, group, or organization, who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project.
Common team members or roles:
When is it appropriate to use WaterScrumFall?
One situation is when a company decides to transition from a traditional way of working to an agile mode, by combining Waterfall and Scrum methodologies for software development can strike a happy medium between traditional and Agile approaches. This method paves the way to a smoother transition from one to another.The Hybrid model is best suited for reusing software code, when dealing with a series of similar products and when future products must also be considered. In such situations, a quick turnaround time may be needed to keep up the pace with continual product releases. Backlog management is a critical area for successful adoption of this Hybrid model, and adoption is best assisted by software version release planning features.
Where in the organization can we apply this methodology?
The Hybrid model is best suited for reusing software code, when dealing with a series of similar products and when future products must also be considered. In such situations, a quick turnaround time may be needed to keep up the pace with continual product releases. Backlog management is a critical area for successful adoption of this Hybrid model, and adoption is best assisted by software version release planning features.
A few other instances:
Software Product Development: Planning, Design and Requirement stages (Waterfall) + Development and Testing (Scrum)
Software Application Development: Front End (Scrum) + Back End (Waterfall)
Product Development Teams: Hardware (Waterfall) + Software (Scrum)
“Planning without action is futile, action without planning is fatal.” — Cornelius Fitchner