Get certified - Transform your world of work today

Close

Saved by Scrum

A 13-year-old’s views on Scrum at home

19 April 2017

A solution to our problem

People often ask me how we got started using Scrum at home. We used Scrum because we wanted to solve a problem. My brother and I would always get into trouble because we thought that after we finished our homework, we could go out to play.



Then, my mom would come out and ask us, "Did you do your homework?"

"Yes."

"Are you really done with your homework?"

"Yes."

The problem would come up when my parents and I couldn’t agree on when the work was considered really "done." For example, the Definition of Done for math is to show all the steps to get the answer. We got into trouble because our Definition of Done was not the same as our parents' definition. Even though we thought we were done with our homework, we really weren't when my parents asked.

To address the problem, my dad introduced something he had used at work: the Definition of Done. We used the Definition of Done as a checklist that both parents and kids agreed on. We had a general Definition of Done that applied to every activity that we needed to finish and the Definition of Done for each subject. From there, we realized that Scrum could be used to solve other problems at home.
 

What is Scrum?

In general terms, Scrum is defined as a process framework.1 Scrum includes three roles: the product owner, the ScrumMaster, and the development team. In our house, the product owner is the all-powerful, all-knowing decision maker. She decides whether something is important. And you guessed it right — our product owner is my mom!

I am the ScrumMaster, the protector of Scrum. ScrumMasters help everybody with how to practice Scrum. In our home, I am a member of the development team as well as the ScrumMaster. The team does the work. So who’s left for the team? My brother, my dad, and I.

In Scrum, products are built incrementally in short timeboxes called sprints. For us, the sprint is always one week long. It starts on Sunday and ends on Saturday.

Scrum helps me to do the right things, do things right, and get things done faster. This structure comes from a Scrum expert named Henrik Kniberg,2 and that's how this article is organized. To get a complete description of Scrum, you can read The Scrum Guide.
 

Doing the right things

Scrum helps me to do the right things at home through our use of the Scrum board and the sprint planning meeting. Because our sprint starts on Sunday and ends on Saturday, we have the sprint planning meeting every Sunday afternoon. In this meeting, we identify things we need to do for the week. The product owner and the whole team must be present at the meeting. The product owner helps to identify the work and the priorities for the week, and we also get a list of assignments from our teachers.

Next, we write the work or tasks on individual index cards. These index cards are kept on a board on the wall. This board is divided into three columns named "To Do," "Doing" (or "Work in Progress/WIP") and "Done." The cards can be moved across the columns during the sprint.
image-1-(1).jpg
Our Scrum board in our hallway

The board helps me in several ways throughout the sprint. For example, sometimes the product owner (Mom) turns evil and makes us do more things than we actually can (sound familiar?). So, when my mom tells me to do an extra thing, I show her the board so that she can see that we already have enough work for the week. But it can also work the other way. My brother and I can’t pretend to have too much work because the product owner can figure it out when she sees a nearly empty board.

The Scrum board also helps me to remember things during the week. One Thursday, my dad was out of town, and he was going to come back the next day. I forgot to move things around on the board that week. I knew he would be mad if he saw the board like that, so I started moving a couple of cards around. Because I finished my science homework, I moved that card to the Done column. I also finished the history homework, but I noticed that I still had to do the math homework and that it was due the next day. I had to quickly finish my math homework, and I moved also that card before I went to bed. So the next day my dad was happy because he saw the board organized, and I was happy because if I hadn’t finished that math homework, I would have earned a terrible grade in math that week.
 

Doing things right

Scrum also helps me to do things right by applying the Definition of Done and the acceptance criteria. The acceptance criteria is specific to each card on the wall and is also different for each card. For example, one of the cards on the wall was a health project whereby the outcome was to find out how unhealthy meals were at restaurants across the U.S. The things I needed to do on that project to get a good grade were to find the nutritional facts for the original recipe from a restaurant, make a new recipe, and contact the restaurant for more information.

