Welcome to the Certified Scrum Master course outline! This is not the full course – it is a roadmap that shows you everything you will learn. Think of it as a treasure map that guides you through the exciting world of Scrum.
A Scrum Master is a key person in an Agile team. They help the team follow Scrum processes, remove obstacles, and improve continuously. They are like a coach who helps the team play better.
In this course outline, you will see all the modules, lessons, and activities that will turn you into a Certified Scrum Master. You will learn what Scrum is, the role of the Scrum Master, and how to lead a team to success.
By the end of this course, you will be able to:
In Lagos, a development team was struggling. They had many meetings, but nothing was getting done. They were frustrated and behind schedule.
They hired a Scrum Master named Chidi. He helped them follow Scrum processes, removed obstacles, and coached them to work better together. The team became productive and delivered value.
Chidi said, "A Scrum Master is like a coach – they help the team win."
What you will learn:
Key Concepts: Scrum, Agile, framework.
Activities: Discuss why Scrum is important, share examples.
What you will learn:
Key Concepts: Roles, events, artifacts.
Activities: Draw a Scrum framework diagram.
What you will learn:
Key Concepts: Scrum Master, responsibility, coaching.
Activities: Role-play a Scrum Master.
What you will learn:
Key Concepts: Values, commitment, respect.
Activities: Discuss how to apply Scrum values.
What you will learn:
Key Concepts: Events, planning, review.
Activities: Simulate a sprint event.
What you will learn:
Key Concepts: Backlog, increment, done.
Activities: Create a product backlog.
What you will learn:
Key Concepts: Product Owner, backlog, value.
Activities: Simulate a Product Owner and Scrum Master interaction.
What you will learn:
Key Concepts: Development Team, self-organisation.
Activities: Discuss self-organisation.
What you will learn:
Key Concepts: Sprint, planning, goal.
Activities: Plan a sprint.
What you will learn:
Key Concepts: Stand-up, daily, alignment.
Activities: Practice a Daily Stand-up.
What you will learn:
Key Concepts: Review, demo, feedback.
Activities: Simulate a Sprint Review.
What you will learn:
Key Concepts: Retrospective, reflection, improvement.
Activities: Run a Retrospective.
What you will learn:
Key Concepts: Obstacles, blockers, protection.
Activities: Identify and remove obstacles.
What you will learn:
Key Concepts: Coaching, trust, self-organisation.
Activities: Practice coaching.
What you will learn:
Key Concepts: Certification, exam, career.
Activities: Create a career plan.
| Word | Simple Definition |
|---|---|
| Scrum | A framework for Agile teams. |
| Scrum Master | A coach for the Scrum team. |
| Sprint | A short period of work. |
| Backlog | A list of work to be done. |
| Product Owner | Maximises product value. |
| Development Team | Builds the product. |
| Stand-up | A short daily meeting. |
| Review | Showing work done. |
| Retrospective | Reflecting on the sprint. |
| Certification | Proof of your skills. |
Scrum Framework
|
+-- Roles
| +-- Scrum Master
| +-- Product Owner
| +-- Development Team
|
+-- Events
| +-- Sprint Planning
| +-- Daily Stand-up
| +-- Sprint Review
| +-- Sprint Retrospective
|
+-- Artifacts
+-- Product Backlog
+-- Sprint Backlog
+-- Increment
Product Backlog
|
V
Sprint Planning
|
V
Sprint (2-4 weeks)
|
+-- Daily Stand-ups
|
V
Sprint Review
|
V
Sprint Retrospective
|
V
Repeat
+-----------------------+-----------------------+ | Traditional | Scrum | +-----------------------+-----------------------+ | Plan everything | Plan and adapt | | Deliver at the end | Deliver frequently | | Hard to change | Easy to change | | Long cycles | Short cycles | | Less feedback | Continuous feedback | +-----------------------+-----------------------+
| Role | Responsibility | Example |
|---|---|---|
| Scrum Master | Coach and facilitator | Removes obstacles |
| Product Owner | Maximises value | Manages backlog |
| Development Team | Builds the product | Delivers features |
| Event | Purpose | Frequency |
|---|---|---|
| Sprint Planning | Plan the sprint | Start of sprint |
| Daily Stand-up | Share progress | Daily |
| Sprint Review | Show work done | End of sprint |
| Sprint Retrospective | Improve process | End of sprint |
Module 1: Introduction to Scrum – Understanding the basics.
Module 2: The Scrum Framework – Roles, events, artifacts.
Module 3: The Scrum Master Role – Responsibilities.
Module 4: Scrum Values – Commitment, Courage, Focus, Openness, Respect.
Module 5: Scrum Events – Planning, stand-up, review, retrospective.
Module 6: Scrum Artifacts – Backlog, increment, done.
Module 7: The Product Owner – Maximising value.
Module 8: The Development Team – Building the product.
Module 9: Sprint Planning – Planning the sprint.
Module 10: Daily Stand-up – Daily alignment.
Module 11: Sprint Review – Demonstrating work.
Module 12: Sprint Retrospective – Reflecting and improving.
Module 13: Removing Obstacles – Protecting the team.
Module 14: Coaching the Team – Building trust.
Module 15: Becoming a Certified Scrum Master – Certification.
This outline gives you a complete overview of the Certified Scrum Master course. You will learn everything from the basics of Scrum to the responsibilities of a Scrum Master and how to become certified. By the end, you will be ready to lead Scrum teams and help them succeed. Whether you are in Lagos, Abuja, or anywhere else, Scrum Master skills are valuable. Get ready to become a Certified Scrum Master!
Match the term with its definition.
| Term | Definition |
|---|---|
| 1. Scrum | A. Framework for Agile teams |
| 2. Scrum Master | B. Coach for the team |
| 3. Sprint | C. Short period of work |
| 4. Backlog | D. List of work |
| 5. Product Owner | E. Maximises value |
Answers: 1-A, 2-B, 3-C, 4-D, 5-E
“Scrum Simulation”
In groups, simulate a Scrum team. Assign roles: Scrum Master, Product Owner, and Development Team. Plan a sprint, hold a daily stand-up, and conduct a review and retrospective. Present your experience to the class.
“My Scrum Master Plan”
Create a plan for becoming a Certified Scrum Master. Include what you will learn, how you will study, and your career goals. Share your plan with the class.
“Scrum Master Plan”
Create a Scrum Master plan for a team. Include how you would facilitate events, remove obstacles, and coach the team. Present your plan to the class.
“Scrum Practice”
Apply Scrum to a personal project. Plan a sprint, hold daily stand-ups, and conduct a review and retrospective. Share your experience with the class.
“Scrum Master Challenge”
Create a comprehensive Scrum Master plan for a complex team. Include facilitation, obstacle removal, coaching, and continuous improvement. Share your solution with the class.
(Answers to fill-in-the-blank, true/false, and multiple choice are provided within those sections.)
You are now ready to start the Certified Scrum Master course. Before Module 1, do the following:
Get ready to become a Certified Scrum Master!
End of Course Outline · Let's get started!
Hello, future Scrum Master! Welcome to the first module of Certified Scrum Master. In this module, we will meet a powerful way of working called Scrum.
Scrum is a framework that helps teams work together, deliver value faster, and adapt to change. It is used by millions of teams around the world to build products and services.
In this module, you will learn what Scrum is, why it was created, and how it helps teams succeed.
Let's start our journey into the world of Scrum!
By the end of this module, you will be able to:
In Lagos, a team was building a new mobile app. They planned everything at the start – all the features, all the designs, all the deadlines. They worked for months.
But then, the market changed. Users wanted different features. The team had to start over. They were frustrated and behind schedule.
They heard about Scrum. They decided to try it. Instead of planning everything at once, they worked in short cycles called sprints. They delivered small pieces of the app every two weeks. They got feedback and adapted.
Within a few months, they had a successful app that users loved. The team leader, Mr. Adebayo, said, "Scrum helped us adapt to change and deliver faster."
Definition: Scrum is a framework that helps teams work together, deliver value, and adapt to change.
Why is it important? It helps teams be more effective and responsive.
Simple explanation: Scrum is like a playbook for teamwork.
Real-life example: A team uses Scrum to build a mobile app.
School example: A group uses Scrum to complete a project.
Home example: A family uses Scrum to plan a holiday.
Nigerian example: A Nigerian team uses Scrum to build a product.
Scrum = Framework for teamwork
Mini summary: Scrum is a framework for effective teamwork.
Definition: Scrum was created because traditional ways of working were too rigid and slow.
Why is it important? It solves the problem of changing requirements.
Simple explanation: The old way of working was like building a house without changes.
Real-life example: Traditional methods plan everything at the start; Scrum adapts.
School example: Traditional is like studying the same way all year; Scrum is like adapting.
Home example: Traditional is like buying all food for the month; Scrum is like buying weekly.
Nigerian example: Nigerian teams use Scrum to adapt to market changes.
Why Scrum was created: - To adapt to change - To deliver faster - To collaborate better - To reduce waste
Mini summary: Scrum was created to solve the problems of rigid planning.
Definition: Traditional (Waterfall) plans everything at the start; Scrum plans and adapts.
Why is it important? Understanding the difference helps you choose the right approach.
Simple explanation: Traditional is like building a house without changes; Scrum is like building a house and making changes along the way.
Real-life example: Traditional: plan all features; Scrum: deliver small pieces and get feedback.
School example: Traditional: write the whole essay first; Scrum: write, get feedback, improve.
Home example: Traditional: buy all groceries for the month; Scrum: buy weekly and adapt.
Nigerian example: Traditional: plan the whole product; Scrum: deliver in small pieces.
Traditional vs Scrum: - Traditional: Plan everything, deliver at the end - Scrum: Plan small, deliver frequently, adapt
Mini summary: Scrum is more flexible than traditional methods.
Definition: Scrum has three roles, five events, and three artifacts.
Why is it important? These elements work together to make Scrum effective.
Simple explanation: Scrum is like a recipe with ingredients and steps.
Real-life example: A team uses Scrum roles, events, and artifacts.
School example: A group uses a framework for a project.
Home example: A family uses a routine for chores.
Nigerian example: A Nigerian team uses the Scrum framework.
Scrum Framework: - 3 Roles: Scrum Master, Product Owner, Development Team - 5 Events: Sprint Planning, Daily Stand-up, Sprint Review, Sprint Retrospective, Sprint - 3 Artifacts: Product Backlog, Sprint Backlog, Increment
Mini summary: Scrum has roles, events, and artifacts.
Definition: Scrum has three roles: Scrum Master, Product Owner, and Development Team.
Why is it important? Each role has specific responsibilities.
Simple explanation: Each person has a job to do.
Real-life example: A team has a Scrum Master, Product Owner, and developers.
School example: A group has a leader, facilitator, and workers.
Home example: A family has different roles.
Nigerian example: A Nigerian Scrum team has these roles.
Scrum Roles: - Scrum Master: Coach and facilitator - Product Owner: Maximises value - Development Team: Builds the product
Mini summary: Scrum has three roles.
Definition: Scrum events are meetings that help the team plan, review, and improve.
Why is it important? They keep the team aligned.
Simple explanation: Scrum events are like team meetings.
Real-life example: A team has sprint planning, daily stand-ups, reviews, and retrospectives.
School example: A group has planning and review meetings.
Home example: A family has planning and review meetings.
Nigerian example: A Nigerian team holds Scrum events.
Scrum Events: - Sprint: A short period of work (2-4 weeks) - Sprint Planning: Plan the sprint - Daily Stand-up: A short daily meeting - Sprint Review: Show work done - Sprint Retrospective: Reflect and improve
Mini summary: Scrum events keep the team aligned.
Definition: Scrum artifacts are the outputs of Scrum – like the product backlog and sprint backlog.
Why is it important? They help the team track progress.
Simple explanation: Artifacts are like tools for the team.
Real-life example: The team uses a product backlog and sprint backlog.
School example: A student uses a to-do list.
Home example: A family uses a shopping list.
Nigerian example: A Nigerian team uses Scrum artifacts.
Scrum Artifacts: - Product Backlog: A list of all features and tasks - Sprint Backlog: Items selected for the sprint - Increment: The working product at the end of the sprint
Mini summary: Scrum artifacts help track progress.
Definition: A sprint is a short period of work, usually 2-4 weeks.
Why is it important? It helps teams deliver value frequently.
Simple explanation: A sprint is like a race – you go fast and finish strong.
Real-life example: A team works in two-week sprints.
School example: A student works in weekly study sprints.
Home example: A family works in daily chore sprints.
Nigerian example: A Nigerian team uses sprints.
Sprint = Short period of work
Mini summary: Sprints help teams deliver value frequently.
Definition: The sprint goal is a clear objective for the sprint.
Why is it important? It gives the team a shared purpose.
Simple explanation: The sprint goal is the destination for the sprint.
Real-life example: "Complete the login feature" is a sprint goal.
School example: "Finish the research" is a sprint goal.
Home example: "Clean the house" is a sprint goal.
Nigerian example: "Implement payment processing" is a sprint goal.
Sprint Goal = Clear objective for the sprint
Mini summary: The sprint goal gives the team a purpose.
Definition: Scrum provides many benefits, including faster delivery, better quality, and happier teams.
Why is it important? It makes teams more effective.
Simple explanation: Scrum helps teams do better work.
Real-life example: A team delivers a product in months instead of years.
School example: A student learns more effectively.
Home example: A family works together better.
Nigerian example: A Nigerian team delivers value faster.
Benefits of Scrum: - Faster delivery - Better quality - Happier teams - Adaptability to change
Mini summary: Scrum makes teams more effective.
Definition: Common mistakes are errors that new Scrum teams often make.
Why is it important? Avoiding them saves time.
Simple explanation: Don't skip Scrum events.
Real-life example: A team skips the retrospective.
School example: A group skips reflection.
Home example: A family skips planning.
Nigerian example: A team skips Scrum events.
Common Mistakes: - Skipping Scrum events - Not following roles - Ignoring the backlog
Mini summary: Don't skip Scrum events.
Definition: Best practices are the recommended ways to use Scrum.
Why is it important? They help you succeed.
Simple explanation: Follow the Scrum framework and values.
Real-life example: A team holds all Scrum events and follows roles.
School example: A group follows a project framework.
Home example: A family follows a routine.
Nigerian example: A Nigerian team follows best practices.
Best Practices: - Hold all Scrum events - Follow Scrum roles - Embrace Agile values - Adapt to change
Mini summary: Follow best practices for success.
Definition: Scrum is not just for work – it is for life.
Why is it important? It helps you be more effective.
Simple explanation: You can use Scrum in daily life.
Real-life example: A person uses Scrum to plan their week.
School example: A student uses Scrum to study.
Home example: A family uses Scrum to plan meals.
Nigerian example: A Nigerian uses Scrum to manage tasks.
Scrum is for life.
Mini summary: Scrum is useful in all areas of life.
Definition: Scrum is a framework for implementing Agile.
Why is it important? It is the most popular Agile framework.
Simple explanation: Scrum is like a recipe for Agile.
Real-life example: A team uses Scrum to be Agile.
School example: A student uses a study framework to be effective.
Home example: A family uses a routine to be organised.
Nigerian example: A Nigerian team uses Scrum to be Agile.
Scrum = Agile framework
Mini summary: Scrum is a framework for Agile.
Definition: You are now on your way to becoming a Scrum Master.
Why is it important? You have started your journey.
Simple explanation: You are the coach of the future.
Real-life example: You can lead a Scrum team.
School example: You can lead school projects.
Home example: You can help your family.
Nigerian example: You can become a Certified Scrum Master in Nigeria.
Future Scrum Master Checklist: - Understands Scrum - Knows the framework - Ready to learn more - Excited to become a Scrum Master
Mini summary: You are on your way to becoming a Scrum Master!
| Word | Simple Definition |
|---|---|
| Scrum | A framework for teamwork. |
| Framework | A structure or system. |
| Sprint | A short period of work. |
| Backlog | A list of work to be done. |
| Scrum Master | A coach for the Scrum team. |
| Product Owner | Maximises product value. |
| Development Team | Builds the product. |
| Stand-up | A short daily meeting. |
| Review | Showing work done. |
| Retrospective | Reflecting on the sprint. |
Product Backlog
|
V
Sprint Planning
|
V
Sprint (2-4 weeks)
|
+-- Daily Stand-ups
|
V
Sprint Review
|
V
Sprint Retrospective
|
V
Repeat
Scrum Framework
|
+-- Roles
| +-- Scrum Master
| +-- Product Owner
| +-- Development Team
|
+-- Events
| +-- Sprint Planning
| +-- Daily Stand-up
| +-- Sprint Review
| +-- Sprint Retrospective
|
+-- Artifacts
+-- Product Backlog
+-- Sprint Backlog
+-- Increment
+-----------------------+-----------------------+ | Traditional | Scrum | +-----------------------+-----------------------+ | Plan everything | Plan and adapt | | Deliver at the end | Deliver frequently | | Hard to change | Easy to change | | Long cycles | Short cycles | | Less feedback | Continuous feedback | +-----------------------+-----------------------+
| Aspect | Traditional | Scrum |
|---|---|---|
| Planning | Plan everything at the start | Plan and adapt |
| Delivery | Deliver at the end | Deliver frequently |
| Change | Hard to change | Easy to change |
| Cycles | Long cycles | Short cycles |
| Feedback | Less feedback | Continuous feedback |
| Role | Responsibility | Example |
|---|---|---|
| Scrum Master | Coach and facilitator | Removes obstacles |
| Product Owner | Maximises value | Manages backlog |
| Development Team | Builds the product | Delivers features |
(Included after each lesson above – review them!)
In this first module, you have learned the basics of Scrum. You discovered what Scrum is, why it was created, and how it differs from traditional methods. You also learned about the Scrum framework, roles, events, and artifacts. You are now on your way to becoming a Scrum Master. In the next module, you will learn about the Scrum framework in detail. Congratulations on completing Module One!
Match the term with its definition.
| Term | Definition |
|---|---|
| 1. Scrum | A. Framework for teamwork |
| 2. Sprint | B. Short period of work |
| 3. Backlog | C. List of work |
| 4. Scrum Master | D. Coach for the team |
| 5. Product Owner | E. Maximises value |
Answers: 1-A, 2-B, 3-C, 4-D, 5-E
“Scrum Discussion”
In groups, discuss how Scrum could help a team you know. Share your ideas with the class.
“My Scrum Plan”
Write a plan for applying Scrum to a project in your life. Include how you would adapt to change and collaborate. Share your plan with the class.
“Scrum Project Plan”
Create a Scrum project plan for a small project. Include how you will adapt to change and collaborate. Present your plan to the class.
“Scrum Observation”
Observe a team or group you are part of. Note how they work. Write a report on how they could use Scrum to improve.
“Scrum Challenge”
Create a comprehensive Scrum plan for a complex project. Include how you will adapt, collaborate, and deliver value. Share your solution with the class.
(Answers to fill-in-the-blank, true/false, and multiple choice are provided within those sections.)
In Module Two, you will learn about the Scrum framework in detail. To prepare:
Get ready to learn about the Scrum framework!
End of Module One · Welcome to the world of Scrum!
Hello, framework explorer! In Module One, you learned what Scrum is and why it is important. Now it is time to learn about the Scrum framework in detail – the roles, events, and artifacts that make Scrum work.
The Scrum framework is like a recipe for success. It has clear ingredients (roles, events, artifacts) that work together to help teams deliver value.
In this module, you will learn about the three roles, five events, and three artifacts of Scrum. You will understand how they work together to create a high-performing team.
Let's explore the Scrum framework!
By the end of this module, you will be able to:
In Lagos, a team was new to Scrum. They knew the theory, but they struggled to put it into practice. They didn't understand how the roles, events, and artifacts fit together.
They decided to learn the Scrum framework in depth. They assigned the three roles – Scrum Master, Product Owner, and Development Team. They held the five events – sprint planning, daily stand-ups, sprint reviews, and retrospectives. They used the three artifacts – product backlog, sprint backlog, and increment.
Soon, they were working like a well-oiled machine. They delivered value faster and improved every sprint. The team leader, Mrs. Okafor, said, "Understanding the framework made all the difference."
Definition: The Scrum framework consists of three roles, five events, and three artifacts.
Why is it important? These elements work together to make Scrum effective.
Simple explanation: The framework is like a recipe for teamwork.
Real-life example: A team uses the framework to build a product.
School example: A group uses a framework for a project.
Home example: A family uses a routine for chores.
Nigerian example: A Nigerian team uses the Scrum framework.
Scrum Framework: - 3 Roles - 5 Events - 3 Artifacts
Mini summary: The Scrum framework has roles, events, and artifacts.
Definition: Scrum has three roles: Scrum Master, Product Owner, and Development Team.
Why is it important? Each role has specific responsibilities.
Simple explanation: Each person has a job to do.
Real-life example: A team has a Scrum Master, Product Owner, and developers.
School example: A group has a leader, facilitator, and workers.
Home example: A family has different roles.
Nigerian example: A Nigerian Scrum team has these roles.
Scrum Roles: - Scrum Master - Product Owner - Development Team
Mini summary: Scrum has three roles.
Definition: The Scrum Master is a coach who helps the team follow Scrum processes and remove obstacles.
Why is it important? They help the team work better.
Simple explanation: The Scrum Master is like a coach.
Real-life example: A Scrum Master facilitates meetings and removes blockers.
School example: A facilitator helps the group work together.
Home example: A parent helps the family stay organised.
Nigerian example: A Scrum Master helps the Nigerian team.
Scrum Master: - Facilitates Scrum events - Removes obstacles - Coaches the team
Mini summary: The Scrum Master coaches the team.
Definition: The Product Owner is responsible for maximising the value of the product.
Why is it important? They guide the product direction.
Simple explanation: The Product Owner is the captain of the ship.
Real-life example: A Product Owner manages the backlog and prioritises features.
School example: A student leader guides the project.
Home example: A parent guides the family.
Nigerian example: A Product Owner guides the Nigerian product.
Product Owner: - Manages backlog - Prioritises features - Maximises value
Mini summary: The Product Owner guides the product.
Definition: The Development Team builds the product.
Why is it important? They are the builders.
Simple explanation: The Development Team does the work.
Real-life example: Developers build the product.
School example: Students do the project work.
Home example: Family members do the chores.
Nigerian example: Nigerian developers build the product.
Development Team: - Builds the product - Self-organises - Delivers value
Mini summary: The Development Team builds the product.
Definition: Scrum events are meetings that help the team plan, review, and improve.
Why is it important? They keep the team aligned.
Simple explanation: Scrum events are like team meetings.
Real-life example: A team has sprint planning, daily stand-ups, reviews, and retrospectives.
School example: A group has planning and review meetings.
Home example: A family has planning and review meetings.
Nigerian example: A Nigerian team holds Scrum events.
Scrum Events: - Sprint Planning - Daily Stand-up - Sprint Review - Sprint Retrospective - Sprint (the work period)
Mini summary: Scrum events keep the team aligned.
Definition: Sprint planning is a meeting where the team plans the sprint.
Why is it important? It sets the direction for the sprint.
Simple explanation: You plan the work for the sprint.
Real-life example: The team plans what to build in the next sprint.
School example: A group plans what to do for the week.
Home example: A family plans the weekend.
Nigerian example: A Nigerian team plans the sprint.
Sprint Planning: - Set sprint goal - Choose backlog items - Plan the work
Mini summary: Sprint planning sets the sprint direction.
Definition: Daily stand-up is a short daily meeting where the team shares progress.
Why is it important? It keeps the team aligned.
Simple explanation: You meet every day for 15 minutes.
Real-life example: The team shares what they did yesterday and what they will do today.
School example: A group shares daily progress.
Home example: A family shares daily plans.
Nigerian example: A Nigerian team holds daily stand-ups.
Daily Stand-up: - What did I do yesterday? - What will I do today? - Any blockers?
Mini summary: Daily stand-ups keep the team aligned.
Definition: Sprint review is a meeting where the team shows what they built.
Why is it important? It demonstrates progress and gathers feedback.
Simple explanation: You show the work done.
Real-life example: The team demos new features.
School example: A group presents project progress.
Home example: A family shows what they accomplished.
Nigerian example: A Nigerian team holds a sprint review.
Sprint Review: - Demo completed work - Gather feedback - Update backlog
Mini summary: Sprint review demonstrates progress.
Definition: Sprint retrospective is a meeting where the team reflects on the sprint.
Why is it important? It helps the team improve.
Simple explanation: You discuss what went well and what can be improved.
Real-life example: The team reflects on the sprint.
School example: A group reflects on the project.
Home example: A family reflects on the week.
Nigerian example: A Nigerian team holds a retrospective.
Sprint Retrospective: - What went well? - What can be improved? - Action items
Mini summary: Sprint retrospective helps the team improve.
Definition: Scrum artifacts are the outputs of Scrum – like the product backlog and sprint backlog.
Why is it important? They help the team track progress.
Simple explanation: Artifacts are like tools for the team.
Real-life example: The team uses a product backlog and sprint backlog.
School example: A student uses a to-do list.
Home example: A family uses a shopping list.
Nigerian example: A Nigerian team uses Scrum artifacts.
Scrum Artifacts: - Product Backlog - Sprint Backlog - Increment
Mini summary: Scrum artifacts help track progress.
Definition: The product backlog is a list of all the features and tasks needed for the product.
Why is it important? It helps the team know what to work on.
Simple explanation: The backlog is a to-do list for the product.
Real-life example: A list of features for an app.
School example: A list of tasks for a project.
Home example: A list of chores for the week.
Nigerian example: A list of features for a Nigerian product.
Product Backlog = To-do list for the product
Mini summary: The product backlog is a to-do list.
Definition: The sprint backlog is a list of items selected for the current sprint.
Why is it important? It defines what the team will work on during the sprint.
Simple explanation: The sprint backlog is the sprint to-do list.
Real-life example: A team selects items for the sprint.
School example: A group selects tasks for the week.
Home example: A family selects chores for the day.
Nigerian example: A Nigerian team creates a sprint backlog.
Sprint Backlog = Items for the sprint
Mini summary: The sprint backlog is the sprint to-do list.
Definition: The increment is the working product at the end of the sprint. The Definition of Done is the criteria for completion.
Why is it important? It ensures quality and consistency.
Simple explanation: The increment is what the team delivers. The Definition of Done is the checklist.
Real-life example: A team delivers a working feature.
School example: A student delivers a completed project.
Home example: A family completes a task.
Nigerian example: A Nigerian team delivers an increment.
Increment = Working product Definition of Done = Checklist for completion
Mini summary: The increment is the working product.
Definition: You are now a framework practitioner – you understand the Scrum framework.
Why is it important? You can help teams use Scrum effectively.
Simple explanation: You have mastered the framework.
Real-life example: You can guide a Scrum team.
School example: You can lead a group project.
Home example: You can apply Scrum at home.
Nigerian example: You can become a Certified Scrum Master in Nigeria.
Framework Practitioner Checklist: - Understands Scrum roles - Knows Scrum events - Uses Scrum artifacts - Ready to apply Scrum
Mini summary: You are now a framework practitioner!
| Word | Simple Definition |
|---|---|
| Framework | A structure or system. |
| Role | A position or function. |
| Event | A meeting or activity. |
| Artifact | An output or document. |
| Scrum Master | Coach for the team. |
| Product Owner | Maximises value. |
| Development Team | Builds the product. |
| Sprint | Short period of work. |
| Backlog | List of work. |
| Increment | Working product. |
Scrum Framework
|
+-- Roles
| +-- Scrum Master
| +-- Product Owner
| +-- Development Team
|
+-- Events
| +-- Sprint Planning
| +-- Daily Stand-up
| +-- Sprint Review
| +-- Sprint Retrospective
| +-- Sprint
|
+-- Artifacts
+-- Product Backlog
+-- Sprint Backlog
+-- Increment
Product Backlog
|
V
Sprint Planning
|
V
Sprint (2-4 weeks)
|
+-- Daily Stand-ups
|
V
Sprint Review
|
V
Sprint Retrospective
|
V
Repeat
+-----------------------+-----------------------+ | Traditional | Scrum | +-----------------------+-----------------------+ | Plan everything | Plan and adapt | | Deliver at the end | Deliver frequently | | Hard to change | Easy to change | | Long cycles | Short cycles | | Less feedback | Continuous feedback | +-----------------------+-----------------------+
| Role | Responsibility | Example |
|---|---|---|
| Scrum Master | Coach and facilitator | Removes obstacles |
| Product Owner | Maximises value | Manages backlog |
| Development Team | Builds the product | Delivers features |
| Event | Purpose | Frequency |
|---|---|---|
| Sprint Planning | Plan the sprint | Start of sprint |
| Daily Stand-up | Share progress | Daily |
| Sprint Review | Show work done | End of sprint |
| Sprint Retrospective | Improve process | End of sprint |
(Included after each lesson above – review them!)
In this module, you learned about the Scrum framework in detail. You discovered the three roles, five events, and three artifacts. You are now a framework practitioner. In the next module, you will learn about the Scrum Master role in detail. Congratulations on completing Module Two!
Match the term with its definition.
| Term | Definition |
|---|---|
| 1. Scrum Master | A. Coaches the team |
| 2. Product Owner | B. Maximises value |
| 3. Development Team | C. Builds the product |
| 4. Sprint | D. Short period of work |
| 5. Backlog | E. List of work |
Answers: 1-A, 2-B, 3-C, 4-D, 5-E
“Framework Simulation”
In groups, simulate a Scrum team. Assign roles, hold a sprint planning, daily stand-up, review, and retrospective. Present your experience to the class.
“My Framework Plan”
Create a plan for using the Scrum framework in a project. Include roles, events, and artifacts. Share your plan with the class.
“Framework Project”
Create a Scrum framework plan for a project. Include roles, events, and artifacts. Present your plan to the class.
“Framework Practice”
Apply the Scrum framework to a personal project. Plan a sprint, hold stand-ups, and conduct a review and retrospective. Share your experience with the class.
“Framework Challenge”
Create a comprehensive Scrum framework plan for a complex project. Include roles, events, and artifacts. Share your solution with the class.
(Answers to fill-in-the-blank, true/false, and multiple choice are provided within those sections.)
In Module Three, you will learn about the Scrum Master role in detail. To prepare:
Get ready to learn about the Scrum Master role!
End of Module Two · You are now a framework practitioner!
Hello, aspiring Scrum Master! In Module Two, you learned about the Scrum framework. Now it is time to dive deep into the Scrum Master role – the heart of Scrum.
A Scrum Master is not a manager or a boss. They are a coach, a facilitator, and a servant leader. They help the team follow Scrum, remove obstacles, and improve continuously.
In this module, you will learn what a Scrum Master does, the skills they need, and how to be an effective Scrum Master.
Let's become a great Scrum Master!
By the end of this module, you will be able to:
In Lagos, a team was struggling. They had a Product Owner, a Development Team, and a backlog. But they were not delivering value. They were frustrated and demotivated.
They hired a Scrum Master named Chidi. He didn't tell them what to do. Instead, he coached them, facilitated their meetings, and removed obstacles. He protected the team from distractions.
Soon, the team became productive and happy. They delivered value every sprint. The team leader said, "Chidi is the best Scrum Master we ever had."
Definition: A Scrum Master is a coach who helps the team follow Scrum processes and remove obstacles.
Why is it important? They help the team work better.
Simple explanation: The Scrum Master is like a coach for the team.
Real-life example: A Scrum Master facilitates meetings and removes blockers.
School example: A facilitator helps the group work together.
Home example: A parent helps the family stay organised.
Nigerian example: A Scrum Master helps the Nigerian team.
Scrum Master = Coach for the team
Mini summary: The Scrum Master coaches the team.
Definition: A servant leader puts the team first and serves their needs.
Why is it important? It builds trust and empowers the team.
Simple explanation: The Scrum Master serves the team, not the other way around.
Real-life example: A Scrum Master removes obstacles for the team.
School example: A teacher helps students succeed.
Home example: A parent supports their children.
Nigerian example: A Scrum Master serves the Nigerian team.
Servant Leader = Puts team first
Mini summary: The Scrum Master serves the team.
Definition: The Scrum Master's responsibilities include facilitating, coaching, and removing obstacles.
Why is it important? They keep the team moving forward.
Simple explanation: The Scrum Master does many things to help the team.
Real-life example: A Scrum Master facilitates sprint planning.
School example: A group leader helps the group plan.
Home example: A parent helps the family plan.
Nigerian example: A Scrum Master facilitates the Nigerian team.
Responsibilities: - Facilitate Scrum events - Coach the team - Remove obstacles - Protect the team
Mini summary: The Scrum Master has many responsibilities.
Definition: Facilitating means making Scrum events run smoothly.
Why is it important? Good facilitation leads to good outcomes.
Simple explanation: The Scrum Master helps the team have effective meetings.
Real-life example: A Scrum Master facilitates sprint planning.
School example: A student leads a group discussion.
Home example: A parent leads a family meeting.
Nigerian example: A Scrum Master facilitates events in Nigeria.
Facilitation: - Sprint Planning - Daily Stand-up - Sprint Review - Sprint Retrospective
Mini summary: The Scrum Master facilitates events.
Definition: Coaching means helping the team improve and grow.
Why is it important? It builds a strong, self-organising team.
Simple explanation: The Scrum Master teaches and guides the team.
Real-life example: A Scrum Master coaches the team on Scrum practices.
School example: A teacher coaches students.
Home example: A parent coaches a child.
Nigerian example: A Scrum Master coaches the Nigerian team.
Coaching: - Teach Scrum - Guide the team - Encourage self-organisation - Build trust
Mini summary: The Scrum Master coaches the team.
Definition: Obstacles are things that block the team's progress.
Why is it important? Removing obstacles helps the team deliver value.
Simple explanation: The Scrum Master clears the path for the team.
Real-life example: A Scrum Master removes a blocker for the team.
School example: A student helps remove a problem for the group.
Home example: A parent helps remove a problem for the family.
Nigerian example: A Scrum Master removes obstacles for the Nigerian team.
Removing Obstacles: - Identify blockers - Remove blockers - Prevent future blockers
Mini summary: The Scrum Master removes obstacles.
Definition: Protecting the team means shielding them from distractions and interruptions.
Why is it important? It helps the team stay focused.
Simple explanation: The Scrum Master guards the team's time.
Real-life example: A Scrum Master prevents stakeholders from interrupting the team.
School example: A student leader protects the group from distractions.
Home example: A parent protects family time.
Nigerian example: A Scrum Master protects the Nigerian team.
Protection: - Shield from distractions - Guard the sprint goal - Maintain focus
Mini summary: The Scrum Master protects the team.
Definition: Skills are the abilities a Scrum Master needs to be effective.
Why is it important? Good skills make a great Scrum Master.
Simple explanation: Skills are like tools in a toolbox.
Real-life example: Communication, facilitation, and coaching.
School example: Leadership, organisation, and teamwork.
Home example: Patience, listening, and problem-solving.
Nigerian example: A Scrum Master uses skills in Nigeria.
Skills: - Communication - Facilitation - Coaching - Problem-solving - Empathy
Mini summary: Scrum Masters need good skills.
Definition: A Project Manager manages tasks and timelines; a Scrum Master coaches and facilitates.
Why is it important? They have different roles and approaches.
Simple explanation: The Scrum Master is a coach; the Project Manager is a boss.
Real-life example: A Project Manager assigns tasks; a Scrum Master helps the team self-organise.
School example: A teacher assigns work; a facilitator helps the group.
Home example: A parent assigns chores; a coach helps the family improve.
Nigerian example: A Nigerian team has a Scrum Master.
Scrum Master vs Project Manager: - Scrum Master: Coach, facilitator, servant leader - Project Manager: Manager, planner, controller
Mini summary: The Scrum Master is different from a Project Manager.
Definition: The Scrum Master works with the Product Owner to manage the backlog and maximise value.
Why is it important? They need to collaborate effectively.
Simple explanation: The Scrum Master helps the Product Owner.
Real-life example: A Scrum Master helps the Product Owner refine the backlog.
School example: A facilitator helps the group leader.
Home example: A parent helps another parent.
Nigerian example: A Scrum Master works with the Nigerian Product Owner.
Scrum Master + Product Owner: - Collaborate on backlog - Align on goals - Support each other
Mini summary: The Scrum Master works with the Product Owner.
Definition: The Scrum Master supports the Development Team and helps them self-organise.
Why is it important? The team needs to be empowered.
Simple explanation: The Scrum Master helps the team work independently.
Real-life example: A Scrum Master coaches the team to solve problems.
School example: A facilitator helps the group work together.
Home example: A parent helps the family work together.
Nigerian example: A Scrum Master supports the Nigerian Development Team.
Scrum Master + Development Team: - Coach and support - Remove obstacles - Encourage self-organisation
Mini summary: The Scrum Master supports the Development Team.
Definition: Common mistakes are errors that new Scrum Masters often make.
Why is it important? Avoiding them saves time.
Simple explanation: Don't act like a manager.
Real-life example: A Scrum Master tells the team what to do.
School example: A facilitator takes over the group.
Home example: A parent controls everything.
Nigerian example: A Scrum Master makes mistakes.
Common Mistakes: - Acting like a manager - Not removing obstacles - Not coaching - Ignoring the team
Mini summary: Avoid common mistakes.
Definition: Best practices are the recommended ways to be a Scrum Master.
Why is it important? They help you succeed.
Simple explanation: Coach, facilitate, and serve.
Real-life example: A Scrum Master coaches and removes obstacles.
School example: A facilitator supports the group.
Home example: A parent supports the family.
Nigerian example: A Scrum Master follows best practices.
Best Practices: - Coach the team - Facilitate events - Remove obstacles - Protect the team - Serve the team
Mini summary: Follow best practices for success.
Definition: The Scrum Master role is not just for work – it is for life.
Why is it important? It helps you help others.
Simple explanation: You can be a Scrum Master for your family and friends.
Real-life example: A person helps their family organise tasks.
School example: A student helps classmates.
Home example: A parent helps the family.
Nigerian example: A Nigerian helps their community.
Scrum Master skills are for life.
Mini summary: Scrum Master skills are useful everywhere.
Definition: You are now a Scrum Master – you understand the role and responsibilities.
Why is it important? You can help teams succeed.
Simple explanation: You have mastered the Scrum Master role.
Real-life example: You can be a Scrum Master for any team.
School example: You can lead school projects.
Home example: You can help your family.
Nigerian example: You can become a Certified Scrum Master in Nigeria.
Scrum Master Checklist: - Understands the role - Coaches the team - Facilitates events - Removes obstacles - Protects the team - Serves the team
Mini summary: You are now a Scrum Master!
| Word | Simple Definition |
|---|---|
| Scrum Master | Coach for the team. |
| Servant Leader | A leader who serves the team. |
| Facilitate | Make something easier. |
| Coach | Teach and guide. |
| Obstacle | A blocker or problem. |
| Protect | Shield from harm. |
| Empathy | Understanding others' feelings. |
| Self-organise | Organise without being told. |
| Collaborate | Work together. |
| Practitioner | Someone who practices a skill. |
Scrum Master
|
+-- Coach
|
+-- Facilitator
|
+-- Servant Leader
|
+-- Obstacle Remover
|
+-- Protector
Facilitate Events
|
V
Coach the Team
|
V
Remove Obstacles
|
V
Protect the Team
|
V
Serve the Team
+-----------------------+-----------------------+ | Scrum Master | Project Manager | +-----------------------+-----------------------+ | Coach | Manager | | Facilitates | Directs | | Serves team | Manages resources | | Removes obstacles | Manages risks | | Empowers team | Controls team | | Servant leader | Traditional leader | +-----------------------+-----------------------+
| Responsibility | Description | Example |
|---|---|---|
| Facilitate | Run Scrum events | Sprint planning |
| Coach | Teach Scrum | Explain roles |
| Remove obstacles | Clear blockers | Fix a problem |
| Protect | Shield the team | Stop interruptions |
| Serve | Support the team | Help the team improve |
| Skill | Description | Example |
|---|---|---|
| Communication | Speak and listen | Clear instructions |
| Facilitation | Run meetings | Effective stand-ups |
| Coaching | Teach and guide | Help the team learn |
| Empathy | Understand others | Support the team |
| Problem-solving | Find solutions | Remove obstacles |
(Included after each lesson above – review them!)
In this module, you learned about the Scrum Master role. You discovered that a Scrum Master is a coach, facilitator, and servant leader. You learned about their responsibilities – facilitating events, coaching the team, removing obstacles, and protecting the team. You also learned about the skills needed and the difference between a Scrum Master and a Project Manager. You are now a Scrum Master. In the next module, you will learn about Scrum values. Congratulations on completing Module Three!
Match the term with its definition.
| Term | Definition |
|---|---|
| 1. Scrum Master | A. Coach for the team |
| 2. Servant Leader | B. Puts team first |
| 3. Facilitate | C. Make easier |
| 4. Coach | D. Teach and guide |
| 5. Obstacle | E. A blocker |
Answers: 1-A, 2-B, 3-C, 4-D, 5-E
“Scrum Master Simulation”
In groups, simulate a Scrum Master role. Practice facilitating a sprint planning, daily stand-up, and retrospective. Present your experience to the class.
“My Scrum Master Plan”
Create a plan for being a Scrum Master. Include how you will facilitate, coach, remove obstacles, and protect the team. Share your plan with the class.
“Scrum Master Project”
Create a Scrum Master plan for a team. Include facilitation, coaching, obstacle removal, and protection. Present your plan to the class.
“Scrum Master Practice”
Apply the Scrum Master role to a real team. Facilitate a meeting, coach the team, or remove an obstacle. Share your experience with the class.
“Scrum Master Challenge”
Create a comprehensive Scrum Master plan for a complex team. Include facilitation, coaching, obstacle removal, and protection. Share your solution with the class.
(Answers to fill-in-the-blank, true/false, and multiple choice are provided within those sections.)
In Module Four, you will learn about Scrum values. To prepare:
Get ready to learn about Scrum values!
End of Module Three · You are now a Scrum Master!
Welcome, young Scrum Master! In this module, you will learn about the Sprint — the heart of Scrum — and the Daily Scrum, a short meeting that keeps the team moving forward every day.
Imagine you are building a giant LEGO castle. You don’t build it all in one day. You work in small steps, check your progress, and make changes. That is exactly what a Sprint does!
By the end of this module, you will know how to plan a Sprint, how to run a Daily Scrum, and how to help your team stay happy and productive. Let’s begin!
Once upon a time, in a village called Scrumville, a group of children decided to build a magic garden for the whole village. They had 30 days to finish. But the garden was huge!
Instead of worrying, the children said: “Let’s split the work into small pieces.” They decided to work in one‑week Sprints.
Every Monday, they planned what to do that week. Every morning, they met for 5 minutes under the big baobab tree to say: “What did I do yesterday? What will I do today? Any problem?”
At the end of each week, they showed their progress to the village chief. The chief loved it! They built the garden step by step, and it became the most beautiful garden in Nigeria. 🌿
This is exactly how Scrum works — Sprints and Daily Scrums help us build amazing things without getting lost.
Definition: A Sprint is a fixed period of time (usually 1‑4 weeks) where the team does work to create a usable product piece.
Why important? It gives the team a small goal to focus on, so they don’t feel overwhelmed.
Simple explanation: Think of a Sprint like a round in a video game. You have a set time to achieve something, then you check your score.
Real‑life example: A baker makes 100 loaves of bread in one morning — that’s her Sprint.
School example: Your class has one week to read a short book and make a poster.
Home example: You and your sibling clean your room in 30 minutes — that’s a mini‑Sprint.
Nigerian example: A tailor in Lagos cuts and sews 10 Ankara dresses in 5 days — each day is a small Sprint.
Sprint (1‑4 weeks) ┌───────────────────┐ │ Plan → Do → Show │ └───────────────────┘
Mini summary: A Sprint is a short, focused work period.
Definition: The time length of a Sprint. Most teams choose 2 weeks.
Why important? If it’s too long, we might get bored. If too short, we rush. 2 weeks is just right.
Simple explanation: Like the length of a school holiday — not too short, not too long.
Example: A team building a mobile app uses 2‑week Sprints.
Nigerian example: A small farm plants maize in a 2‑week planting Sprint.
Mini summary: Sprints are usually 2 weeks, but can be 1‑4 weeks.
Definition: The Sprint Goal is one sentence that explains what the team wants to achieve during the Sprint.
Why important? It gives the team a clear target.
Simple explanation: Like a finish line in a race.
Example: “We will finish the login page of our game.”
Mini summary: Every Sprint has one goal.
Definition: A meeting at the start of a Sprint where the team decides what work they will do.
Why important? Without planning, we don’t know where to start.
Simple explanation: Like making a grocery list before going to the market.
Nigerian example: A family plans their weekly meals on Sunday morning.
Sprint Planning ┌─────────────┐ │ What to do? │ │ How to do? │ │ Who does? │ └─────────────┘
Mini summary: Plan before you start.
Definition: A 15‑minute meeting every day, where the team answers three questions:
Why important? It helps everyone know what’s happening and who needs help.
Simple explanation: Like a morning check‑in with your friends before playing.
Home example: At breakfast, your family shares their plans for the day.
Nigerian example: A market woman checks with her helpers every morning about which goods to sell.
Mini summary: Daily Scrum = 15 min, 3 questions.
Definition: Only the developers (team members) speak. The Scrum Master helps if there are problems.
Why important? It’s a team meeting, not a boss meeting.
Simple explanation: It’s like players talking on the field, not the coach.
Mini summary: Daily Scrum is for the team.
Definition: A list of tasks the team will work on during the Sprint. It comes from the Product Backlog.
Why important? It shows exactly what we are building now.
Simple explanation: Like a to‑do list for the week.
Nigerian example: A school club’s list of activities for the cultural festival.
Sprint Backlog ┌──────────────────────┐ │ 1. Design banner │ │ 2. Write script │ │ 3. Practice dance │ └──────────────────────┘
Mini summary: Sprint Backlog = our current tasks.
Definition: During the Sprint, we check our work (inspect) and make changes (adapt) to do better.
Why important? It helps us fix problems early.
Simple explanation: Like tasting the stew while cooking to add salt.
Mini summary: Check often and improve.
Definition: A meeting at the end of the Sprint where the team shows what they built to stakeholders.
Why important? People see our work and give feedback.
Simple explanation: Like show‑and‑tell at school.
Nigerian example: A fashion designer shows the finished clothes to the customer.
Mini summary: Sprint Review = show your work.
Definition: A meeting after the Sprint where the team talks about what went well, what could be better, and what to improve next Sprint.
Why important? It helps the team become better every time.
Simple explanation: Like after a game, talking about what you did well and what to practice.
Mini summary: Retrospective = learn and improve.
The Product Owner helps the team understand what is most important to build. They attend the Sprint Planning and Review.
Mini summary: PO gives guidance.
The Scrum Master helps the team stay focused, removes blocks, and teaches Scrum.
Mini summary: SM is a helper.
Very rarely, a Sprint can be stopped if the goal becomes useless. Only the Product Owner can cancel.
Mini summary: Cancelling is rare.
It is for the team to coordinate, not to report to the boss. We talk about work, not people.
Mini summary: Daily Scrum = team coordination.
Every event in Scrum has a maximum time. For example, Daily Scrum is 15 minutes. This is called timeboxing.
Why important? It keeps meetings short and focused.
Example: Like setting a 10‑minute timer for a game.
Mini summary: Timebox = fixed time.
Sprint Flow
┌─────────────┐ ┌──────────────┐ ┌─────────────┐ ┌─────────────┐
│ Planning │────▶│ Daily Work │────▶│ Review │────▶│Retrospective│
└─────────────┘ └──────────────┘ └─────────────┘ └─────────────┘
▲ │ ▲ │ │
└───────────────────┴─────────────────────┴───────────────────┘
| Event | Timebox | Who attends? |
|---|---|---|
| Sprint Planning | Max 8 hours (2‑week Sprint) | Team + PO |
| Daily Scrum | 15 minutes | Developers |
| Sprint Review | Max 4 hours | Team + PO + Stakeholders |
| Sprint Retrospective | Max 3 hours | Team |
| Sprint (Agile) | Waterfall |
|---|---|
| Small pieces, quick feedback | One big piece, slow feedback |
| Change is welcome | Change is difficult |
| Team decides | Boss decides |
(Each lesson above includes a mini summary.)
In this module, you learned about the Sprint – the heartbeat of Scrum. A Sprint is a short, fixed period where the team works towards a Sprint Goal. You also learned about the Daily Scrum, a 15‑minute meeting where the team coordinates. We covered the Sprint Backlog, inspect and adapt, and the important events: Planning, Daily Scrum, Review, and Retrospective.
Remember: Sprints help us build things step by step, and the Daily Scrum keeps us connected every day. These practices make teams happy and productive!
| Term | Match with |
|---|---|
| 1. Sprint | A. 15‑minute daily meeting |
| 2. Daily Scrum | B. Shows work to stakeholders |
| 3. Sprint Review | C. Improve the team process |
| 4. Retrospective | D. Fixed work period |
Answers: 1‑D, 2‑A, 3‑B, 4‑C
Scenario: Your team is building a website for a school. It is Day 3 of a 2‑week Sprint. During the Daily Scrum, Chidi says: “I finished the homepage yesterday. Today I will work on the contact page. I am blocked because I don’t have the pictures.”
Question: What should the team do?
Answer: The team should help Chidi get the pictures, or adjust the plan so he can work on something else.
In groups of 5, role‑play a Daily Scrum for a project to build a school garden. Each person says their yesterday, today, and blockers. The Scrum Master helps remove blockers.
Write down your personal Sprint Goal for the next 2 weeks (e.g., reading a book or finishing a drawing). List 3 tasks in your Sprint Backlog.
Plan a 1‑week Sprint to organize a cultural day in your school. Create a Sprint Goal, a Sprint Backlog, and assign tasks to team members.
Run a Daily Scrum with your family for 3 days. Each day, ask the three questions at breakfast. Write down what you learned.
Imagine a Sprint is cancelled. What steps would you take to restart? Write a short plan.
(Answers are provided within the Multiple Choice and Matching sections above.)
In the next module, we will dive into Scrum Artifacts – the Product Backlog, Sprint Backlog, and Increment. You will learn how to manage these lists and keep them clean. For now, practice your Daily Scrum skills and get ready to become a true Scrum Master!
🎉 Congratulations! You have completed Module Four. Keep up the great work!
Hello again, future Scrum Master! In this module, we will explore the three Scrum Artifacts. Think of artifacts as treasure boxes that hold all the important information about your project. They help everyone see what is done, what is next, and how the work is going.
Imagine you are planning a big birthday party. You have a list of everything you want (cake, games, guests). You have a list of what you will do today. And you have the actual party that is slowly coming together. These are your three treasures!
By the end of this module, you will know the Product Backlog, the Sprint Backlog, and the Increment. You will understand how they work together and why they are so important.
In a small village in Nigeria, there was a wise old woman named Mama Nkechi. She told the children: “I have hidden three treasures in this village. Each treasure will help you build anything you dream of.”
The children were excited! They found the first treasure – a big scroll with a list of all the things they wanted to build: a well, a school, a playground, and a clinic. This was the Product Backlog – the big wish list.
The second treasure was a small chalkboard that said: “What we will do this week.” This was the Sprint Backlog – the weekly plan.
The third treasure was a golden brick. Mama Nkechi said: “Each time you finish a piece of work, add it to the building. The finished parts are your Increment.”
The children used the scroll to decide what to build, the chalkboard to plan their week, and the golden bricks to show their progress. Soon, they built a beautiful school! The three treasures worked together perfectly.
Definition: The Product Backlog is a list of everything that might be needed in the product. It is ordered by importance.
Why important? It helps the team know what to work on next. It is the single source of truth.
Simple explanation: Like a shopping list for your project. You write down everything you want, then you decide which is most important.
Real‑life example: A restaurant menu – all the dishes they could make, but they only cook a few each day.
School example: A list of all topics you want to learn in a term.
Home example: A wish list of toys you want for your birthday.
Nigerian example: A farmer’s list of all crops they could plant (yam, cassava, maize) – but they choose the most important ones for the season.
Product Backlog (wish list) ┌─────────────────────────────┐ │ 1. Build a well (important) │ │ 2. Build a school │ │ 3. Build a playground │ │ 4. Build a clinic │ └─────────────────────────────┘
Mini summary: Product Backlog = big list of all desired features.
Definition: The Product Owner owns the Product Backlog. They add, remove, and order items.
Why important? One person makes sure the list is clear and valuable.
Simple explanation: Like a parent who decides which groceries are most needed.
Mini summary: The Product Owner is the caretaker of the Product Backlog.
Definition: Each item in the Product Backlog is called a Product Backlog Item (PBI). It can be a feature, a fix, or an improvement.
Simple explanation: Like each toy on your wish list is one item.
Example: “Add a login button” is a PBI.
Mini summary: PBIs are single pieces of work.
Definition: Items are ordered from most important to least important. The most important items are at the top.
Why important? The team always works on the highest value items first.
Simple explanation: Like putting your favourite subjects at the top of your study list.
Top (most important) ┌─────────────────────────────┐ │ 1. Safety feature │ │ 2. Login page │ │ 3. Profile picture │ │ 4. Fancy background │ (least important) └─────────────────────────────┘
Mini summary: Order = importance.
Definition: The team and Product Owner meet to review and update the Product Backlog. They add details, estimate, and reorder.
Why important? Keeps the backlog clean and ready for planning.
Simple explanation: Like cleaning your room so you can find things easily.
Nigerian example: A market woman arranges her goods so the best ones are at the front.
Mini summary: Backlog Refinement = tidy up the list.
Definition: The Sprint Backlog is a list of tasks the team will work on during the current Sprint. It is chosen from the Product Backlog.
Why important? It shows the team’s plan for the Sprint.
Simple explanation: Like your homework list for this week.
Real‑life example: A chef’s list of dishes to cook today.
Nigerian example: A tailor’s list of 5 Ankara dresses to sew this week.
Sprint Backlog (this week’s plan) ┌─────────────────────────────┐ │ 1. Design login page │ │ 2. Write login code │ │ 3. Test login button │ │ 4. Fix any bugs │ └─────────────────────────────┘
Mini summary: Sprint Backlog = the current Sprint’s to‑do list.
Definition: The Development Team creates the Sprint Backlog during Sprint Planning. They choose the items they can finish.
Why important? The team knows best what they can do.
Simple explanation: Like you choosing your own chores for the day.
Mini summary: The team owns the Sprint Backlog.
Definition: During the Sprint, the team can add or remove tasks as long as the Sprint Goal stays the same.
Why important? It allows the team to adapt to new information.
Simple explanation: Like changing your plan if it starts raining and you need to play indoors.
Mini summary: Sprint Backlog can change, but goal stays.
Definition: The Increment is the sum of all the work done during the Sprint plus all previous Sprints. It must be “Done” – meaning it is usable.
Why important? It shows the real progress of the product.
Simple explanation: Like the parts of a LEGO castle you have already built and can play with.
Real‑life example: A new feature in a game that players can actually use.
Nigerian example: A finished batch of puff‑puff that is ready to sell.
Increment = All Done work ┌─────────────────────────────┐ │ Sprint 1: Login page │ │ Sprint 2: Profile page │ │ Sprint 3: Settings page │ │ = Complete user area │ └─────────────────────────────┘
Mini summary: Increment = finished, usable product pieces.
Definition: The team agrees on what “Done” means for every item. It is a checklist of quality standards.
Why important? Everyone knows when work is truly finished.
Simple explanation: Like knowing that “clean room” means toys put away, bed made, floor swept.
Example: “Done” for a code feature might mean: code written, tested, and reviewed.
Mini summary: Definition of Done = quality checklist.
Definition: The Product Backlog feeds the Sprint Backlog, and the Sprint Backlog produces the Increment.
Why important? They work as a system to build the product step by step.
Product Backlog (big list)
│
▼
Sprint Backlog (this Sprint’s plan)
│
▼
Increment (finished work)
Mini summary: They are connected like a river flowing to the sea.
Definition: All artifacts are visible to everyone. No secrets.
Why important? Everyone can see progress and make good decisions.
Simple explanation: Like a glass jar – you can see how many cookies are left.
Mini summary: Artifacts are open for all to see.
Definition: The team commits to achieving the Sprint Goal, not just to finishing the Sprint Backlog.
Why important? It keeps the team focused on value, not just tasks.
Mini summary: Focus on the goal, not just the list.
Definition: During the Daily Scrum, the team updates the Sprint Backlog to show what is done and what remains.
Why important? It gives a clear picture of progress.
Mini summary: Keep the Sprint Backlog fresh every day.
Definition: Every Increment is a step towards the final product. It must be in a usable state, even if the product isn’t complete.
Why important? We can release it at any time if we want.
Simple explanation: Like baking a cake – after each step, the cake is edible, even if we still add icing later.
Mini summary: Each Increment is potentially shippable.
Artifact Flow
┌─────────────────────┐
│ Product Backlog │ (Big list)
└──────────┬──────────┘
│
▼
┌─────────────────────┐
│ Sprint Backlog │ (This Sprint's tasks)
└──────────┬──────────┘
│
▼
┌─────────────────────┐
│ Increment │ (Finished work)
└─────────────────────┘
| Artifact | Owner | Content | Changes |
|---|---|---|---|
| Product Backlog | Product Owner | All desired features | Refined continuously |
| Sprint Backlog | Development Team | Tasks for current Sprint | Can be updated daily |
| Increment | Development Team | Finished, usable work | Added each Sprint |
Timeline
Sprint 1 Sprint 2 Sprint 3
┌─────────┐ ┌─────────┐ ┌─────────┐
│Product │ │Product │ │Product │
│Backlog │ │Backlog │ │Backlog │
└────┬────┘ └────┬────┘ └────┬────┘
│ │ │
▼ ▼ ▼
┌─────────┐ ┌─────────┐ ┌─────────┐
│Sprint │ │Sprint │ │Sprint │
│Backlog │ │Backlog │ │Backlog │
└────┬────┘ └────┬────┘ └────┬────┘
│ │ │
▼ ▼ ▼
┌─────────┐ ┌─────────┐ ┌─────────┐
│Increment│ │Increment│ │Increment│
│ (v1) │ │ (v2) │ │ (v3) │
└─────────┘ └─────────┘ └─────────┘
(Each lesson above includes a mini summary.)
In this module, you learned about the three Scrum Artifacts – the Product Backlog, the Sprint Backlog, and the Increment. The Product Backlog is a big list of everything the product could have, ordered by importance. The Product Owner takes care of it. The Sprint Backlog is the team’s plan for the current Sprint, made up of tasks selected from the Product Backlog. The Increment is the sum of all the work done so far – it must be “Done” and usable.
We also learned about Definition of Done, Backlog Refinement, and how all three artifacts are transparent. They work together like a recipe, a shopping list, and the cooked meal. These artifacts keep the project clear and focused.
| Artifact | Description |
|---|---|
| 1. Product Backlog | A. This week’s work plan |
| 2. Sprint Backlog | B. Finished, usable product pieces |
| 3. Increment | C. The big wish list |
Answers: 1‑C, 2‑A, 3‑B
Scenario: Your team is building a mobile game. The Product Backlog has 50 items. The team is in Sprint Planning and they pick the top 5 items. They break them into 15 tasks and put them in the Sprint Backlog. After the Sprint, they have 10 tasks finished and 5 not done. The Increment includes only the finished tasks.
Question: What should the team do with the 5 unfinished tasks? What should they do to avoid this in the future?
Answer: The unfinished tasks go back to the Product Backlog. To avoid this, the team should be more careful when choosing the number of items for the Sprint Backlog, and make sure they understand the Definition of Done.
In groups of 4, create a Product Backlog for a “School Sports Day” (at least 10 items). Then, choose 3 items for a Sprint Backlog and break them into tasks. Finally, define what “Done” means for each item. Present your work to the class.
Draw a picture showing the three artifacts as a river: Product Backlog at the top, Sprint Backlog in the middle, and Increment at the bottom. Label each part.
Plan a project to build a small garden. Create a Product Backlog with at least 8 items (e.g., buy seeds, prepare soil, plant, water, etc.). Then, create a Sprint Backlog for the first week (choose 3 items). Define “Done” for each item. Show how the Increment grows each week.
Find a Product Backlog in real life – for example, your school’s list of events for the term. Write down 5 items and order them by importance. Then, choose 2 items for a “Sprint” and list the tasks you would do.
Imagine you are the Product Owner for a new app. The stakeholders want 20 new features. But your team can only do 5 features in the next Sprint. How do you decide which 5 to choose? Write your decision process and explain it.
(Answers are provided within the Multiple Choice and Matching sections above.)
In the next module, we will dive into Scrum Roles and Responsibilities – the Product Owner, Scrum Master, and Development Team. You will learn exactly what each role does and how they work together. We will also explore how to choose the right people for each role. For now, practice creating and ordering backlogs in your daily life. You are doing great!
🎉 Congratulations! You have completed Module Five. Keep learning and growing as a Scrum Master!
Welcome, young Scrum Master! In this module, you will meet the three heroes of every Scrum team: the Product Owner, the Scrum Master, and the Development Team. Together, they are called the Scrum Team.
Think of a football team. You have a captain (Product Owner), a coach (Scrum Master), and the players (Development Team). Each person has a special job, but they all work together to win the match.
By the end of this module, you will know exactly what each role does, why they are important, and how they help each other. You will also learn how to be a great team member in any project!
In a bustling city in Nigeria, there were three best friends: Ada, Chidi, and Kofi. They decided to build a community library for their neighbourhood.
Ada was very organized. She knew exactly what books, furniture, and decorations they needed. She made a big list and decided what was most important. Ada was the Product Owner.
Chidi was a great helper. He made sure everyone had what they needed. He removed obstacles (like broken tools) and made sure the team followed their plan. Chidi was the Scrum Master.
Kofi was a builder. He could hammer, paint, and arrange shelves. He worked with other volunteers to actually build the library. Kofi was part of the Development Team.
Together, they built a beautiful library in just three months. Each friend had a different job, but they all shared the same goal. That’s how a Scrum Team works!
Definition: The Scrum Team is a small group of people who work together to build the product. It has three roles: Product Owner, Scrum Master, and Development Team.
Why important? Each role has a special job, which makes the team effective.
Simple explanation: Like a pizza shop – someone takes orders (Product Owner), someone manages the kitchen (Scrum Master), and someone makes the pizza (Development Team).
Real‑life example: A school project – one student researches, one organizes, one presents.
Home example: Family cleaning day – one person plans, one person leads, and others do the cleaning.
Nigerian example: A wedding planning committee – chief planner (Product Owner), coordinator (Scrum Master), and decorators/cooks (Development Team).
Scrum Team ┌─────────────────────────────┐ │ Product Owner │ │ Scrum Master │ │ Development Team │ └─────────────────────────────┘
Mini summary: Scrum Team = three roles working together.
Definition: The Product Owner (PO) is the person who decides what the team will build and in what order.
Why important? The PO makes sure the team builds the most valuable things.
Simple explanation: Like the captain of a ship – they decide which direction to go.
Real‑life example: A chef who decides the menu for the week.
School example: The class president who decides which activities to do first.
Home example: A parent who decides what groceries to buy.
Nigerian example: The head of a market association who decides which goods to promote.
Mini summary: Product Owner = decision‑maker for value.
Definition: The PO manages the Product Backlog, orders items, and makes sure everyone understands the work.
Why important? They ensure the team works on the right things.
Simple explanation: Like a teacher who gives homework – they decide what is most important to learn.
Key tasks:
Mini summary: PO = Product Backlog caretaker.
Definition: The Scrum Master (SM) is a helper and coach. They make sure everyone understands Scrum and follows its rules.
Why important? The SM removes obstacles and helps the team work smoothly.
Simple explanation: Like a referee in a game – they make sure the rules are followed and the game is fair.
Real‑life example: A sports coach who helps players improve.
School example: A teacher’s assistant who helps classmates with questions.
Home example: An older sibling who helps younger ones with chores.
Nigerian example: A community leader who resolves disputes and keeps peace.
Mini summary: Scrum Master = coach and helper.
Definition: The SM helps the team follow Scrum, removes blockers, and protects the team from outside interruptions.
Why important? They keep the team happy and productive.
Simple explanation: Like a lifeguard – they watch for problems and keep everyone safe.
Key tasks:
Mini summary: SM = removes obstacles and teaches Scrum.
Definition: The Development Team is the group of people who actually build the product. They do the hands‑on work.
Why important? Without them, nothing gets built!
Simple explanation: Like the players on a football field – they score the goals.
Real‑life example: Bakers who make the bread.
School example: Students who work on a group project.
Home example: Family members who do the cleaning and cooking.
Nigerian example: Farmers who plant and harvest crops.
Mini summary: Development Team = the builders.
Definition: The Development Team is self‑organizing, cross‑functional, and accountable for the work.
Why important? They can solve problems without being told.
Simple explanation: Like a group of friends building a fort – they decide who does what.
Key points:
Mini summary: Development Team = capable and responsible.
Definition: A Scrum Team is usually between 3 and 9 members (including PO and SM).
Why important? Small enough to be agile, large enough to get work done.
Simple explanation: Like a group of friends – too few, you can’t do much; too many, it gets chaotic.
Mini summary: Scrum Team = 3‑9 people.
Definition: The PO decides what to build, but the team decides how to build it.
Why important? It gives the team freedom to be creative.
Simple explanation: The PO says “build a house”, but the team decides the colour and materials.
Mini summary: PO = what; Team = how.
Definition: The SM does not manage people. They help the team manage themselves.
Why important? The team is empowered to make their own decisions.
Simple explanation: The SM is like a gardener – they water and care, but the plants grow on their own.
Mini summary: SM = servant‑leader, not boss.
Definition: The three roles work closely together. They communicate daily and help each other.
Why important? Good collaboration leads to better products.
Simple explanation: Like a band – the guitarist, drummer, and singer listen to each other and play together.
Collaboration
Product Owner ←→ Scrum Master
↕ ↕
Development Team
Mini summary: All roles work as one team.
Definition: No one is more important than the others. All roles are essential.
Why important? Everyone’s contribution is valued.
Simple explanation: Like a bicycle – the wheels, pedals, and handlebars all need to work together.
Mini summary: Every role is important.
Definition: Stakeholders are people who care about the product but are not on the Scrum Team (e.g., customers, managers).
Why important? The team gets feedback from stakeholders, but the team makes the final decisions.
Simple explanation: Stakeholders are like fans of a football team – they cheer, but the players play.
Mini summary: Stakeholders = interested people outside the team.
Definition: The Development Team is responsible for delivering a Done Increment every Sprint.
Why important? They own the quality of the product.
Simple explanation: Like a chef who takes responsibility for the taste of the food.
Mini summary: Team owns the Increment.
Definition: A great Scrum Team is respectful, collaborative, and focused on the goal.
Why important? It makes work fun and successful.
Simple explanation: Like a group of best friends working on a project – they trust and help each other.
Mini summary: Great teams = trust + collaboration.
The Scrum Team
┌─────────────────────────────┐
│ Product Owner │
│ (decides WHAT to build) │
└──────────────┬──────────────┘
│
┌──────────────┴──────────────┐
│ Scrum Master │
│ (coach & obstacle remover)│
└──────────────┬──────────────┘
│
┌──────────────┴──────────────┐
│ Development Team │
│ (builds the product) │
└─────────────────────────────┘
| Role | Main Responsibility | Key Activity |
|---|---|---|
| Product Owner | Maximize value | Manage Product Backlog |
| Scrum Master | Facilitate Scrum | Remove obstacles |
| Development Team | Deliver Done Increment | Build product |
| Traditional Manager | Scrum Master |
|---|---|
| Tells people what to do | Helps team decide |
| Assigns tasks | Facilitates self‑organization |
| Focuses on control | Focuses on empowerment |
(Each lesson above includes a mini summary.)
In this module, you learned about the three Scrum roles that form the Scrum Team. The Product Owner decides what to build and manages the Product Backlog. The Scrum Master is a coach and helper who removes obstacles and teaches Scrum. The Development Team is a group of skilled people who actually build the product.
We discovered that all roles are equally important and work together like a band. The team is self‑organizing, cross‑functional, and accountable for delivering a Done Increment every Sprint. We also learned that the Scrum Master is not a boss, and the Product Owner doesn’t tell the team how to work.
With this knowledge, you can now identify these roles in any team and understand how they contribute to success.
| Role | Responsibility |
|---|---|
| 1. Product Owner | A. Removes obstacles |
| 2. Scrum Master | B. Builds the product |
| 3. Development Team | C. Manages Product Backlog |
Answers: 1‑C, 2‑A, 3‑B
Scenario: Your team is building a website. The Product Owner keeps changing the requirements, and the team is confused. The Scrum Master notices that the PO is not available for questions. The Development Team is frustrated because they don’t know what to work on.
Question: What should the Scrum Master do? What can the team do to help?
Answer: The Scrum Master should talk to the Product Owner and help them be more available. The team can also ask clear questions and suggest ways to make the backlog clearer.
In groups of 4, assign one person as Product Owner, one as Scrum Master, and two as Development Team. Plan a “mini‑project” (e.g., a class magazine). The PO creates a backlog, the SM helps plan, and the team decides how to do the work. Present your plan to the class.
Write a short paragraph describing which Scrum role you would like to have and why. Explain what you would do in that role.
Form a Scrum Team of 3‑5 people. Choose a simple project (e.g., a class newsletter). Define the roles (PO, SM, Dev Team). Create a Product Backlog, plan a Sprint, and build a small piece of the product. Present your work.
Observe a team at school or home (e.g., a group project or family chore). Identify who acts like the Product Owner, Scrum Master, and Development Team. Write a short report on what you observed.
Imagine you are the Scrum Master for a team that keeps missing the Sprint Goal. List three things you would do to help the team succeed. Explain why each action would help.
(Answers are provided within the Multiple Choice and Matching sections above.)
In the next module, we will explore Scrum Events and Ceremonies – Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. You will learn how to run each event effectively and why they are important. For now, practice identifying roles in your daily activities and think about how you can be a great team member. You are becoming a true Scrum Master!
🎉 Congratulations! You have completed Module Six. Keep shining!
Hello, Scrum Champion! In this module, we will explore the five Scrum events (sometimes called ceremonies). These are meetings that help the team plan, check progress, and improve. Think of them as the heartbeat of Scrum – they keep the team alive and moving forward.
Imagine you are cooking a big meal. You plan what to cook, check the food while it’s cooking, taste it, and then clean up. Scrum events are like that – they help you cook a perfect product!
By the end of this module, you will know all about Sprint Planning, the Daily Scrum, Sprint Review, Sprint Retrospective, and the Sprint itself. You will know how to run each event and why they matter.
In a small village in Nigeria, the elders decided to organize a big festival. They formed a committee to plan everything.
First, they held a planning meeting where they decided what they needed: food, music, decorations, and games. This was like Sprint Planning.
Every morning, the committee met for 15 minutes to share what they did yesterday, what they would do today, and any problems. This was their Daily Scrum.
At the end of the week, they showed their progress to the village chief – the food was ready, the music was arranged. This was the Sprint Review.
After the festival, they sat together and discussed what went well and what could be better. That was their Retrospective.
The whole week of preparation was one Sprint. The events helped them stay organized and successful!
Definition: Scrum events are meetings that happen during a Sprint. They help the team plan, check, and improve.
Why important? Without these events, the team might get lost or make mistakes.
Simple explanation: Like checkpoints in a race – they make sure you’re on the right track.
Real‑life example: A school has regular staff meetings to plan lessons and solve problems.
Home example: Family meetings to plan the week and discuss issues.
Nigerian example: A market union meets weekly to discuss prices and logistics.
Scrum Events ┌─────────────────────────────┐ │ 1. Sprint (the container) │ │ 2. Sprint Planning │ │ 3. Daily Scrum │ │ 4. Sprint Review │ │ 5. Sprint Retrospective │ └─────────────────────────────┘
Mini summary: Scrum events = essential meetings.
Definition: The Sprint is a fixed‑length period (1‑4 weeks) during which the team builds an Increment. All other events happen inside the Sprint.
Why important? It gives the team a consistent rhythm.
Simple explanation: Like a school term – you have classes, exams, and holidays within a term.
Mini summary: Sprint = container for all other events.
Definition: Sprint Planning is a meeting at the start of the Sprint. The team decides what to build and how to build it.
Why important? It gives the team a clear plan for the Sprint.
Simple explanation: Like making a to‑do list before starting homework.
Real‑life example: A chef plans the menu for the week.
School example: Students plan their study schedule for exams.
Home example: Family plans the week’s meals and activities.
Nigerian example: A farmer plans which crops to plant and when.
Timebox: Max 8 hours for a 2‑week Sprint.
Sprint Planning ┌─────────────────────────────┐ │ 1. What can we do? │ │ 2. How will we do it? │ │ 3. Create Sprint Backlog │ └─────────────────────────────┘
Mini summary: Sprint Planning = decide what and how.
Definition: The Daily Scrum is a 15‑minute meeting every day. The Development Team shares progress and plans.
Why important? It keeps everyone aligned and helps identify problems early.
Simple explanation: Like a morning huddle before a game.
Real‑life example: A hospital shift‑handover where nurses discuss patients.
School example: A quick group check‑in before a project session.
Home example: Family breakfast where everyone shares their plans.
Nigerian example: Market traders meeting briefly each morning to discuss prices.
Timebox: 15 minutes.
Three questions: Yesterday? Today? Blockers?
Daily Scrum (15 min) ┌─────────────────────────────┐ │ 1. What did I do yesterday? │ │ 2. What will I do today? │ │ 3. Any blockers? │ └─────────────────────────────┘
Mini summary: Daily Scrum = 15 min, 3 questions.
Definition: Sprint Review is a meeting at the end of the Sprint where the team shows what they built to stakeholders.
Why important? It gets feedback and shows progress.
Simple explanation: Like show‑and‑tell at school.
Real‑life example: A fashion show where designers display new clothes.
School example: A science fair where students present projects.
Home example: Showing your parents the artwork you made.
Nigerian example: A tailor showing finished clothes to the customer.
Timebox: Max 4 hours for a 2‑week Sprint.
Sprint Review ┌─────────────────────────────┐ │ 1. Team shows Done work │ │ 2. Stakeholders give feedback│ │ 3. Update Product Backlog │ └─────────────────────────────┘
Mini summary: Sprint Review = show and get feedback.
Definition: The Sprint Retrospective is a meeting after the Sprint Review. The team discusses what went well, what could be better, and what to improve.
Why important? It helps the team continuously improve.
Simple explanation: Like after a game, talking about what you did well and what to practice.
Real‑life example: A restaurant team meets after service to discuss the evening.
School example: Students discuss how their group project went and what to do differently.
Home example: Family talks about the week and plans changes.
Nigerian example: A church committee reviews an event and plans improvements.
Timebox: Max 3 hours for a 2‑week Sprint.
Sprint Retrospective ┌─────────────────────────────┐ │ 1. What went well? │ │ 2. What could be better? │ │ 3. What will we improve? │ └─────────────────────────────┘
Mini summary: Retrospective = improve for next Sprint.
Definition: Different events have different attendees.
Why important? The right people need to be there.
Simple explanation: Like a play – actors, director, and audience all have their roles.
| Event | Attendees |
|---|---|
| Sprint Planning | PO, SM, Development Team |
| Daily Scrum | Development Team (SM optional) |
| Sprint Review | PO, SM, Development Team, Stakeholders |
| Retrospective | PO, SM, Development Team |
Mini summary: Each event has specific attendees.
Definition: Every event has a maximum time (timebox).
Why important? Keeps meetings focused and efficient.
Simple explanation: Like a timer for a game – it makes sure you don’t spend too long.
| Event | Timebox (2‑week Sprint) |
|---|---|
| Sprint Planning | 8 hours |
| Daily Scrum | 15 minutes |
| Sprint Review | 4 hours |
| Retrospective | 3 hours |
Mini summary: Timebox = fixed maximum time.
Definition: In Sprint Planning, the team decides the Sprint Goal – one sentence describing what they will achieve.
Why important? It gives focus for the whole Sprint.
Simple explanation: Like a target in archery – you need to know what you’re aiming at.
Mini summary: Sprint Goal = the target.
Definition: The team breaks the selected items into tasks and creates the Sprint Backlog.
Why important? It shows exactly what work needs to be done.
Simple explanation: Like a recipe – you list the ingredients and steps.
Mini summary: Sprint Backlog = task list.
Definition: The Daily Scrum is for coordination, not for solving deep problems.
Why important? It keeps the meeting short.
Simple explanation: Like a quick check‑in – you discuss problems later with the right people.
Mini summary: Daily Scrum = coordination, not problem‑solving.
Definition: Feedback from stakeholders helps the team know if they are on the right track.
Why important? It prevents building the wrong thing.
Simple explanation: Like tasting the soup while cooking – you add salt if needed.
Mini summary: Feedback = valuable.
Definition: The team identifies actions to improve in the next Sprint.
Why important? The team gets better over time.
Simple explanation: Like practising a sport – you get better by fixing mistakes.
Mini summary: Retrospective = improvement plan.
Definition: Every Scrum event must happen. They are not optional.
Why important? They are essential for Scrum to work.
Simple explanation: Like brushing your teeth – you must do it to stay healthy.
Mini summary: Events are required.
Definition: All events happen inside the Sprint. The Sprint is like a box that holds everything.
Why important? It gives structure to the work.
Simple explanation: Like a school day – classes, lunch, and break all happen inside the day.
Mini summary: Sprint = container for events.
Sprint Flow ┌─────────────────────────────────────────────────────────────┐ │ SPRINT (1‑4 weeks) │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌─────┐ │ │ │ Planning │───▶│ Daily │───▶│ Review │───▶│Retro│ │ │ │ │ │ Scrum │ │ │ │ │ │ │ └──────────┘ └──────────┘ └──────────┘ └─────┘ │ └─────────────────────────────────────────────────────────────┘
| Event | When | Timebox | Purpose |
|---|---|---|---|
| Sprint Planning | Start of Sprint | 8 hrs (2‑week) | Plan the Sprint |
| Daily Scrum | Every day | 15 min | Coordinate |
| Sprint Review | End of Sprint | 4 hrs (2‑week) | Get feedback |
| Retrospective | After Review | 3 hrs (2‑week) | Improve |
| Sprint Review | Sprint Retrospective |
|---|---|
| Focus on product | Focus on process |
| Stakeholders attend | Only Scrum Team |
| Shows Done work | Discusses improvements |
| Updates Product Backlog | Creates action plan |
(Each lesson above includes a mini summary.)
In this module, you learned about the five Scrum events. The Sprint is the container for all other events and is a fixed period of 1‑4 weeks. Sprint Planning happens at the start to decide the Sprint Goal and create the Sprint Backlog. The Daily Scrum is a 15‑minute daily meeting for coordination. The Sprint Review at the end of the Sprint is where the team shows their work and gets feedback. Finally, the Sprint Retrospective helps the team improve for the next Sprint.
We also learned about timeboxing – every event has a fixed maximum time to keep meetings efficient. These events work together like a well‑oiled machine, ensuring the team stays on track and continuously improves.
| Event | Purpose |
|---|---|
| 1. Sprint Planning | A. Daily coordination |
| 2. Daily Scrum | B. Show work and get feedback |
| 3. Sprint Review | C. Plan the Sprint |
| 4. Retrospective | D. Improve the process |
Answers: 1‑C, 2‑A, 3‑B, 4‑D
Scenario: Your team has just finished a Sprint. The product works, but stakeholders said the design was confusing. The team is tired and wants to skip the Retrospective.
Question: Why is it important to hold the Retrospective? What should the team do in the Retrospective to address the design issue?
Answer: The Retrospective is important to learn from the Sprint and improve. The team should discuss why the design was confusing and create an action plan to improve it in the next Sprint, such as involving a designer earlier.
In groups of 5, role‑play all four events of a Sprint for a project to build a school garden. One person is PO, one SM, two developers, and one stakeholder. Run Sprint Planning (10 min), a Daily Scrum (3 min), a Sprint Review (5 min), and a Retrospective (5 min).
Draw a timeline of a 2‑week Sprint. Show where each event happens: Sprint Planning, Daily Scrums (mark each day), Sprint Review, and Retrospective.
Form a Scrum Team. Plan a 1‑week Sprint to create a short play or skit. Conduct Sprint Planning, hold a Daily Scrum each day, present the play at the end (Review), and then hold a Retrospective. Document what you learned.
Observe a team in your school or community (e.g., a sports team, a club). Identify which Scrum events they already do (even if they don’t call them that). Write a short report comparing their practices to Scrum events.
You are the Scrum Master for a team that keeps extending the Daily Scrum to 30 minutes. List three strategies you would use to get the team back to 15 minutes. Explain why each strategy would work.
(Answers are provided within the Multiple Choice and Matching sections above.)
In the next module, we will explore Scaling Scrum – how to use Scrum with large projects and multiple teams. You will learn about the Nexus framework and how to coordinate many teams working together. For now, practice running Scrum events with your friends or family. You are becoming a true Scrum Master!
🎉 Congratulations! You have completed Module Seven. Keep the Scrum spirit alive!
Hello, Scrum Leader! So far, you have learned how one Scrum team works. But what if your project is so big that one team is not enough? What if you need 5, 10, or even 50 teams?
This is called Scaling Scrum. It means using Scrum with many teams that work together on the same product. Think of it like a big orchestra – each musician plays their own instrument, but they all follow the same conductor and the same music.
In this module, you will learn about the Nexus framework – a simple way to scale Scrum. You will also learn how to coordinate teams, manage dependencies, and keep everyone aligned.
In a big city in Nigeria, there was a school with 10 classes. The principal wanted to build a giant science exhibition that involved all the classes.
Each class was like a Scrum team. But if each class worked alone, they would make a mess – duplicate exhibits, missing pieces, and confusion.
So the principal formed a “coordination team” made of one teacher from each class. This team met every week to plan together, share what each class was doing, and solve problems. This coordination team was like the Nexus Integration Team.
They created a master list of all the exhibits – this was like the Nexus Sprint Backlog. They made sure no two classes built the same thing and that everything fit together.
The result? A beautiful, coordinated science exhibition that made the whole city proud!
Definition: Scaling Scrum means using Scrum with multiple teams working on one product.
Why important? Some projects are too big for one team. Scaling helps us build bigger products faster.
Simple explanation: Like a big construction site – you need many workers, not just one.
Real‑life example: Building a skyscraper – many teams work together.
School example: A school festival – each class does a different activity.
Home example: A big family wedding – different relatives handle food, music, and decorations.
Nigerian example: Organizing a national festival – many committees work together.
One Team → Many Teams
┌─────────┐ ┌─────────┐
│ Team 1 │ │ Team 2 │
└────┬────┘ └────┬────┘
│ │
└──────┬──────┘
│
┌──────┴──────┐
│ Product │
└─────────────┘
Mini summary: Scaling = many teams for big projects.
Definition: Nexus is a framework for scaling Scrum. It is a simple way to coordinate 3‑9 Scrum teams working on the same product.
Why important? It gives a structured way to work together.
Simple explanation: Like a team of teams – a “super‑team”.
Mini summary: Nexus = scaling framework for up to 9 teams.
Definition: The Nexus Integration Team (NIT) is a small group of people who coordinate the work of all the teams.
Why important? They make sure all teams work together smoothly.
Simple explanation: Like the conductor of an orchestra – they keep everyone in sync.
Who is in the NIT? Usually the Product Owner, Scrum Master, and some developers from each team.
Mini summary: NIT = coordination team.
Definition: A single list that contains all the work for all teams in one Sprint.
Why important? It gives a global view of what everyone is doing.
Simple explanation: Like a master to‑do list for the whole festival.
Nexus Sprint Backlog ┌─────────────────────────────┐ │ Team 1: Login page │ │ Team 2: Profile page │ │ Team 3: Settings page │ │ Team 4: Search feature │ └─────────────────────────────┘
Mini summary: Nexus Sprint Backlog = all teams' tasks in one place.
Definition: A single goal that all teams work towards in a Sprint.
Why important? It unites all teams with a common purpose.
Simple explanation: Like “Let’s all make the festival fun!” – everyone works towards that.
Mini summary: Nexus Sprint Goal = shared objective.
Definition: A meeting where all teams and the NIT plan the work for the next Sprint.
Why important? It ensures that teams don’t duplicate work and that dependencies are managed.
Simple explanation: Like a big group discussion before a group project.
Timebox: Usually longer than a single team's Sprint Planning.
Mini summary: Nexus Sprint Planning = all‑team planning.
Definition: A daily meeting for the NIT to coordinate, not for all teams.
Why important? It keeps the integration team aligned.
Simple explanation: Like a quick check‑in for the conductors.
Mini summary: Nexus Daily Scrum = NIT coordination.
Definition: A joint Sprint Review where all teams show their Increments together.
Why important? Stakeholders see the whole picture.
Simple explanation: Like a big show‑and‑tell with all classes.
Mini summary: Nexus Sprint Review = joint demo.
Definition: A meeting with all teams to improve the overall process.
Why important? It helps the whole system improve, not just individual teams.
Simple explanation: Like a big meeting to discuss how the whole festival went.
Mini summary: Nexus Retrospective = improve the whole system.
Definition: A meeting where the NIT and teams refine the Product Backlog, focusing on cross‑team dependencies.
Why important? It keeps the backlog ready for planning.
Mini summary: Refine = clean and prepare.
Definition: When one team’s work depends on another team’s work.
Why important? If not managed, dependencies can cause delays.
Simple explanation: Like you can’t bake a cake until someone buys the flour.
Example: Team A needs Team B to finish the database before they can build the user interface.
Dependency Team A ────► Team B (needs B's work)
Mini summary: Dependencies = one team needs another.
Definition: The NIT works with teams to plan and track dependencies so they don’t block progress.
Why important? It keeps the project moving smoothly.
Simple explanation: Like making sure the flour arrives before you start baking.
Mini summary: Manage dependencies = avoid delays.
Definition: The process of combining the work of all teams into a single, integrated Increment.
Why important? It ensures the product works as a whole.
Simple explanation: Like putting all the puzzle pieces together.
Mini summary: Integration = combine work.
Definition: The long‑term objective for the Nexus – what the entire group of teams is trying to achieve.
Why important? It gives direction to all teams.
Simple explanation: Like the final destination of a bus – all passengers are going there.
Mini summary: Nexus Goal = shared destination.
Definition: If one team can handle the work, there’s no need to scale.
Why important? Scaling adds complexity, so only do it when necessary.
Simple explanation: Don’t bring a whole orchestra to play a solo.
Mini summary: Only scale when needed.
Nexus Structure
┌─────────────────────────────────────────┐
│ Nexus Integration Team │
│ (PO, SM, + reps from each team) │
└───────────┬─────────────────────────────┘
│
┌───────┴───────┐
│ │
┌───┴───┐ ┌───┴───┐
│Team 1 │ │Team 2 │
└───────┘ └───────┘
│ │
┌───┴───┐ ┌───┴───┐
│Team 3 │ │Team 4 │
└───────┘ └───────┘
| Single Scrum Team | Nexus (Scaled) |
|---|---|
| 1 team | 3‑9 teams |
| 1 Product Backlog | 1 Product Backlog |
| 1 Sprint Backlog | 1 Nexus Sprint Backlog |
| 1 Sprint Goal | 1 Nexus Sprint Goal |
| No integration team | Has Nexus Integration Team |
Nexus Sprint Timeline Week 1 Week 2 ┌──────────────┬──────────────┐ │ Planning │ Work │ │ (all teams) │ (all teams) │ ├──────────────┼──────────────┤ │ Daily NIT │ Daily NIT │ │ coordination │ coordination │ ├──────────────┼──────────────┤ │ │ Review & │ │ │ Retrospective │ └──────────────┴──────────────┘
(Each lesson above includes a mini summary.)
In this module, you learned about Scaling Scrum – how to use Scrum when one team is not enough. The Nexus framework is a simple way to scale with 3‑9 teams. The Nexus Integration Team (NIT) coordinates the work of all teams, manages dependencies, and ensures integration.
Key events in Nexus include the Nexus Sprint Planning (all teams plan together), the Nexus Daily Scrum (for the NIT), the Nexus Sprint Review (joint demo), and the Nexus Sprint Retrospective (improve the whole system).
We also learned about the Nexus Sprint Backlog (the combined tasks) and the Nexus Sprint Goal (shared objective). Scaling adds complexity, so it’s important to only do it when necessary and to manage dependencies carefully.
| Term | Definition |
|---|---|
| 1. Nexus | A. Coordination team |
| 2. NIT | B. Scaling framework |
| 3. Dependency | C. One team needs another's work |
| 4. Integration | D. Combining work |
Answers: 1‑B, 2‑A, 3‑C, 4‑D
Scenario: A company has 5 teams working on a single app. The teams are struggling because they don’t know what the others are doing. Sometimes two teams build the same feature, and sometimes one team waits for another to finish.
Question: How can Nexus help this situation? What should the NIT do?
Answer: Nexus can help by providing a coordination team (NIT) to manage the work. The NIT should create a Nexus Sprint Backlog, hold joint planning, and manage dependencies to avoid duplication and delays.
Divide the class into 3 “teams”. Each team is responsible for building a part of a “robot” (drawing/paper). Form an NIT with one representative from each team. Plan a Sprint together, identify dependencies, and build the robot. At the end, hold a joint Review and Retrospective.
Draw a diagram showing 3 teams working on a project. Show the Nexus Integration Team in the middle. Label the dependencies between the teams.
Form 3 teams and an NIT. Plan a 2‑week Sprint to create a class magazine. Each team handles a section (news, stories, art). The NIT coordinates. Run a Nexus Sprint Planning, work for a week (simulated), hold a Nexus Review, and a Nexus Retrospective.
Observe a large project in your community (e.g., a church event, a market renovation). Identify how many teams are involved and how they coordinate. Write a report comparing their coordination to Nexus.
You are the NIT lead for 4 teams. One team is consistently delayed, causing delays for other teams. List three strategies you would use to help that team catch up without slowing the others. Explain why each strategy is effective.
(Answers are provided within the Multiple Choice and Matching sections above.)
In the next module, we will dive into Scrum in Real Life – how to apply Scrum to everyday projects, overcome common challenges, and build a great team culture. We will also look at tools that help teams manage their work. For now, think about how you could use Nexus in a big project at school or in your community. You are becoming a master of Scrum at any scale!
🎉 Congratulations! You have completed Module Eight. Keep leading and coordinating!
Hello, Scrum Master! You have learned so much! You know the roles, the events, the artifacts, and even how to scale Scrum. Now it’s time to put it all together and see how Scrum works in real life.
This module is like the final exam – but a fun one! We will look at how to apply Scrum to everyday projects, how to handle challenges, and how to build a great team culture. We will also explore tools that help teams manage their work.
Think of this as your Scrum survival guide – everything you need to be a successful Scrum Master in the real world.
Chidi had just finished his Scrum Master training. He was excited to lead his first project – building a community playground in his neighbourhood in Lagos.
He gathered a team of volunteers: architects, builders, and artists. He helped them form a Scrum Team. They created a Product Backlog with all the things they wanted: swings, slides, benches, and a garden.
They planned their first Sprint – building the swings and benches. Chidi held Daily Scrums every morning. When the builders didn’t have enough wood, Chidi helped find a supplier. When the artists argued about the colours, Chidi facilitated a discussion.
At the end of the Sprint, they held a Sprint Review – the neighbourhood children came to test the swings! They were so happy. Then the team held a Retrospective and decided to involve the children earlier in the next Sprint.
In just 3 Sprints, the playground was finished. Chidi learned that Scrum works anywhere – not just in software!
Definition: Scrum is not just for building software. You can use it for any project – school, home, community, or business.
Why important? It’s a flexible framework that works in many situations.
Simple explanation: Like a Swiss Army knife – useful for many things.
Real‑life example: A hospital uses Scrum to improve patient care.
School example: A class uses Scrum to plan a field trip.
Home example: A family uses Scrum to plan a holiday.
Nigerian example: A market association uses Scrum to organize a festival.
Scrum Can Be Used For: ┌─────────────────────────────┐ │ Software │ School │ │ Home │ Community │ │ Business │ Events │ └─────────────────────────────┘
Mini summary: Scrum works anywhere!
Definition: To start, you need a product vision, a Product Owner, a Scrum Master, and a Development Team.
Why important? A strong start leads to a successful project.
Simple explanation: Like building a house – you need a plan and the right people.
Steps:
Mini summary: Start with vision, roles, and backlog.
Definition: A short statement that describes what the product is, who it’s for, and why it’s valuable.
Why important? It gives direction to the whole project.
Simple explanation: Like a destination on a map – you need to know where you’re going.
Example: “A playground that brings joy to every child in our neighbourhood.”
Mini summary: Product Vision = the “why”.
Definition: The Product Backlog is a list of everything the product could have. It is ordered by importance.
Why important? It helps the team focus on the most valuable work.
Simple explanation: Like a shopping list – you buy the most important items first.
Mini summary: Backlog = prioritized list.
Definition: The first Sprint is often the most exciting. The team plans, builds, and delivers the first piece of the product.
Why important? It sets the pace and builds confidence.
Simple explanation: Like the first pancake – it might not be perfect, but it’s a start.
Mini summary: First Sprint = momentum builder.
Definition: Every team faces challenges – like unclear requirements, communication problems, or lack of resources.
Why important? Knowing common challenges helps you prepare for them.
Simple explanation: Like knowing that a road might be bumpy – you can drive carefully.
Common challenges:
Mini summary: Challenges are normal – be ready for them.
Definition: The Scrum Master helps the team overcome challenges by removing obstacles and coaching.
Why important? It keeps the team moving forward.
Simple explanation: Like a mechanic fixing a broken car – you get back on the road.
Solutions:
Mini summary: Help the team overcome obstacles.
Definition: Tools help teams manage their work – like boards, sticky notes, or digital tools.
Why important? They make work visible and organized.
Simple explanation: Like a whiteboard in your room to track homework.
Examples:
Scrum Board ┌──────────┬──────────┬──────────┐ │ To Do │ Doing │ Done │ ├──────────┼──────────┼──────────┤ │ Task 1 │ Task 3 │ Task 5 │ │ Task 2 │ Task 4 │ Task 6 │ └──────────┴──────────┴──────────┘
Mini summary: Tools = make work visible.
Definition: A great team culture is one where people trust each other, communicate openly, and help each other.
Why important? It makes work fun and productive.
Simple explanation: Like a group of best friends – they enjoy working together.
How to build it:
Mini summary: Culture = trust + respect + fun.
Definition: Continuous improvement means always looking for ways to get better – as individuals, as a team, and as a product.
Why important? It’s the heart of Scrum.
Simple explanation: Like practising a sport – you get better every day.
How to practice it:
Mini summary: Always improve – never stop learning.
Definition: Teachers and students can use Scrum for group projects, class activities, and even studying.
Why important? It teaches teamwork and organization.
Simple explanation: Like using Scrum to plan a school play.
Examples:
Mini summary: Scrum is great for schools.
Definition: Families can use Scrum to organize chores, plan vacations, or manage projects.
Why important? It makes family life more organized and fun.
Simple explanation: Like using Scrum to plan a family camping trip.
Examples:
Mini summary: Scrum makes home life easier.
Definition: Community groups can use Scrum to organize events, build projects, or solve problems.
Why important? It helps communities achieve big things together.
Simple explanation: Like using Scrum to build a community garden.
Nigerian example: A neighbourhood uses Scrum to clean up a park.
Mini summary: Scrum helps communities grow.
Definition: A Scrum Master is a servant‑leader – they lead by helping others.
Why important? It creates an environment where everyone can succeed.
Simple explanation: Like a gardener – they care for the plants so they can grow.
Key qualities:
Mini summary: Scrum Master = servant‑leader.
Definition: You have now learned the fundamentals of Scrum. Your journey as a Scrum Master is just beginning.
Why important? You have the knowledge to make a difference.
Simple explanation: Like learning to ride a bike – now you can go anywhere.
Next steps:
Mini summary: Your Scrum journey starts now!
Scrum in Real Life ┌─────────────────────────────────────────┐ │ School │ Home │ Community │ │ Projects │ Chores │ Events │ ├───────────┼──────────┼──────────────────┤ │ Vision │ Vision │ Vision │ │ Backlog │ Backlog │ Backlog │ │ Sprints │ Sprints │ Sprints │ │ Review │ Review │ Review │ │ Retro │ Retro │ Retro │ └─────────────────────────────────────────┘
| Challenge | Solution |
|---|---|
| Unclear backlog items | Refine and clarify with PO |
| Poor communication | Encourage Daily Scrum and open dialogue |
| Scope changes during Sprint | Protect the Sprint Goal |
| Lack of stakeholder feedback | Involve stakeholders in Review |
| Technical issues | Seek expert help early |
| Scrum | Traditional |
|---|---|
| Iterative, flexible | Sequential, rigid |
| Team decides how | Manager decides how |
| Changes welcome | Changes difficult |
| Continuous improvement | Improvement at end |
(Each lesson above includes a mini summary.)
In this module, we explored how to apply Scrum in real life. We learned that Scrum is for everyone – schools, homes, communities, and businesses. We discussed how to start a project with a vision, roles, and a backlog. We also looked at common challenges and how to overcome them.
We discovered tools that help teams stay organized and the importance of building a great team culture. We emphasized continuous improvement – the heart of Scrum. Finally, we explored examples of Scrum in schools, homes, and communities.
Remember, Scrum is a journey, not a destination. Keep learning, keep improving, and keep helping your team succeed!
| Term | Definition |
|---|---|
| 1. Product Vision | A. Always getting better |
| 2. Challenge | B. A problem or difficulty |
| 3. Tool | C. Helps us do work |
| 4. Continuous Improvement | D. What and why of the product |
Answers: 1‑D, 2‑B, 3‑C, 4‑A
Scenario: You are the Scrum Master for a team building a community library. The team is struggling because the Product Owner is not available to answer questions, and the backlog is unclear. The team is losing motivation.
Question: What steps would you take to help the team?
Answer: First, I would talk to the Product Owner about being more available. I would also help the team refine the backlog, perhaps by facilitating a session with the PO. I would hold a team meeting to boost morale and remind them of the vision. Finally, I would suggest a Retrospective to address the issues openly.
In groups of 4, design a Scrum project for a “School Clean‑Up Day”. Create a product vision, a Product Backlog with at least 10 items, and plan the first Sprint. Present your plan to the class.
Write a one‑page guide on how to use Scrum for a family project (e.g., a holiday plan). Include the vision, backlog, Sprint plan, and Retrospective.
Choose a small project (e.g., a class newsletter, a small garden, a talent show). Apply all the Scrum elements: vision, roles, backlog, Sprints, events. Run at least 2 Sprints and document your process. Present your results to the class.
Find a real‑life project in your community (e.g., a church event, a market day). Observe how it is organized. Write a report on how Scrum could be applied to make it better.
You are the Scrum Master for a team that has been using Scrum for 6 months. However, the team is not improving. The Retrospectives are boring, and no one follows up on the action items. List three creative ideas to revitalize the Retrospectives and make them actionable. Explain why each idea would work.
(Answers are provided within the Multiple Choice and Matching sections above.)
In the next module, we will wrap up our Scrum journey with a Final Review and Certification Preparation. We will go over all the key concepts, practice exam questions, and prepare you to become a Certified Scrum Master. You will also create a personal action plan for your Scrum journey.
You are almost there! Keep up the great work, and get ready to become a certified Scrum Master!
🎉 Congratulations! You have completed Module Nine. You are ready for the final step!
Congratulations, Scrum Champion! You have reached the final module of your Certified Scrum Master course. This is where we bring everything together, review all the important concepts, and prepare you to become a Certified Scrum Master.
Think of this module as your grand finale – like the last chapter of a book, the final level of a video game, or the championship match. You have learned all the skills. Now it’s time to show what you know and get ready for the certification exam.
In this module, we will review all the key concepts from Modules 1 to 9, practice exam questions, and create a personal action plan for your Scrum journey. Let’s finish strong!
In a small village in Nigeria, there was a young boy named Ade. He had trained for many months to become a village storyteller. He had learned all the stories, practised his voice, and even helped younger children learn.
On the day of the final test, the village elders gathered. They asked Ade to tell a story that included all the lessons he had learned – teamwork, planning, courage, and kindness.
Ade took a deep breath and told a wonderful story. He didn’t just repeat facts – he showed that he understood the heart of storytelling. The elders were impressed. They declared him the new village storyteller.
Just like Ade, you have learned many things. Now it’s time to show that you understand Scrum, not just memorize it. You are ready!
Definition: Scrum is a framework for building products in small steps. It helps teams work together, inspect their work, and adapt to changes.
Why important? It makes projects more flexible and successful.
Simple explanation: Like building a LEGO castle block by block, checking it often, and changing the plan if needed.
Real‑life example: A team builds a website in small pieces.
School example: Students complete a project in weekly phases.
Home example: Family plans a vacation week by week.
Nigerian example: A market vendor stocks goods based on customer demand.
Scrum Review ┌─────────────────────────────┐ │ Small steps │ │ Team works together │ │ Check and adapt │ └─────────────────────────────┘
Mini summary: Scrum = small steps + teamwork + adaptation.
Definition: The Scrum Team has three roles: Product Owner, Scrum Master, and Development Team.
Why important? Each role has a specific job that helps the team succeed.
Simple explanation: Like a football team – captain (PO), coach (SM), and players (Development Team).
| Role | Main Responsibility |
|---|---|
| Product Owner | Decides what to build |
| Scrum Master | Helps the team follow Scrum |
| Development Team | Builds the product |
Mini summary: Three roles, one team.
Definition: The five Scrum events are: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
Why important? They give structure and rhythm to the work.
| Event | Timebox |
|---|---|
| Sprint | 1‑4 weeks |
| Sprint Planning | 8 hours (2‑week Sprint) |
| Daily Scrum | 15 minutes |
| Sprint Review | 4 hours (2‑week Sprint) |
| Sprint Retrospective | 3 hours (2‑week Sprint) |
Mini summary: Events = plan, coordinate, review, improve.
Definition: The three artifacts are: Product Backlog, Sprint Backlog, and Increment.
Why important? They make work visible and organized.
| Artifact | Description |
|---|---|
| Product Backlog | Big wish list of all features |
| Sprint Backlog | This Sprint's to‑do list |
| Increment | Finished, usable product pieces |
Mini summary: Artifacts = visibility + organization.
Definition: Nexus is a framework for scaling Scrum with 3‑9 teams.
Why important? It helps large projects stay organized.
Key components: Nexus Integration Team, Nexus Sprint Backlog, Nexus Sprint Goal.
Mini summary: Nexus = many teams, one goal.
Definition: The Scrum Master is a servant‑leader who helps the team follow Scrum, removes obstacles, and teaches Scrum.
Why important? They are the key to a successful Scrum implementation.
Key responsibilities:
Mini summary: SM = coach + helper + protector.
Definition: The Product Owner maximizes the value of the product by managing the Product Backlog.
Why important? They ensure the team builds the right things.
Key responsibilities:
Mini summary: PO = value maximizer.
Definition: The Development Team is self‑organizing and cross‑functional. They build the product.
Why important? They are the builders.
Key characteristics:
Mini summary: Dev Team = self‑organizing builders.
Definition: Every Scrum event has a fixed maximum time (timebox).
Why important? It keeps meetings short and focused.
Example: Daily Scrum = 15 minutes.
Mini summary: Timebox = fixed time for each event.
Definition: The Definition of Done is a checklist that everyone agrees on. It says when work is truly finished.
Why important? It prevents confusion about what “done” means.
Example: “Done” means code written, tested, and reviewed.
Mini summary: Definition of Done = quality checklist.
Definition: Continuous improvement means always looking for ways to get better.
Why important? It is the heart of Scrum.
How to practice:
Mini summary: Continuous improvement = always getting better.
Definition: The certification exam tests your understanding of roles, events, artifacts, and principles.
Why important? Knowing the common topics helps you study effectively.
Common topics:
Mini summary: Study roles, events, artifacts, and principles.
Definition: Tips to help you pass the exam.
Why important? They increase your chances of success.
Tips:
Mini summary: Read carefully, think Scrum, trust yourself.
Definition: A plan for what you will do after you become certified.
Why important? It turns your knowledge into action.
Steps:
Mini summary: Plan your next steps.
Definition: You have completed the entire course! That’s a big achievement.
Why important? Celebrating helps you appreciate your hard work.
How to celebrate:
Your Journey ┌─────────────────────────────────────────┐ │ Module 1 → 2 → 3 → 4 → 5 → 6 → 7 → 8 → 9 → 10 │ └─────────────────────────────────────────┘ 🎉 You made it!
Mini summary: Celebrate your success!
Your Scrum Master Journey
┌──────────────────────────────────────────────────┐
│ Learn │ Practice │ Apply │ Master │
└──────────┴────────────┴──────────┴────────────┘
│ │ │ │
▼ ▼ ▼ ▼
Study Find a Use on Become a
modules team projects Certified
Scrum Master
| Topic | Key Concepts |
|---|---|
| Roles | PO, SM, Development Team – responsibilities |
| Events | Sprint, Planning, Daily Scrum, Review, Retrospective – timeboxes |
| Artifacts | Product Backlog, Sprint Backlog, Increment – ownership |
| Principles | Empiricism, self‑organization, transparency |
| Scaling | Nexus, Integration Team, dependencies |
| Scrum | Waterfall |
|---|---|
| Small steps (Sprints) | One big step |
| Change is welcome | Change is difficult |
| Team decides | Manager decides |
| Continuous improvement | Improvement at end |
(Each lesson above includes a mini summary.)
In this final module, we reviewed all the key Scrum concepts: the three roles (Product Owner, Scrum Master, Development Team), the five events (Sprint, Planning, Daily Scrum, Review, Retrospective), and the three artifacts (Product Backlog, Sprint Backlog, Increment). We also revisited scaling with Nexus, timeboxing, the Definition of Done, and continuous improvement.
We discussed the certification exam, common topics, and tips for success. Most importantly, we created a personal action plan to apply Scrum in real life. You have completed the entire course and are now ready to become a Certified Scrum Master.
Remember, Scrum is a journey, not a destination. Keep learning, keep improving, and keep helping your team succeed. You have the knowledge – now go out and make a difference!
| Term | Definition |
|---|---|
| 1. Scrum Master | A. Decides what to build |
| 2. Product Owner | B. Coach and helper |
| 3. Development Team | C. Builds the product |
| 4. Sprint | D. Fixed work period |
Answers: 1‑B, 2‑A, 3‑C, 4‑D
Scenario: You have just become a Certified Scrum Master. Your friend asks you, “What is Scrum and why should I use it?”
Question: How would you explain Scrum to your friend in simple terms?
Answer: I would say, “Scrum is a way of working that helps teams build things in small steps. It has three roles, five events, and three artifacts. It helps teams work together, check their progress, and adapt to changes. It’s like building a LEGO castle block by block, checking it often, and changing the plan if needed.”
In groups of 3‑4, create a “Scrum Master Survival Kit” – a list of tips, tools, and strategies for a new Scrum Master. Present your kit to the class.
Write your personal action plan for after you become certified. Include at least 5 steps (e.g., find a project, join a community, teach someone).
Create a one‑page “Scrum Guide” for beginners. Include the roles, events, and artifacts in simple language. Make it easy for a child to understand.
Find a real‑life project (at school, home, or community) and apply Scrum for one Sprint. Document your process – what you planned, what you did, what you learned.
You are a Scrum Master for a team that has never used Scrum before. Create a 10‑step plan to introduce Scrum to the team, starting from the first day. Explain each step and why it’s important.
(Answers are provided within the Multiple Choice and Matching sections above.)
Congratulations! You have completed all ten modules of the Certified Scrum Master course. You now have the knowledge and skills to become a successful Scrum Master.
Next steps:
🎉 You did it! You are now ready to become a Certified Scrum Master. Go out and make the world a better place – one Sprint at a time!
Hello, Certified Scrum Master! You have completed all the modules, passed your exam, and now you are officially a Certified Scrum Master. But your journey is just beginning!
In this final bonus module, we will explore what comes next. We will talk about how to continue growing, how to help your team, how to stay updated with new ideas, and how to be a great Scrum Master for many years.
Think of this as your Scrum Master's compass – it will guide you in the right direction after you get your certificate.
In Lagos, there was a Scrum Master named Tunde. He got his certification and was very proud. He helped his team build great products. But after a few months, he noticed that his team was not improving as much as before.
Tunde decided to keep learning. He read new books, joined online communities, and even attended a Scrum conference. He learned new ways to facilitate meetings and new tools to help his team.
He also started mentoring other Scrum Masters. He shared his experiences and learned from theirs. His team became one of the best in the company.
Tunde realized that certification was just the beginning. The real journey is about continuous growth and helping others grow too.
Definition: Certification is official proof that you have learned the basics of Scrum.
Why important? It shows employers and teams that you know Scrum.
Simple explanation: Like a driver's license – it says you know how to drive, but you still need practice.
Real‑life example: A doctor gets a degree but continues learning throughout their career.
School example: You get a certificate for finishing a course, but you still study more.
Home example: Learning to cook – a certificate doesn't make you a chef overnight.
Nigerian example: A tailor learns sewing, gets a certificate, but still learns new styles.
Certification = Start Line ┌─────────────────────────────┐ │ Certification │ │ │ │ │ ▼ │ │ Continuous Learning │ └─────────────────────────────┘
Mini summary: Certification is the start, not the end.
Definition: A growth mindset means believing that you can always learn and improve.
Why important? It helps you keep getting better.
Simple explanation: Like a plant – if you water it, it grows.
How to practice:
Mini summary: Growth mindset = always learning.
Definition: Lifelong learning means continuing to learn new things throughout your life.
Why important? The world changes, and Scrum evolves.
Simple explanation: Like updating your phone – you need new features.
Ways to keep learning:
Mini summary: Lifelong learning = staying sharp.
Definition: A community is a group of people who share the same interests and help each other.
Why important? You learn from others and get support.
Simple explanation: Like a soccer team – you practise together and get better.
How to build community:
Nigerian example: Join the Agile Nigeria community.
Mini summary: Community = growth together.
Definition: As a Scrum Master, you help your team get better at teamwork, communication, and delivery.
Why important? A great team makes great products.
Simple explanation: Like a coach helping players improve.
Ways to help:
Mini summary: Help your team shine.
Definition: A leader is someone who guides and inspires others.
Why important? Teams look to you for direction and support.
Simple explanation: Like a captain steering a ship.
Qualities of a leader:
Mini summary: Lead by helping.
Definition: Sometimes teams face conflicts, resistance, or failure.
Why important? Knowing how to handle tough times makes you a better Scrum Master.
Simple explanation: Like knowing how to fix a flat tire.
Tips:
Mini summary: Handle tough situations with care.
Definition: Inspiration is what keeps you excited and motivated.
Why important? It helps you stay positive and energetic.
Simple explanation: Like fuel for a car – you need it to keep going.
How to stay inspired:
Mini summary: Find inspiration every day.
Definition: Scrum isn't just for work – you can use it in your personal life, school, and community.
Why important? It helps you stay organized and achieve goals.
Simple explanation: Like using a calendar to plan your day.
Examples:
Mini summary: Scrum is for life.
Definition: Values are the principles that guide your actions.
Why important? They help you make good decisions.
Key values:
Mini summary: Values guide your journey.
Definition: Mentoring means helping someone else learn and grow.
Why important? It strengthens the community and helps you learn too.
Simple explanation: Like teaching a friend how to play a game.
How to mentor:
Mini summary: Mentoring helps both you and others.
Definition: Trends are new ideas and practices that become popular.
Why important? Scrum evolves, and you need to stay updated.
Simple explanation: Like getting new versions of a game.
How to keep up:
Mini summary: Stay current with trends.
Definition: A great Scrum Master creates a positive impact on their team, product, and organization.
Why important? You can make a real difference.
Simple explanation: Like a gardener – you help things grow.
Examples of impact:
Mini summary: Your impact matters.
Definition: Goals are things you want to achieve in the future.
Why important? They give you direction.
Simple explanation: Like a destination on a map.
Examples of goals:
Mini summary: Set goals and work towards them.
Definition: Legacy is what you leave behind – the impact you have on people and organizations.
Why important? It's about making a lasting difference.
Simple explanation: Like planting a tree that others will enjoy.
How to build a legacy:
Mini summary: Build a legacy of positive impact.
Scrum Master Growth Path
┌─────────────────────────────────────────────────────┐
│ Certification → Practice → Advanced → Mentor → Legacy │
└─────────────────────────────────────────────────────┘
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
"I know" "I do" "I help" "I guide" "I inspire"
| Phase | Focus | Key Skill |
|---|---|---|
| Beginner | Learn Scrum basics | Knowledge of events and roles |
| Practitioner | Apply Scrum | Facilitation and coaching |
| Advanced | Solve complex problems | Conflict resolution and leadership |
| Mentor | Guide others | Teaching and inspiring |
| Beginner SM | Experienced SM |
|---|---|
| Follows rules strictly | Adapts rules to context |
| Focuses on events | Focuses on values |
| Asks for help often | Helps others often |
| Learns from mistakes | Learns and teaches from mistakes |
(Each lesson above includes a mini summary.)
In this bonus module, we explored what it means to be a Certified Scrum Master beyond the certification. We learned that certification is just the beginning – the real journey is about continuous learning, community building, and making a positive impact.
We discussed the importance of a growth mindset, lifelong learning, and helping your team improve. We explored leadership, handling difficult situations, and staying inspired. We also looked at applying Scrum beyond work, mentoring others, and building a lasting legacy.
Remember, you are now part of a global community of Scrum Masters. Your journey is unique, and you have the power to make a difference. Keep learning, keep growing, and keep helping others.
| Term | Definition |
|---|---|
| 1. Certification | A. Always learning |
| 2. Growth Mindset | B. Official proof of knowledge |
| 3. Lifelong Learning | C. Positive impact left behind |
| 4. Legacy | D. Believing you can improve |
Answers: 1‑B, 2‑D, 3‑A, 4‑C
Scenario: You have been a Certified Scrum Master for 2 years. Your team is doing well, but you feel that you are not growing. You want to do more than just the basics.
Question: What steps would you take to challenge yourself and continue growing?
Answer: I would set a new learning goal – maybe an advanced certification. I would join a new community or start a meetup. I would offer to mentor a junior Scrum Master. I would also volunteer to lead a large, complex project to gain new experience.
In groups of 4, create a "Scrum Master Growth Plan" for the next 12 months. Include learning goals, community activities, and mentoring plans. Share your plan with the class.
Write a letter to your future self – one year from now. Describe what you hope to have achieved as a Scrum Master. Include your goals, challenges you might face, and how you will overcome them.
Design a "Scrum Master Toolbox" – a collection of techniques, frameworks, and tips that you can use in your work. Include at least 5 tools and explain when and how to use each one.
Find a local project (at school, in your community, or at work) that could benefit from Scrum. Offer to help the team apply Scrum for one Sprint. Document the process and the results.
You are invited to speak at a conference about your Scrum journey. Write a 5‑minute speech about the most important lessons you have learned as a Scrum Master. Include stories and practical advice.
(Answers are provided within the Multiple Choice and Matching sections above.)
You have completed all eleven modules of this Certified Scrum Master course. You now have a solid foundation in Scrum and the tools to become a great Scrum Master.
What's next?
🎉 Congratulations on completing the entire course! You are now a Certified Scrum Master. Go out, lead with heart, and make a positive impact on the world – one Sprint at a time!
Hello, Scrum Master! You have learned all the basics of Scrum. You know the roles, the events, and the artifacts. But what do you do when things get tricky? What tools can you use to help your team work better, solve problems, and stay happy?
In this module, we will explore the Scrum Master's Toolbox – a collection of techniques, tips, and tools that you can use in your daily work. Think of it like a handy bag of tricks that you can pull out whenever your team needs help.
By the end of this module, you will have many new tools to help your team communicate, solve problems, and keep improving. Let's open the toolbox!
In a busy tech company in Lagos, there was a Scrum Master named Funke. She was known for her magic bag. Every time her team had a problem, she would reach into her bag and pull out a tool to help.
One day, the team was arguing about what to build next. Funke pulled out a Priority Matrix. She asked the team to place each item on a grid of "important" and "urgent". Suddenly, it was clear which items to work on first.
Another day, the team felt bored and unmotivated. Funke pulled out a Retrospective activity called "Mad, Sad, Glad". The team shared what made them mad, sad, and glad – and found solutions together.
The team loved Funke's magic bag. But Funke knew that the real magic was not in the tools – it was in knowing when and how to use them.
Definition: The Scrum Master's Toolbox is a collection of techniques, activities, and frameworks that help the team work better.
Why important? It gives you practical ways to solve common problems.
Simple explanation: Like a carpenter's toolbox – you need the right tool for the right job.
Real‑life example: A teacher has many teaching methods to reach different students.
School example: A student uses flashcards, mind maps, and practice tests to study.
Home example: A parent uses different strategies to get kids to do chores.
Nigerian example: A market trader uses different bargaining techniques for different customers.
Scrum Master's Toolbox ┌─────────────────────────────┐ │ Communication tools │ │ Problem‑solving tools │ │ Meeting facilitation tools │ │ Team building tools │ │ Motivation tools │ └─────────────────────────────┘
Mini summary: Toolbox = practical help for any situation.
Definition: A grid that helps you decide what is important and urgent.
Why important? It helps the team focus on the most important work.
Simple explanation: Like sorting your homework – urgent and important things come first.
Priority Matrix ┌─────────────────────────────┐ │ Important & Urgent │ Important & Not Urgent │ │ (Do first) │ (Plan for later) │ ├─────────────────────────────┤ │ Not Important & Urgent │ Not Important & Not Urgent │ │ (Delegate) │ (Eliminate) │ └─────────────────────────────┘
Mini summary: Priority Matrix = decide what matters most.
Definition: A technique where you ask "Why?" five times to find the root cause of a problem.
Why important? It helps you solve the real problem, not just the symptoms.
Simple explanation: Like a detective asking questions until they find the truth.
Example:
Mini summary: 5 Whys = find the root cause.
Definition: A technique where team members write down ideas silently before sharing.
Why important? It gives everyone a chance to speak, not just the loudest people.
Simple explanation: Like writing your answer on a paper before reading it aloud.
How to do it:
Mini summary: Silent Brainstorming = hear everyone's voice.
Definition: A Retrospective activity with 5 categories: Start, Stop, Continue, More, Less.
Why important? It gives structure to the Retrospective and covers all areas.
Simple explanation: Like a starfish with 5 arms – each arm is a different area.
Retrospective Starfish ┌─────────────────────────────┐ │ Start │ Stop │ Continue │ │ More │ Less │ │ └─────────────────────────────┘
Mini summary: Starfish = balanced Retrospective.
Definition: A quick way to check how the team is feeling each day.
Why important? It helps you spot problems before they grow.
Simple explanation: Like a weather forecast – sunny, cloudy, or rainy.
How to do it:
Mini summary: Happiness Meter = check team mood.
Definition: A place to capture off‑topic ideas during a meeting.
Why important? It keeps the meeting focused but also captures good ideas.
Simple explanation: Like a notebook for thoughts that come up during class.
How to do it:
Mini summary: Parking Lot = save ideas for later.
Definition: A table that helps the team make decisions by evaluating options against criteria.
Why important? It makes decisions objective and transparent.
Simple explanation: Like scoring movies based on different categories.
Decision Matrix ┌─────────────────────────────────┐ │ Option │ Cost │ Time │ Score │ ├─────────────────────────────────┤ │ A │ 3 │ 4 │ 7 │ │ B │ 2 │ 5 │ 7 │ │ C │ 4 │ 2 │ 6 │ └─────────────────────────────────┘
Mini summary: Decision Matrix = make decisions easier.
Definition: Using a timer to keep meetings and activities within a set time.
Why important? It keeps everyone focused and on track.
Simple explanation: Like using a timer for a game so everyone gets a turn.
Tips:
Mini summary: Timeboxing = manage time well.
Definition: A visual tool that helps teams align on goals, roles, and working agreements.
Why important? It builds shared understanding.
Simple explanation: Like a poster that shows everyone's role and how to work together.
Sections:
Mini summary: Team Canvas = shared understanding.
Definition: A technique for giving feedback: positive, constructive, positive.
Why important? It makes feedback easier to hear and accept.
Simple explanation: Like a sandwich – bread (positive), filling (constructive), bread (positive).
Example:
Mini summary: Feedback Sandwich = make feedback easier.
Definition: Short breaks during meetings to recharge and refocus.
Why important? It keeps energy levels high.
Simple explanation: Like a short recess during class.
Ideas:
Mini summary: Energy Breaks = recharge and focus.
Definition: A checklist to make sure your Sprint Review is effective.
Why important? It ensures you don't miss anything.
Checklist:
Mini summary: Sprint Review Checklist = stay organized.
Definition: A set of different Retrospective activities to keep it fresh.
Why important? Variety keeps the Retrospective engaging.
Activities:
Mini summary: Retrospective Toolkit = variety and engagement.
Definition: Your personal guide to knowing what to do in any situation.
Why important? It helps you stay focused on the right things.
Directions:
The Scrum Master's Compass ┌─────────────────────────────┐ │ North (Values) │ │ │ │ │ West (Org)───┼─── East (PO) │ │ │ │ │ South (Team) │ └─────────────────────────────┘
Mini summary: Compass = guide your actions.
The Scrum Master's Toolbox ┌─────────────────────────────────────────────┐ │ ┌─────────┐ ┌─────────┐ ┌─────────┐ │ │ │ Priority │ │ 5 Whys │ │Silent │ │ │ │ Matrix │ │ │ │Brain- │ │ │ └─────────┘ └─────────┘ │storming │ │ │ ┌─────────┐ ┌─────────┐ └─────────┘ │ │ │Starfish │ │Happiness│ ┌─────────┐ │ │ │ │ │ Meter │ │Parking │ │ │ └─────────┘ └─────────┘ │ Lot │ │ │ ┌─────────┐ ┌─────────┐ └─────────┘ │ │ │Decision │ │Team │ ┌─────────┐ │ │ │ Matrix │ │ Canvas │ │Feedback │ │ │ └─────────┘ └─────────┘ │Sandwich │ │ │ ┌─────────┐ ┌─────────┐ └─────────┘ │ │ │ Energy │ │ Checklist│ ┌─────────┐ │ │ │ Breaks │ │ Review │ │Compass │ │ │ └─────────┘ └─────────┘ └─────────┘ │ └─────────────────────────────────────────────┘
| Tool | Best Use Case |
|---|---|
| Priority Matrix | When the team needs to prioritize work |
| 5 Whys | When you need to find the root cause of a problem |
| Silent Brainstorming | When you want to hear everyone's ideas |
| Retrospective Starfish | During Retrospectives to structure feedback |
| Happiness Meter | To check team morale regularly |
| Parking Lot | During meetings to capture off‑topic ideas |
| Decision Matrix | When making decisions with multiple options |
| Feedback Sandwich | When giving constructive feedback |
| Scrum Tool | Traditional Approach |
|---|---|
| Silent Brainstorming | Open discussion (loudest voice wins) |
| 5 Whys | Blame people for problems |
| Happiness Meter | Ignore team feelings until problems appear |
| Parking Lot | Let meetings go off‑track |
(Each lesson above includes a mini summary.)
In this module, we explored the Scrum Master's Toolbox – a set of practical tools to help you in your role. We learned about the Priority Matrix for prioritizing work, the 5 Whys for finding root causes, and Silent Brainstorming to hear everyone's voice. We also covered the Retrospective Starfish, the Happiness Meter, the Parking Lot, the Decision Matrix, the Team Canvas, the Feedback Sandwich, and many more.
Remember, tools are only useful if you use them. Practice each tool, adapt them to your team, and keep adding new ones to your toolbox. With these tools, you can handle almost any situation and help your team succeed.
| Tool | Purpose |
|---|---|
| 1. Priority Matrix | A. Find root causes |
| 2. 5 Whys | B. Prioritize work |
| 3. Silent Brainstorming | C. Hear everyone's ideas |
| 4. Happiness Meter | D. Check team mood |
Answers: 1‑B, 2‑A, 3‑C, 4‑D
Scenario: Your team is having a long meeting. People are getting tired and distracted. The agenda is not being followed.
Question: What tools from the toolbox could you use to help? Choose at least 3 and explain how you would use them.
Answer: I would use Timeboxing to set time limits for each agenda item. I would use the Parking Lot to capture off‑topic ideas and keep the meeting focused. I would also use Energy Breaks to help the team recharge and refocus.
In groups of 4, create a "Toolbox" presentation. Choose 5 tools from this module. Explain each tool, show an example, and practice using it with the group. Present your toolbox to the class.
Create a personal "Scrum Master's Toolbox" card. List at least 10 tools with a short description of when to use each one. Keep it as a reference for your work.
Choose a team project (real or imaginary). Use at least 3 tools from the toolbox to help the team. Document how you used each tool and the results.
Observe a meeting in your school or community. Identify at least 3 problems (e.g., people talking over each other, no agenda, low energy). Suggest a tool from the toolbox to solve each problem.
Create a brand new tool that is not in this module. Describe its purpose, how to use it, and when to use it. Present your new tool to the class and explain why it would be helpful.
(Answers are provided within the Multiple Choice and Matching sections above.)
In the next module, we will explore Advanced Facilitation Techniques. You will learn how to run meetings like a pro, handle conflicts, and guide your team to make better decisions. For now, start practising the tools you learned in this module. You are becoming a master of your craft!
🎉 Congratulations! You have completed Module Twelve. Keep building your toolbox!
Hello, Scrum Master! You already know the basics of Scrum. You have a toolbox full of tools. Now it's time to take your skills to the next level with advanced facilitation techniques.
Facilitation is like being a guide for your team. You help them have good meetings, make good decisions, and solve problems together. A great facilitator makes everything look easy – but it takes practice!
Think of this module as your facilitation masterclass. You will learn how to handle difficult situations, keep meetings engaging, and help your team collaborate like never before.
In a bustling tech hub in Lagos, there was a Scrum Master named Amara. She was known as the master facilitator. Whenever a meeting was stuck, people would call Amara.
One day, a team was arguing about what feature to build next. The meeting was going nowhere. Amara walked in and said, "Let's try something different."
She asked everyone to write their ideas on sticky notes. She grouped the ideas and asked the team to vote. Within 30 minutes, they had a clear decision. The team was amazed.
Amara smiled and said, "Facilitation is not about having the answer. It's about helping the team find the answer themselves."
From that day, the team learned to facilitate their own meetings. And they always remembered Amara's secret – listen, guide, and empower.
Definition: Facilitation is the art of helping a group work together effectively.
Why important? It makes meetings productive and enjoyable.
Simple explanation: Like a referee in a game – they help the game run smoothly.
Real‑life example: A teacher facilitating a class discussion.
School example: A student leading a group project meeting.
Home example: A parent guiding a family meeting.
Nigerian example: A community leader facilitating a town hall meeting.
Facilitation = Guiding the Group ┌─────────────────────────────┐ │ Facilitator │ │ │ │ │ ▼ │ │ Team → Discussion → Decision│ └─────────────────────────────┘
Mini summary: Facilitation = helping the group succeed.
Definition: The facilitator's role is to guide the process, not to make decisions.
Why important? It keeps the focus on the team's needs.
Simple explanation: Like a tour guide – they show the way, but you decide where to go.
Key responsibilities:
Mini summary: Facilitator = guide, not boss.
Definition: Preparation is everything – knowing the goal, the agenda, and the participants.
Why important? A well‑prepared session is more likely to succeed.
Simple explanation: Like preparing ingredients before cooking.
Steps:
Mini summary: Preparation = key to success.
Definition: Ground rules are simple rules that everyone agrees to follow during the meeting.
Why important? They create a safe and respectful environment.
Simple explanation: Like the rules of a game – everyone knows how to play.
Examples:
Mini summary: Ground rules = keep meetings respectful.
Definition: A voting technique where participants show fingers to indicate agreement.
Why important? It gives a quick sense of the group's opinion.
Simple explanation: Like raising your hand in class.
Fist of Five ┌─────────────────────────────┐ │ 5 fingers = full support │ │ 1 finger = not at all │ │ 3 fingers = neutral │ └─────────────────────────────┘
Mini summary: Fist of Five = quick consensus check.
Definition: A technique where everyone gets a chance to speak in turn.
Why important? It ensures everyone is heard.
Simple explanation: Like going around the circle in a game.
How to do it:
Mini summary: Round Robin = everyone speaks.
Definition: A technique where participants vote silently on paper or digitally.
Why important? It reduces peer pressure and gives honest answers.
Simple explanation: Like voting in a secret ballot.
How to do it:
Mini summary: Silent Vote = honest feedback.
Definition: A technique where participants use stickers or dots to vote on options.
Why important? It's visual, quick, and engaging.
Simple explanation: Like putting a sticker on your favourite toy.
How to do it:
Dot Voting ┌─────────────────────────────┐ │ Option A: ●●●● │ │ Option B: ●● │ │ Option C: ●●● │ └─────────────────────────────┘
Mini summary: Dot Voting = visual and fun.
Definition: Capturing off‑topic ideas to discuss later.
Why important? It keeps the meeting focused.
Simple explanation: Like a "to‑do later" list.
How to do it:
Mini summary: Parking Lot = stay on track.
Definition: A person who watches the time and keeps the meeting on schedule.
Why important? It prevents meetings from running too long.
Simple explanation: Like a referee with a stopwatch.
Tips:
Mini summary: Timekeeper = keep meetings on time.
Definition: Techniques to make sure quiet people get a chance to speak.
Why important? Everyone's voice matters.
Simple explanation: Like making sure everyone gets a turn in a game.
Techniques:
Mini summary: Handle dominant voices = include everyone.
Definition: Helping team members resolve disagreements constructively.
Why important? Conflict can be healthy if handled well.
Simple explanation: Like a referee in a sports match – they make sure the game is fair.
Steps:
Mini summary: Manage conflict = keep it constructive.
Definition: Ending a meeting with a clear summary of what was decided and what to do next.
Why important? It ensures everyone is on the same page.
Simple explanation: Like writing down the homework at the end of class.
What to summarize:
Mini summary: Summarize = clear next steps.
Definition: Techniques to keep participants engaged and energetic.
Why important? High energy leads to better participation and outcomes.
Simple explanation: Like a cheerleader – they keep the team excited.
Techniques:
Mini summary: Keep energy high = keep everyone engaged.
Definition: Using facilitation techniques to make the Retrospective effective.
Why important? The Retrospective is the heart of continuous improvement.
Simple explanation: Like a team huddle after a game – talk about what went well and what to improve.
Tips:
Mini summary: Retrospective facilitation = improve continuously.
Facilitation Process
┌─────────────────────────────────────────────┐
│ Prepare → Start → Facilitate → Summarize → Close │
└─────────────────────────────────────────────┘
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
Set goal Set rules Guide talk Recap End well
| Technique | When to Use |
|---|---|
| Fist of Five | Quick consensus check |
| Round Robin | Ensure everyone speaks |
| Silent Vote | Reduce peer pressure |
| Dot Voting | Visual, quick decision |
| Parking Lot | Capture off‑topic ideas |
| Timekeeper | Keep meeting on schedule |
| Good Facilitation | Poor Facilitation |
|---|---|
| Everyone participates | Only a few people speak |
| Meetings end on time | Meetings run over |
| Clear decisions are made | No decisions are made |
| People feel heard | People feel ignored |
(Each lesson above includes a mini summary.)
In this module, we explored advanced facilitation techniques – skills that help you guide your team to success. We learned that facilitation is about helping the group, not making decisions for them. We covered preparation, setting ground rules, and using techniques like Round Robin, Fist of Five, Silent Vote, Dot Voting, and the Parking Lot.
We also discussed handling dominant voices, managing conflict, keeping energy high, and facilitating the Sprint Retrospective. These techniques will make you a more effective Scrum Master and help your team collaborate better.
| Technique | Purpose |
|---|---|
| 1. Fist of Five | A. Quick consensus check |
| 2. Round Robin | B. Ensure everyone speaks |
| 3. Silent Vote | C. Reduce peer pressure |
| 4. Dot Voting | D. Visual voting |
Answers: 1‑A, 2‑B, 3‑C, 4‑D
Scenario: You are facilitating a Sprint Planning meeting. Two team members are arguing about the importance of a feature. The meeting is getting tense, and time is running out.
Question: What facilitation techniques would you use to resolve the situation?
Answer: I would use the Parking Lot to capture the argument for later discussion. I would also use Fist of Five to check the team's opinion. If needed, I would use Dot Voting to make a decision. I would also use a Timekeeper to make sure we finish on time.
In groups of 4, practice facilitating a meeting. One person is the facilitator, and the others are team members. The topic: "What should we do for our next team building activity?" Use at least 3 facilitation techniques. After 10 minutes, discuss how it went.
Observe a meeting in your school or community. Write a report on how the meeting was facilitated. What techniques were used? What could be improved?
Plan and facilitate a 15‑minute meeting on a topic of your choice. Use at least 3 facilitation techniques. Record the meeting (with permission) and review your performance. What went well? What could be improved?
Volunteer to facilitate a meeting in your school, community, or family. Use at least 2 facilitation techniques. Write a report on your experience.
You are the facilitator for a team that has been arguing for weeks. The team is stuck and not making progress. Create a facilitation plan to help the team move forward. Include techniques, ground rules, and a timeline.
(Answers are provided within the Multiple Choice and Matching sections above.)
In the next module, we will explore Coaching and Mentoring in Scrum. You will learn how to coach your team members, help them grow, and become a better leader. For now, practice your facilitation skills in every meeting you attend. You are becoming a master facilitator!
🎉 Congratulations! You have completed Module Thirteen. Keep facilitating and empowering!
Hello, Scrum Master! You have learned many skills – facilitation, tools, events, and roles. Now it's time to learn about coaching and mentoring. These are skills that help your team members grow, become better, and reach their potential.
Think of coaching like being a sports coach. You don't play the game, but you help your players improve. Mentoring is like being a wise friend who shares experience and advice.
In this module, you will learn how to coach and mentor your team. You will discover how to ask good questions, give helpful feedback, and help people solve their own problems. Let's begin!
In a busy tech company in Lagos, there was a senior developer named Kemi. She was known for her coding skills, but she was also a great coach. When new developers joined the team, Kemi would mentor them.
One day, a new developer named Tayo joined the team. He was smart but nervous. Kemi didn't just tell him what to do. Instead, she asked questions: "What do you think is the best way to solve this?" "What have you tried so far?"
Tayo started thinking for himself. He made mistakes, but Kemi helped him learn from them. Within a few months, Tayo became a confident developer. He said, "Kemi didn't give me answers. She taught me how to find answers myself."
That is the power of coaching and mentoring.
Definition: Coaching is helping someone improve their skills and performance by asking questions and guiding them.
Why important? It helps people become independent and confident.
Simple explanation: Like a sports coach – they help you get better at the game.
Real‑life example: A music teacher helps you play an instrument better.
School example: A teacher helps you understand a difficult topic.
Home example: A parent helps you learn to ride a bike.
Nigerian example: A traditional craftsman teaches an apprentice a trade.
Coaching = Helping People Grow ┌─────────────────────────────┐ │ Coach │ │ │ │ │ ▼ │ │ Ask questions → Guide → Grow│ └─────────────────────────────┘
Mini summary: Coaching = help people improve.
Definition: Mentoring is sharing your experience and advice to help someone grow.
Why important? It passes on knowledge and wisdom.
Simple explanation: Like an older sibling showing you how to do something.
Real‑life example: A senior worker guiding a new employee.
School example: An older student helping a younger one.
Home example: A grandparent sharing life lessons.
Nigerian example: A successful business owner mentoring a young entrepreneur.
Mini summary: Mentoring = sharing wisdom and experience.
Definition: Coaching is about helping people find answers themselves. Mentoring is about sharing your own experience.
Why important? Knowing the difference helps you choose the right approach.
Simple explanation: Coaching = "What do you think?" Mentoring = "Let me tell you what I did."
| Coaching | Mentoring |
|---|---|
| Asks questions | Gives advice |
| Helps people find answers | Shares experience |
| Focuses on skills | Focuses on career or life |
| Short‑term | Long‑term |
Mini summary: Coaching = questions; Mentoring = advice.
Definition: A coaching mindset means believing that people can grow and that you are there to help them.
Why important? It builds trust and empowers people.
Simple explanation: Like a gardener – you help plants grow, but you don't pull them up.
Key beliefs:
Mini summary: Coaching mindset = believe in people.
Definition: Questions that make people think deeply and find their own solutions.
Why important? They help people grow without being told what to do.
Simple explanation: Like a mirror – you help people see themselves clearly.
Examples:
Mini summary: Powerful questions = unlock thinking.
Definition: Listening not just to the words, but to the meaning and feelings behind them.
Why important? It shows respect and helps you understand the person.
Simple explanation: Like listening to a friend – you hear what they're really saying.
Tips:
Mini summary: Active listening = hear with your heart.
Definition: Sharing observations to help someone improve.
Why important? Feedback helps people grow.
Simple explanation: Like a mirror – you show people what they can't see themselves.
Tips for effective feedback:
Mini summary: Feedback = help people improve.
Definition: Positive feedback, constructive feedback, positive feedback.
Why important? It makes feedback easier to hear.
Simple explanation: Like a sandwich – bread (positive), filling (constructive), bread (positive).
Example:
Mini summary: Feedback Sandwich = make feedback palatable.
Definition: A simple coaching framework: Goal, Reality, Options, Way forward.
Why important? It gives structure to coaching conversations.
Simple explanation: Like a map – it helps you know where you are and where you're going.
Steps:
GROW Model ┌─────────────────────────────┐ │ Goal → Reality → Options → Way Forward │ └─────────────────────────────┘
Mini summary: GROW = structure for coaching.
Definition: Situation, Behaviour, Impact – a model for giving feedback.
Why important? It makes feedback clear and objective.
Simple explanation: Like telling a story – what happened, what was done, what was the result.
Steps:
Example: "In yesterday's meeting (Situation), you interrupted Tayo twice (Behaviour), and I felt it was hard for Tayo to share his ideas (Impact)."
Mini summary: SBI = clear, objective feedback.
Definition: Helping the whole team improve together.
Why important? Teams need to grow together, not just individuals.
Simple explanation: Like a choir – you help everyone sing in harmony.
Techniques:
Mini summary: Coach the team = grow together.
Definition: Helping new people learn the ropes and feel welcome.
Why important? It helps new team members become productive faster.
Simple explanation: Like showing a new student around the school.
Tips:
Mini summary: Mentor new members = help them settle in.
Definition: Not giving answers, but guiding people to find solutions themselves.
Why important? It builds independence and confidence.
Simple explanation: Like teaching someone to fish – you don't give them a fish, you teach them how to fish.
Approach:
Mini summary: Help people solve their own problems.
Definition: Knowing when to use coaching (asking questions) and when to use mentoring (giving advice).
Why important? Using the right approach at the right time is key.
Simple explanation: Like knowing when to listen and when to speak.
Guidelines:
Mini summary: Coach or mentor – choose wisely.
Definition: A great coach and mentor is patient, empathetic, and always learning.
Why important? You help others become their best selves.
Simple explanation: Like a wise elder – they guide with kindness.
Qualities:
Mini summary: Great coach = patient, empathetic, committed.
Coaching vs Mentoring ┌─────────────────────────────────────────────┐ │ Coaching Mentoring │ │ ┌─────────────────────┐ ┌─────────────────┐ │ │ │ Ask questions │ │ Share experience │ │ │ │ Guide │ │ Give advice │ │ │ │ Help find answers │ │ Provide wisdom │ │ │ └─────────────────────┘ └─────────────────┘ │ └─────────────────────────────────────────────┘
| Technique | When to Use |
|---|---|
| Powerful Questions | When you want to unlock thinking |
| Active Listening | Always – it builds trust |
| GROW Model | When you need structure for coaching |
| SBI Model | When giving specific feedback |
| Feedback Sandwich | When giving constructive feedback |
| Coach | Mentor |
|---|---|
| Asks questions | Gives advice |
| Focuses on skills | Focuses on career/life |
| Short‑term | Long‑term |
| Helps find answers | Shares experience |
(Each lesson above includes a mini summary.)
In this module, we explored coaching and mentoring in Scrum. We learned that coaching is about asking questions and helping people find their own answers, while mentoring is about sharing experience and advice. We covered important skills like active listening, asking powerful questions, and giving effective feedback.
We also learned about useful frameworks like the GROW Model and the SBI Model. These tools help you structure coaching conversations and give clear feedback. Remember, the goal of coaching and mentoring is to help people grow and become independent.
| Term | Definition |
|---|---|
| 1. Coaching | A. Sharing experience |
| 2. Mentoring | B. Asking questions |
| 3. GROW | C. Goal, Reality, Options, Way forward |
| 4. SBI | D. Situation, Behaviour, Impact |
Answers: 1‑B, 2‑A, 3‑C, 4‑D
Scenario: A team member is struggling with a technical problem. They have been stuck for two days and are feeling frustrated.
Question: How would you coach them instead of just giving them the answer?
Answer: I would start by empathizing – "That sounds frustrating." Then I would ask powerful questions: "What have you tried so far?" "What do you think the problem might be?" "What would you try if you had no constraints?" "What is one small step you could take now?" I would help them explore options and find their own solution.
In pairs, practice a coaching conversation. One person is the coach, the other is the coachee. Choose a problem – "How can I improve my Retrospectives?" Use the GROW model. After 10 minutes, switch roles. Discuss what worked well.
Write a reflection on a time when you were coached or mentored. What did the person do that was helpful? What could they have done differently?
Create a "Coaching Guide" for your team. Include the GROW model, tips for active listening, and examples of powerful questions. Share it with your team.
Volunteer to coach or mentor someone in your school or community. Use the techniques you learned. Write a report on your experience – what worked, what you learned, and what you would do differently.
You have a team member who is very resistant to feedback. They always become defensive. Create a coaching plan to help them become more open. Include specific questions and approaches.
(Answers are provided within the Multiple Choice and Matching sections above.)
In the next module, we will explore Agile Leadership and the Scrum Master as a Change Agent. You will learn how to lead change in your organization, help teams adopt agile mindsets, and overcome resistance. For now, practice your coaching skills with your team or friends. You are becoming a great leader!
🎉 Congratulations! You have completed Module Fourteen. Keep coaching and mentoring!
Hello, Scrum Master! You have learned many skills – coaching, facilitation, and all the Scrum basics. Now it's time to talk about leadership. You are not just a Scrum Master – you are a change agent. You help your team, your organization, and even your community become more agile.
Think of a change agent like a gardener. You don't just plant seeds – you water them, protect them from pests, and help them grow. You create the conditions for change to happen.
In this module, you will learn how to lead change, overcome resistance, and inspire others to adopt agile mindsets. You will become a true leader – not by giving orders, but by helping others see the way.
In a large company in Lagos, there was a Scrum Master named Chidi. The company had been working the same way for 20 years – slowly and with many problems. People were unhappy, but they were afraid of change.
Chidi didn't tell everyone, "You must change!" Instead, he started small. He helped one team adopt Scrum. That team became happier and faster. Other teams saw the success and wanted to try too.
Chidi also talked to managers. He showed them how agile could help the company. He answered their questions and calmed their fears. Slowly, the company began to change.
A year later, the company was more agile, more productive, and more joyful. Chidi didn't force the change – he inspired it. He was a true change agent.
Definition: A change agent is someone who helps others adopt new ways of thinking and working.
Why important? Change doesn't happen by itself – someone needs to lead it.
Simple explanation: Like a tour guide – you show people a new path.
Real‑life example: A teacher who introduces a new way of learning.
School example: A student who starts a recycling club.
Home example: A parent who introduces a new chore system.
Nigerian example: A community leader who brings clean water to a village.
Change Agent = Leader of Change ┌─────────────────────────────┐ │ Inspire → Guide → Support → Succeed │ └─────────────────────────────┘
Mini summary: Change agent = lead the way.
Definition: People often resist change because it feels uncomfortable or risky.
Why important? Understanding why change is hard helps you be patient and empathetic.
Simple explanation: Like wearing a new pair of shoes – it feels strange at first.
Reasons people resist change:
Mini summary: Change is hard – be understanding.
Definition: The Scrum Master is not just a facilitator – they are also a leader of change.
Why important? Scrum is a big change for many organizations.
Simple explanation: Like a captain guiding a ship through a storm.
Key roles:
Mini summary: SM = change agent.
Definition: Showing others what to do by doing it yourself.
Why important? People are more likely to follow if they see you doing it.
Simple explanation: Like a parent who reads – children will read too.
How to lead by example:
Mini summary: Lead by example = show the way.
Definition: Trust is believing that someone is honest, reliable, and has good intentions.
Why important? Without trust, people won't follow your lead.
Simple explanation: Like a friendship – trust is the foundation.
How to build trust:
Mini summary: Trust = foundation of change.
Definition: Helping people who are resistant to change become more open.
Why important? Resistance is natural – you need to help people work through it.
Simple explanation: Like a lock – you need the right key to open it.
Strategies:
Mini summary: Overcome resistance with patience and empathy.
Definition: Motivating people to want to change.
Why important? Inspired people change willingly.
Simple explanation: Like a coach giving a motivational speech.
How to inspire:
Mini summary: Inspire = motivate from within.
Definition: Getting people to change without having power over them.
Why important? As a Scrum Master, you don't always have authority.
Simple explanation: Like a friend convincing you to try a new game.
Techniques:
Mini summary: Influence = guide without power.
Definition: Clearly explaining what you want to achieve and why it matters.
Why important? People need to understand the "why" before they buy in.
Simple explanation: Like telling a story – people need to see the ending.
Tips:
Mini summary: Vision = the "why" of change.
Definition: Building an environment where agile values and practices thrive.
Why important? Agile is not just a process – it's a mindset.
Simple explanation: Like planting a garden – you need the right soil and care.
How to create it:
Mini summary: Culture = environment for agility.
Definition: An 8‑step model for leading change.
Why important? It gives a structured approach to change.
Simple explanation: Like a recipe – you follow the steps to get the result.
Steps:
Kotter Model ┌─────────────────────────────────────────────────┐ │ Urgency → Coalition → Vision → Communicate → Remove Obstacles │ │ → Wins → Build → Stick │ └─────────────────────────────────────────────────┘
Mini summary: Kotter = 8 steps to change.
Definition: A model for individual change: Awareness, Desire, Knowledge, Ability, Reinforcement.
Why important? It focuses on the person, not just the organization.
Simple explanation: Like learning a new skill – you need awareness, then knowledge, then practice.
Steps:
Mini summary: ADKAR = change at the individual level.
Definition: Leaders create the conditions for agile to succeed.
Why important? Without leadership support, agile struggles.
Simple explanation: Like a captain – they set the course.
What leaders should do:
Mini summary: Leaders = support agile.
Definition: Making sure the change lasts and becomes the new normal.
Why important? Change that doesn't stick is wasted effort.
Simple explanation: Like a diet – you need to keep it up.
How to sustain change:
Mini summary: Sustain = make change permanent.
Definition: Leadership is about serving others and helping them succeed.
Why important? People follow leaders who care about them.
Simple explanation: Like a parent – they put their children first.
Key qualities:
Mini summary: Leadership = serve and care.
Change Agent Journey
┌─────────────────────────────────────────────────┐
│ Inspire → Guide → Support → Succeed → Sustain │
└─────────────────────────────────────────────────┘
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
Vision Influence Remove Celebrate Embed
& Trust Obstacles Wins Change
| Model | Focus | Steps |
|---|---|---|
| Kotter | Organizational change | 8 steps |
| ADKAR | Individual change | 5 steps |
| Leading Change | Forcing Change |
|---|---|
| Inspires | Demands |
| Involves people | Orders people |
| Builds trust | Creates resistance |
| Listens | Ignores concerns |
| Celebrates wins | Moves on |
(Each lesson above includes a mini summary.)
In this module, we explored the role of the Scrum Master as a change agent. We learned that change is hard but necessary, and that leaders help others adopt new ways of working. We covered important skills like building trust, inspiring others, and overcoming resistance.
We also learned about structured change models like the Kotter Model (8 steps for organizational change) and the ADKAR Model (5 steps for individual change). These models give us a roadmap for leading change effectively.
Remember, as a Scrum Master, you are not just a facilitator – you are a leader of change. You help your team, your organization, and your community become more agile, productive, and joyful.
| Term | Definition |
|---|---|
| 1. Change Agent | A. Leading by serving |
| 2. Trust | B. Belief in honesty and reliability |
| 3. Servant Leadership | C. Someone who leads change |
| 4. Kotter Model | D. 8‑step change model |
Answers: 1‑C, 2‑B, 3‑A, 4‑D
Scenario: Your organization has been doing the same thing for 10 years. People are comfortable, but the company is falling behind competitors. You want to introduce Scrum, but people are afraid.
Question: What steps would you take as a change agent to introduce Scrum?
Answer: I would start by building trust and showing empathy. I would create a sense of urgency by sharing data and stories. I would build a coalition of supporters. I would start with a small pilot team to show success. I would celebrate their wins and use them to inspire others.
In groups of 4, choose a change you want to make in your school or community. Use the Kotter Model to plan the change. Present your plan to the class.
Write a reflection on a time you led change (or tried to). What worked? What didn't? What would you do differently now?
Create a "Change Plan" for introducing a new idea in your organization (real or imaginary). Include a vision, a coalition, and a step‑by‑step plan. Use the Kotter Model as a guide.
Identify a change you want to make in your school or community. Talk to at least 3 people about it – ask for their thoughts and concerns. Write a report on what you learned and how you could address their concerns.
You are the change agent for a team that has been using Scrum for 6 months but is not seeing results. They are losing motivation and are tempted to go back to the old way. Create a plan to revive their agile adoption. Include specific actions and why they will work.
(Answers are provided within the Multiple Choice and Matching sections above.)
In the next module, we will explore Agile Metrics and Measuring Success. You will learn how to track progress, measure team performance, and use data to improve. For now, think about changes you want to lead in your own life. You are becoming a true leader!
🎉 Congratulations! You have completed Module Fifteen. Keep leading change!