When working with project managers the terms “Waterfall” and “Scrum” come up. What are they and why are they important?
Waterfall
We’re not talking about Niagara Falls – but rather a process for handling projects. Waterfall is the “typical” method for accomplishing tasks and projects. Requirements for every feature, or micro-deliverables, within a project are gathered up-front and a plan is designed. Implementations are handled in a linear manner; each feature will be delivered by the end of the project’s life. Features are not considered independent of one another and must be delivered all at once.
Pros: The client or sponsor does not need to be called upon as frequently as when using the Scrum method.
Cons: This methodology does not handle change well and is less efficient for long or complex software projects in general.
From a value-add perspective, the last 20-40 percent of a project is the most expensive.
Scrum
Using the Scrum method, projects are separated into features, placed inside a backlog, and then prioritized into sprints. Sprints are a defined length of time – some features will span multiple sprints. By handling projects in this manner, 80 percent of the value can be delivered within 20 percent of the effort. This doesn’t mean more features are completed; it means the most valuable things are done first and delivered back to the client before the entire project is completed, producing the “Minimal Viable Product,” or MVP.
This iterative process handles scope change well by checking in frequently with a client or sponsor for alignment and then adjusting what is going into the next sprint accordingly. For projects that are complex or have frequent scope changes and tight deadlines, Scrum can produce better results and at a greater speed.
Pros: Efficient, higher priorities are worked on first and scope changes are handled well.
Cons: Project goals will pivot and overall timing may change due to feedback, but a better product is delivered and typically within a faster timeframe.
Here at VPDCS
We use Agile Scrum as a framework for our development team using two week sprint cycles. Our sprints start every other Wednesday, allowing our team greater flexibility to accomplish development tasks for our clients and customers.
To learn more about Agile Scrum and its benefits, Jeff Sutherland has written an excellent book called Scrum: The Art of Doing Twice the Work in Half the Time.
Article written by:
Bryce House
Client Innovation Manager