So that’s what we write on the card, numbering each step 1, 2, 3, respectively.

health-project-image.jpg


But wait, there’s more! There’s also something called the Definition of Done. The Definition of Done is usually generic and mostly applies to all cards. As stated in the introductory paragraph, the Definition of Done is a checklist that both parents and kids had agreed on. Before we mark anything done and move its card to the Done column, we verify whether we have met the acceptance criteria of the particular card and whether it is done according to the Definition of Done.
image-DOD-(1).jpg

Going faster

How does Scrum help me to get things done faster? To get things done faster at home, we use two things: the Daily Scrum meeting and a special house rule. We have our Daily Scrum meeting next to the board every day in the evening. This is when we move cards around on the board for that day. In the meeting, we say what we did that day, what we will do the next day, and any impediments we had so that our parents can help us remove the impediments.

By doing this every day, we get feedback on what work we did and how much work we did that day. But we can get feedback even more frequently by using the 25-minute rule.3 It works like this: When we come back from school, we take off our backpacks and eat some snacks, and then start begin our homework. Along with starting the homework, we start a 25-minute timer. At the end of that 25 minutes, regardless of whether we're done with the work, we show our parents what we've finished. We also get to take a few minutes' break. We get feedback on how well we worked and feedback on the work we did.

I talked a lot about feedback here, but how does this help me do things faster? Have you ever worked really hard on a big project nonstop, and at the end, when you show it to your boss, it turns out to be completely wrong? This problem, as we found out, can be fixed by getting frequent feedback. We use Scrum as a feedback loop, by getting feedback every week, every day, and even every 25 minutes. But getting things done faster doesn't mean that we are working any harder; rather, we get things done faster by finding mistakes earlier and by getting feedback earlier.
 

How Scrum has helped our household

Scrum has helped us solve a lot of problems we face at home and at school. We had the problem of not knowing what we should be doing, and it was fixed by using the Scrum board and the sprint planning meeting. We also had the problem of not getting things done the right way, which was solved by the Definition of Done. Another problem we faced was the problem of not getting things done on time, which was fixed by the 25-minute rule and by getting feedback all the time.

What I have described here is not everything that is defined in Scrum. We do not practice all of the Scrum principles when we use it at home, but we use most of them. One major difference that you will see is the lack of the shippable increment that is produced at the end of every sprint. We don’t have one single product that we are working on in a sprint. Instead, there are several items we work on. However, like in Scrum, we bring the backlog items to a done state at the end of every sprint. Another part we haven’t described here is the retrospective meeting at the end of every sprint; however, we have begun to use this lately.

To conclude, we started using a single practice in Scrum to solve one problem. By implementing more aspects of Scrum into our home and school life, we found that we could fix not one but many problems. Scrum helps us to get things done right, get the right things done, and get things done faster.
 

References

  1. Scrum Guides, http://www.scrumguides.org/
  2. "Agile Product Ownership in a Nutshell," YouTube video, 15:51, https://www.youtube.com/watch?v=502ILHjX9EE
  3. "Pomodoro Technique," Wikipedia, https://en.wikipedia.org/wiki/Pomodoro_Technique

Note: The author, Aaron Vadakkan, CSM®, is a 13-year-old who's currently in the eighth grade at Rocky Heights Middle School. He participated in two CSM classes. He is also an expert on "Scrum at Home," which is the topic he wrote about. Vadakkan has presented this topic twice, at two global Scrum gatherings. He had an early exposure to Scrum, at age eight, and he has been practicing it at home for about four years.
 

Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.



Article Rating

Current rating: 5 (1 ratings)

Comments

Holger Paffrath, CSM, 4/23/2017 6:45:52 AM
Aaron, thank you for your post. It's a very inspirational story. Great way to show how scrum can help even school kids manage their work load.

You must Login or Signup to comment.

The community welcomes feedback that is constructive and supportive, in the spirit of better understanding and implementation of Scrum.

 

Newsletter Sign-Up

Subscribe