Agile Homeschooling

An Experiment in Applying Scrum to Everyday Life

August 5, 2023
Scrum Education - pencils

Have you ever wondered if you can apply Scrum outside of software development? Like could Scrum be used in education?

It certainly can, and education is a field currently undergoing significant innovation. Our family has taken a less traditional approach by combining homeschooling with other learning opportunities. And through that journey discovered an unexpected application for Scrum.

Sometimes you just have questions about key Scrum terms. Download the Scrum terminology cheat sheet.

Adapting homeschool

When our oldest three boys moved from elementary to middle school, my wife and I knew they needed more agency and responsibility in managing their school work. But we weren’t sure how to navigate the transition.

We would give them more freedom, and they would procrastinate or not fully complete the work. They wanted more autonomy but didn’t yet have the maturity to handle it. They needed help. They needed freedom and flexibility combined with focus.

I had recently given a presentation on Scrum where I stated, “Scrum treats you like an adult.” 

A light bulb went off. 

And I nerded out and created a family Scrum team

  • I took the role of Scrum Master and would teach the family to practice Scrum.
  • My wife became the Product Owner focusing on what learning value needed to be delivered each sprint/week. 
  • Our kids made up the Dev Team.

I wanted to keep the process visually simple and accessible to everyone, so I created a board in Miro with a primary backlog, a weekly backlog, and columns for active, needs grading, needs correction and done

Homeschooling Scrum Miro Board
A typical week in Scrum homeschool

I gave each child a swim lane on the board to help them focus. This setup is not typical for Scrum, but we're talking about 11-year-old boys here.

Our Scrum rhythm.

At the beginning of the week, we would move all the new assignments to the weekly backlog column, and the kids would review their work and communicate their plans for getting things done that week. 

Every day we would check in using a typical Scrum daily standup approach. The boys would identify what they had completed, what they would focus on next and where they were stuck. If needed, we would plan the day together, informed by the week’s remaining work.

Just like on a team of adults, the act of stating out loud to others what you have completed and what you commit to doing next creates enormous accountability and ownership. I knew this to be true but was still surprised to see how quickly it changed my kids’ approach to their school work.

My wife would review all the work at the end of the week. If something was completed or needed to be redone, it was added to the following week’s backlog. This activity mirrors the sprint review, except that there weren’t any other stakeholders to present to. 

I would hold a retro where we evaluated how the week went, what was good and what we wanted to change. This review led to some creative adaptations over time. 

  1. We ended up sizing the work using small, medium and large rather than numeric story points.
  2. We experimented with many variations of color-coding or labeling cards so they could see at a glance which subjects had more work remaining. 

We kept these events pretty informal. I didn’t use much Scrum language, but I was still clear about what we did, when we did it and why it mattered.

What I learned from applying Scrum to schooling.

As we now are making the transition to high school, we are no longer using Scrum for the boy's schooling. Not because it didn’t work, but because it worked great. 

They are now owning to the process of prioritizing and completing their work. They each have their own system they’ve tweaked based on the board we started with. 

As I reflect on this Scrum schooling experiment, here are some observations and takeaways

  • We played roles according to our giftings.
  • The definition of done still matters.
  • Scrum faces the same challenges with kids as it does with adults. 
  • The scum values were adopted. 
  • Scrum can be applied less formally. 

Leaning Scrum for the first time can be a bit overwhelming. There are many new terms and concepts in Scrum.

Well we’re here to help.

We played roles according to our gifting.

My wife and I are both pretty involved in charting the course for our kids' education. But we bring different perspectives and strengths, and thus we play different roles.

My wife has a greater attention to detail and a more sequential approach to getting things done. She is way more patient to sit and work through learning handwriting than I would be. These strengths better equipped her for the broad yet methodical instruction of our kids' elementary years. 

I naturally bend toward a more global view and a non-linear approach. As our kids moved into middle and high school, their education involved combining disciplines and exploring possible vocational options. This is more my jam.

