What is Scrum?
“Scrum” has become a new meaning and purpose in today’s professional workforce. It is a framework for getting things done, primarily in software development. Still, it has become more common in project management and other sectors such as marketing, product development, and financial services.
The Scrum methodology is based on the agile approach to project management, breaking down large projects into manageable tasks completed in short iterations. The Scrum framework emphasizes constant collaboration, allowing teams to quickly complete tasks within an allotted time and move on to the next project phase.
The word “Scrum” can be traced back to rugby, where the group mindset and teamwork inspired its use in the modern workforce. The concept was first advanced in the 1986 Harvard Business Review article “The New Product Development Game” by Hirotaka Takeuchi and Ikujiro Nonaka. Scrum was further popularized in the early 1990s by Jeff Sutherland and Ken Schwaber, who sought to expand the concept to software development.
For Scrum to be employed successfully, Sutherland and Schwaber argue that those involved must adhere to five values: commitment, focus, openness, respect, and courage. These values guide the Scrum team’s work, actions, and behavior. The authors explain that the decisions and steps taken in using Scrum should reinforce these values and not undermine them.
The Scrum framework relies on six essential principles, which must be followed throughout every project. The principles are control over the empirical process, self-organization, collaboration, value-based prioritization, time-boxing, and iterative development.
To deliver a project successfully, you must rely on the contributions of the Scrum team. Team members don’t necessarily have to come from the same department; they all have to play a role in the process. The Scrum team is not built on a hierarchy; every member is treated equally to accomplish each objective.
The Scrum Guide recommends that Scrum teams be cross-functional, smaller, and accountable. Cross-functional teams are comprised of members with the skills needed to create value who are self-organized and empowered to work independently. Smaller groups with fewer than ten people are recommended to avoid communication gaps and decreased productivity. The entire Scrum team is accountable for creating a valuable, helpful increment every Sprint.
The article is “What is Scrum?“
The Scrum framework is built on a set of principles and values that guide its implementation. Scrum is often associated with the three pillars (Transparency, Inspection, and Adaptation) and the five values (Commitment, Courage, Focus, Openness, and Respect).
| Principle | Description |
|---|---|
| Empirical Process Control | Scrum is based on the idea that knowledge comes from experience and making decisions based on observed realities. It relies on the three pillars: Transparency, Inspection, and Adaptation. |
| Self-organization | Scrum teams are self-organizing, meaning they choose how best to accomplish their work rather than being directed by others. This principle empowers the team and relies on their expertise. |
| Collaboration | Scrum employs fixed-length iterations called Sprints, which are time-boxed to a month or less. This ensures a regular delivery rhythm and provides a framework for planning and feedback. |
| Value-based Prioritization | The work is prioritized based on its value to the end-user and the business. The Product Owner maintains and prioritizes the Product Backlog to ensure maximum value delivery. |
| Time-boxing | Scrum employs fixed-length iterations called Sprints, which are time-boxed to a month or less. This ensures a regular rhythm of delivery and provides a framework for planning and feedback. |
| Iterative Development | Work is done in small, manageable chunks and is delivered iteratively. After each Sprint, a potentially shippable product increment is delivered, allowing for regular feedback and ensuring that the product remains aligned with user needs. |