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 project 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 work 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.

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.

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.

Next steps​ for applying Scrum.

New methodologies and frameworks are continually developing. Understanding the basics will help you continue to learn and grow.

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 1-hour coaching session, and we can work together to identify a good next step for you.