.svg)
.svg)
Learning Scrum for the first time can be a bit overwhelming. There are a lot of new terms and concepts in Scrum, and sometimes we don’t feel confident we’re using the right words. You may find yourself asking:
How is a methodology and a framework different, and which one is Scrum?
This question is about more than just terminology; it gets at the schemas we use to organize our work. This article will cover four essential topics to help you.
- What are methodologies and frameworks?
- Outline of scrum framework
- What problem does Scrum help solve?
- What does your team or organization need?
What are methodologies and frameworks?
Today we’ll explore two terms you will hear around Scrum. You’ll learn they have a lot of similarities, but there are also some key differences. We’ll look at the definition of both a methodology and a framework and consider how they apply when practicing Scrum.
In today’s VUCA world, less and less work can be managed and performed by just following rules.
What is a methodology?
The root of the term methodology is ‘method,’ which Oxford defines as “A particular form of procedure for accomplishing or approaching something, especially a systematic or established one.” A key term in this definition is “particular form.” A methodology explicitly prescribes how to do something.
A methodology provides steps and processes, which can be helpful if the environment and work are static and predictable. It’s also beneficial if the person following the methodology is a novice and isn’t expected to make any decisions but instead just follow the rules. However, in today’s VUCA world, less and less work can be managed and performed this way.
‘Methodologies’ are typically composed of stringent and mandatory sequences of processes and procedures that implement predefined algorithms.”
-GUNTHER VERHEYEN
When practicing Scrum, your team or organization may create a methodology outlining how you will practice Scrum. But it will likely evolve as your team adapts and grows.
What is a framework
Kanban and Scrum are frameworks that help teams adhere to Agile principles and get stuff done.
A framework provides basic rules but doesn’t prescribe how to do the work. It provides principles, values, rules, and some core structure but still leaves a lot undefined.
A framework is designed to be adapted and customized to a particular situation. Think about the framing of a house; it guides where walls and some of the utilities will be, but it doesn’t predetermine how the rooms will be laid out or used. And the framing certainly doesn’t prescribe the color you paint your walls.
A framework allows you to be loose and flexible; to have ‘poetic license.’ A methodology is much more prescriptive. Both can be handy at different times.
- ANTHONY DRAFFIN
Frameworks can vary significantly in size. Two common project management frameworks are good examples of this. The Project Management Body of Knowledge (PMBOK) is 1,000+ pages, while the Scrum guide is just under 20. Both are frameworks.
A quick outline of the Scrum framework.
Scrums framework consists of its pillars, values, roles, events and artifacts.
Scrum pillars
- Transparency. How does this make things more visible?
- Inspection. Where does this create space to evaluate?
- Adaptation. When does this encourage growth?
Scrum value
- Commit to achieving the goals of the Scrum Team
- Courage to do the right thing and work on challenging problems
- Focus on the work of the Sprint and the goals of the Scrum Team
- Open about all the work and the challenges with performing the work
- Respect each other to be capable, independent people
Scrum Roles
- Development Team does the work to create value.
- Product Owner maximized the value delivered.
- Scrum Master maximizes the effectiveness of the Scrum team.
Scum Events
- Sprint Planning identifies how the team will reach the sprint goal.
- Daily Standup allows the team to inspect and adapt each day.
- Backlog Refinement brings the Scrum team together to clarify product backlog items.
- Sprint Review inspects the completed work from a sprint.
- Retrospective allows the team to reflect on and evaluate how they functioned during the sprint.
Scrum Artifacts
- Backlog contains all the prioritized PBIs for the team.
- Definition of Done establishes what must be true for something to be considered done.
- User Stories outline requirements around the end user's needs, motivations, and goals.
Related Guides
What problem does Scrum help solve?
A significant challenge you face when managing work for a team or even an individual is clarity. You need clarity about what has been done, what is being prioritized, who is doing what, and when things will be done in the future.
Let’s walk through each of these.
Clarity about what has been done.
At the end of every sprint, during the sprint review, completed work is presented to stakeholders and ready for release. If it’s not completed, it’s not presented, and the definition of done gives clear guidance about what is completed and what’s not. During the sprint, team members share what they finished the day before during the daily standup.
Clarity about what is being prioritized.
The product owner works with the whole Scrum team to refine the backlog to ensure clarity and understanding about upcoming work. All future work resides in the backlog, and the product owner is responsible for ordering it based on priority. At the beginning of a sprint, during sprint planning, the team selects how much work they can complete from the top of the backlog. The sprint is a protected time for the team to focus on completing prioritized work without adding any new work.
Clarity about who is doing what.
Every day during the sprint, the team meets for a 15-minute daily standup to plan the day. Everyone shares what they are working on, what they completed, and any obstacles they face. Two people or more may join together to accomplish something, but there is always a shared awareness of who is doing what.
Clarity about when things will be done in the future.
All work is collected in the backlog and ordered based on priority. Using story points and velocity, the product owner can predict when the team will complete items in the backlog.
Did you know Scrum applies to more than just developing code?
When you understand the essentials of Scrum and the nuance of how to apply it, you can use it to level up aspects of everyday life.
What does your team or organization need?
Given the uncertainty and change experienced today, frameworks provide a more resilient resource to your teams and organizations than methodologies.
You may develop a methodology within your organization that describes how your teams will practice Scrum or Agile. These could involve specifics to the technology or software you are using to do and track the work.
Prescribing these practices can be helpful in training and coordination at scale but proceed with caution. Once you start defining how to do things, it’s easy to just continue down that road until you find yourself with something that looks like scientific management, having removed all agency from your team members.
If you are architecting your organization’s workflow, process, or structure, you will likely be embedding various frameworks or methodologies. You will want to consider what is the least that is needed to maintain healthy agility. Think minimal viable process.
You will also want to be careful about how many different concepts must be understood by teams and leaders, as this can quickly become a tax on performance.
“Scrum replaces a programmed algorithmic approach with a heuristic one, with respect for people and thriving on the self-organizing capabilities of people to deal with unpredictability and address complex challenges.”
- GUNTHER VERHEYEN
As we bring it back to Scrum, remember Scrum doesn’t prescribe how to inspect, adapt, or make things visible. It prescribes specific meetings and roles that allow a team to have time and focus on these three areas.
Related Guides
Next steps for applying Scrum.
New methodologies and frameworks are continually developing. Understanding the basics will help you continue to learn and grow.
Action Plan
I hope this article helped you get a feel for the difference between methodologies and frameworks and how to apply both when practicing Scrum. If you want to learn more about Scrum in general, check out my What is Scrum? A Guide for Everyday People to Learn Scrum. If you have more questions, please feel free to reach out on LinkedIn.
Still not sure about your next step with Scrum? I offer a couple of free coaching sessions each month. You can signup for a free 30-minute coaching session, and we can work together to identify a good next step for you.
Frequently Asked Questions
What is Scrum?
What is the definition of scrum?
Scrum is founded on three essential pillars leading teams to ask the following questions:
- How does this make things more visible? (Transparency)
- Where does this create space to evaluate? (Inspection)
- When does this encourage growth? (Adaptation)
Further explore the definition of scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Is Scrum hard to learn?
This is because Scrum’s simplicity makes learning easy, but Scrum truly changes how you work, and that adjustment can be difficult. It changes power dynamics and expectations within the team and between the team and the rest of the organization.
You can explore further is Scrum hard to learn, along with the pros and cons of Scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
When did Scrum start?
Scrum was initially used as a term related to project management in 1986 by Hirotaka Takeuchi and Ikujiro Nonaka in their paper “New New Product Development Game” In the Harvard Business Review. The first recorded Scrum project came a little later in 1993 from Jeff Sutherland.
You can learn more about Scrum’s backstory. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
What do all the scrum words mean?
Learning Scrum for the first time can be overwhelming. There are a lot of new terms and concepts in Scrum. I’ve listed the most common terms in a Scrum glossary.
How to use Scrum
Why use Scrum?
It forces clarity and prioritization, which provides the focus necessary for teams to be effective. Scrum embraces complexity and change by keeping many things simple and iteratively evaluating and adapting.
You can learn more about why to use Scrum and three challenges Scrum solves. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
When does Scrum not work well?
Scrum isn’t always the best option for teams. Scrum can fail when there is a substantial mismatch between organizational culture and the Scrum values. It also depends on the nature of the work you do. If you work if very linear, predictable and tightly defined, you may not experience many benefits Scrum provides.
Find out more about aligning your organizational values with Scrum or how Scrum might fit in your context. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
How do I know when to use Scrum?
Scrum functions at its best when you have a dedicated team focused on developing a singular product. Its agility shines when there are time constraints combined with uncertainty.
Explore the pros and cons of Scrum along with expectations vs. realities with Scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Learning to apply Scrum
How to choose between Scrum and Kanban?
Important factors include your team size and the type of work you do. Kanban is very process-oriented, so you should consider how defined, static, or long your process is?
You can explore Scrum and other agile approaches. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
How does scrum help an organization?
Scrum forces clarity and prioritization, which are critical to organizational effectiveness. It provides a competitive edge by allowing teams to adapt as the market or priorities change. Teams operate more effectively because Scrum combines empowerment of the team members with alignment to top priorities.
Learn more about scrum’s impact on organizational culture. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Is scrum a methodology or a framework?
Scrum is more of a framework than a methodology, and it helps teams adhere to Agile principles and get stuff done. Scrum provides basic rules but doesn’t prescribe how to do the work. It provides principles, values, rules, and some core structure but still leaves a lot undefined.
Learn more about scrum as a framework. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
What’s the difference between scrum and agile?
When people say “agile,” they usually refer to it as a mindset. Scrum is a framework for how to organize people and work in an agile way. If you’re practicing Scrum, you’re working in an Agile way.
Learn more about the relationship between scrum and agile. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Scrum design
What are the three pillars of Scrum?
Scrum is founded on three essential pillars, and each leads the team to ask a critical question.
- Transparency. How does this make things more visible?
- Inspection. Where does this create space to evaluate?
- Adaptation. When does this encourage growth?
Learn how to apply the three pillars of Scrum and then explore the most common terms in a Scrum glossary.
What are the values of Scrum?
There are five values critical to the practice of Scrum: commitment, courage, focus, openness, and respect.
- Commit to achieving the goals of the Scrum Team.
- Courage to do the right thing and work on challenging problems.
- Focus on the Sprint's work and the Scrum Team's goals.
- Open about all the work and the challenges with performing the work.
- Respect each other to be capable, independent people
Learn how to align Scrum values with your organization and then explore the most common terms in a Scrum glossary.
What is the sprint goal in scrum?
The sprint goal encapsulates the product owner’s vision into a concrete statement for the development team to measure the sprint against. The sprint goal provides a theme for the sprint’s work helping the team see how all the parts come together.
Learn more about the role of the sprint goal in scrum and explore the essential Scrum glossary.
Scrum backlog
What is the backlog in Scrum?
There are actually two backlogs, the product backlog and the sprint backlog. They each contain the definitive list of work to be done. The product owner keeps the backlog ordered by priority.
Learn to use the backlog in Scrum and check out the sprint backlog vs product backlog in Scrum.
How are the product backlog and sprint backlog different?
The product backlog prioritizes the features needed in the product. It is a singular visible source of requirements for the product.
The sprint backlog represents the work to do in a given sprint. It is a definitive list of all the scrum team is being asked to produce for the sprint.
Learn more about the sprint backlog vs product backlog in Scrum.
What is a PBI (product backlog item)?
Each item in the backlog represents precise work and value to deliver. Often these PBIs are written using both user stories and acceptance criteria. The PBIs are what gets refined during the backlog refinement session, and if one is too large, it may be broken down into smaller PBIs.
Learn more about how backlogs are used in scrum, the sprint backlog vs product backlog in Scrum and explore the essential Scrum glossary.
What is the Scrum sprint backlog?
The Scrum sprint backlog is a prioritized list of items from the product backlog that the development team plans to complete during the upcoming sprint.
It is a plan for the Sprint and is created during the Sprint Planning meeting where the Development Team decides on how to build the functionality that meets the Sprint Goal. The Sprint Backlog typically includes user stories, bugs, technical work, and other items that the development team needs to work on during the sprint. Each item in the Sprint Backlog has a clear definition of done, so the team knows when the item is considered complete.
The Development Team is responsible for creating and updating their Sprint Backlog throughout the Sprint, making sure they are on track to meet the Sprint Goal. The Sprint Backlog is a working document that helps the Development Team visualize their progress and make any necessary adjustments to their plan as they go along. The Sprint Backlog is also transparent, allowing stakeholders to see what work is being done during the Sprint.
Learn more about the backlogs of Scrum.
What is the Scrum product backlog?
In Scrum, the product backlog is a prioritized list of features, bugs, technical work, and other product-related items that need to be addressed by the development team.
It serves as a single source of truth for what needs to be done on the product.
The items in the product backlog are ordered based on their importance to the product owner and the value they bring to the end-user. As the project progresses, the product backlog is constantly updated to reflect new priorities, changes in requirements, and feedback from stakeholders.
The product backlog is a living document that evolves throughout the project's lifecycle. It provides transparency and enables collaboration among all members of the Scrum team.
Learn more about the backlogs in Scrum.