The grammar, tone and narrative structure of communication combined with the math of analytics and the art of design all come together into disciplines like UX or marketing. These also happen to be subjects I experience and share an interest with my kids.  

So I have taken more of the lead in helping them explore new subjects and careers by applying their giftings and interests.

The definition of done still matters. 

Just like with a team of adults, not everyone means the same thing when they say something is “done.” The first few weeks involved a lot of clarifying what was required for something to go into the done column.

Some examples included: 

  • Show ALL your math work. 
  • Spell check your paper. 
  • Make corrections after grading. 
  • Put your books away. 

These each seem simple and basic, which is why they are essential to cultivating maturity in how our kids approach work and life. Any team practicing Scrum needs a clear definition of done.

Scrum faces the same challenges with kids as it does with adults.

Simultaneously facilitating Scrum with children at home and adults at work was a fascinating study in human behavior. 

I was surprised how often I would address the same issues with both groups, even in a given week. These issues manifested differently but mostly revolved around living out the Scrum values. More on that in a minute.

I’ve often thought if my kids can learn kindness, delayed gratification and responsibility, they’ll do pretty in life. Interestingly Scrum assumes these qualities, which will be clearly visible when they aren’t present, and growth will be necessary.

If you haven’t learned agency and ownership already, Scrum will be challenging but present you with an opportunity to grow more than you thought possible. 

The scum values were adopted. 

Scrum is based on living out a set of 5 values. 

  1. Commit to achieving the goals of the Scrum Team.
  2. Courage to do the right thing and work on challenging problems.
  3. Focus on the Sprint's work and the Scrum Team's goals.
  4. Open about all the work and the challenges with performing the work.
  5. Respect each other to be capable, independent people.

In the beginning, commitment and focus were driving factors to us experimenting with Scrum. We wanted to cultivate these values more in our kids as they took greater ownership of their learning experience. 

Then courage and openness quickly came to the forefront. 

The first day we looked at the board, the kids were a little overwhelmed with how much they needed to get done, and there was a temptation to do all the easy things first. We addressed this during retrospectives for the first few weeks, and eventually, they grew the courage to take on the challenging tasks first. 

Early on, they were more prone to moving tasks along the board toward done even if they weren’t. As time went on, they learned the value of openness. If they said they needed help when encountering a problem, they benefited from us being able to help immediately. 

My wife and I had to grow in respect for our kids to be able to complete what they committed to. Taking this posture was hard when we could see they weren’t doing enough to finish by the end of the week. Allowing them to fail allowed them to grow. 

These values are essential to maturity and part of why I often say, “Scrum treats you like an adult.” 

Scrum can be applied less formally.

Our application of Scrum was undoubtedly less technical than what I was leading at work, but it was still effective. This experience is an instructive example of how Scrum can be applied to many types of work. If you're considering using Scrum in a field outside software development, check out my What is Scrum? Guide. I developed it to help people apply scrum to everyday life. 

What’s next

We’re no longer using scrum for our kids' education, but I continue experimenting with it in everyday life, such as writing or home DIY projects. 

If you’re applying scrum in a non-conventional setting, I’d love to hear about it. You can find me on LinkedIn. Reach out and let me know your experience.

Action Plan

To learn more about Scrum, check out my What is Scrum? A Guide for Everyday People to Learn Scrum.

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:

  1. How does this make things more visible? (Transparency)
  2. Where does this create space to evaluate? (Inspection)
  3. 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.

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.

  1. Transparency. How does this make things more visible?
  2. Inspection. Where does this create space to evaluate?
  3. 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.

  1. Commit to achieving the goals of the Scrum Team.
  2. Courage to do the right thing and work on challenging problems.
  3. Focus on the Sprint's work and the Scrum Team's goals.
  4. Open about all the work and the challenges with performing the work.
  5. 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.

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.

Ready to level up your company? Get in touch today!