Scrum Framework:
What is Scrum
and how does
it work?

To answer the question, what is Scrum, simply put, Scrum is an agile method of iterative and incremental product delivery that uses frequent feedback and collaborative decision-making.¹ In fact, the Scrum Framework is a subset of the Agile project management methodology that was developed in response to the more pervasive Waterfall Methodology. It is different from the highly linear Waterfall model that focuses on planning, siloed teamwork, and forward momentum. Conversely, the Scrum Framework emphasizes flexibility and seeks to break the work up into smaller units with cross-functional teamwork. 

Scrum stays true to the Agile philosophy that collaboration is king, but markedly accelerates the process by specifically focusing on 15-minute daily meetings and working in two-week "sprints" to achieve predetermined goals. The consistent, incremental get-togethers allow team members to hash out ideas and mitigate potential problems while also enabling review of the previous day's progress.

For example, instead of long, standing weekly meetings, Agile Scrum teams often hold very short, daily stand-up meetings. Larger project tasks are divided into more urgent "sprints" with each sprint typically broken into four stages: plan, develop, deploy and evaluate.

Below are the main differences between Scrum and Waterfall.

Key differentiators between the Scrum Framework and the Waterfall Methodology include speed, flexibility, stakeholder engagement, and project complexity.

At its core, Scrum Framework is focused on getting more work done faster by splitting the project into sprints. Team members are able to save time by working on different aspects of the project simultaneously. And because clients are involved throughout the entire process, any problems that arise can be worked on as soon as they are identified.

Conversely, the Waterfall Methodology divides work into sequential stages, therefore issues are more likely to be identified in the review stage, particularly as clients are not involved in development. This can mean that the project takes longer to finish.

Scrum Framework forms nimble, cross-functional teams that have real decision-making authority. It emphasizes flexibility by focusing specifically on how people work together within and outside of an organization. Solutions evolve primarily through structured collaboration made up of smaller, engaged groups that can better take stock of evolving customer needs and adapt more quickly to changing external contexts.

Waterfall emphasizes top-down control, where a manager directs subordinates to focus on specific tasks that are isolated in silos. Project stages are planned in advance and sequential; each stage depends on the completion of the previous stage. It is better suited to projects with strict regulations or where certain preconditions must be met before further work can be carried out.

The approach to stakeholder engagement is a key consideration when it comes to Scrum vs. Waterfall. Project stakeholders and clients are consulted at every step in the project development process and their feedback can prompt changes to the project.

Conversely, with Waterfall once the end goal is established with the client, the client is not involved in the work process, apart from status check-ins or for deliverables. Additionally, because the course of the project is outlined from the start, incorporating client feedback is not included as an ongoing part of the process.

Scrum is best for more complex projects and those which may require multiple iterations, such as when the client does not have a clear final vision.¹ In contrast, Waterfall is better suited to simpler projects with a detailed outcome agreed by all parties.