Module One: Agile Foundations and the Agile Mindset – Learning a Better Way to Work

“Agile Fundamentals” – A beginner’s guide to working smarter together

Module Introduction

Welcome, young explorer! Have you ever worked on a big project and found it became messy and slow? Have you ever finished something only to discover it was not what anyone wanted? Many people and businesses have this problem. That is why a way of working called Agile was created.

Agile is not a tool or a computer program. It is a way of thinking and working. It helps teams finish tasks faster, change plans easily, and make things people truly want. Agile started with computer programmers, but today it is used by schools, banks, shops, hospitals, and even families.

In this module, we will learn what Agile is, where it came from, and what it stands for. We will learn its four values and twelve principles. We will see how Agile is different from the old way of working. By the end, you will understand why Agile is so popular and how it can help you in school, home, and future work.

Let’s begin!

Learning Objectives

After finishing this module, you will be able to:

• Explain what Agile means in your own words.
• Describe the difference between Waterfall and Agile.
• List and explain the 4 Agile values.
• Describe the 12 Agile principles in simple language.
• Explain the difference between an Agile mindset and Agile methods.
• Give examples of Agile in real life.
• Share Nigerian examples of Agile in action.
• Understand why Agile helps teams succeed.
• Start thinking like an Agile team member.
• Complete a mini project and practical assignment.

Warm-up Story: Chidi’s Group Project

Chidi is 13 years old and lives in Lagos. His teacher gave the class a big group project: build a model of a Nigerian market. The project was due in four weeks.

Chidi’s group chose a plan. They divided the work into steps: research, design, build, and present. They decided to do everything in order. First, they would finish all research. Then, they would design everything. Then, they would build everything. Only at the end would they show the teacher.

Three weeks passed. The group worked hard. On the last day, they showed their model to the teacher. The teacher looked at it and said, "This is not what I asked for. I wanted the market to show how goods move from farms to buyers. Your model just shows shops and stalls."

Chidi’s group was sad. They had worked for weeks but missed the point. They had done everything in one long order and never checked with the teacher until the end.

Another group, led by Ada, did things differently. Ada’s group decided to work in small steps. Each week, they made a small piece of the model and showed it to the teacher. In the first week, the teacher said, "Great start, but add the farm part." In the second week, the teacher said, "Good, now add the transport part." Each week, the group improved and stayed on track.

On the last day, Ada’s group showed a beautiful model that included farms, transport, and shops. The teacher was very happy.

Chidi asked Ada, "How did you get it right?" Ada said, "We did not plan everything at the start. We worked in small steps and checked with the teacher often. That is called Agile."

Chidi learned a big lesson. Working in small steps and checking often is smarter than working a long time without checking.

Moral of the story: Agile means working in small steps, checking often, and improving as you go. It helps you finish projects that people really want.

Main Lessons

Lesson 1: What is Agile?

Definition: Agile is a way of working that helps teams finish projects in small steps, learn as they go, and change plans when needed.

Why it is important: Agile helps teams create better results faster and avoid big mistakes.

Simple explanation: Imagine building a house one room at a time and checking with the owner after each room. That is Agile.

Real-life example: Software companies use Agile to build apps step by step.

School example: A group project done in weekly steps with teacher feedback.

Home example: Cooking a meal and tasting it as you go.

Nigerian example: A trader tests a new product with a few customers before buying in bulk.

Illustration:

  Agile = Small Steps + Feedback + Improvement

  Plan small
      |
      V
  Do small
      |
      V
  Check with others
      |
      V
  Improve and repeat 🎉
  

Mini summary: Agile means working in small steps, checking often, and improving. It helps teams succeed.

Lesson 2: Where Did Agile Come From?

Definition: Agile started in 2001 when a group of software developers wrote the Agile Manifesto.

Why it is important: Knowing the story helps us understand why Agile matters.

Simple explanation: A group of smart people got together and said, "Our old way is not working. Let’s find a better way."

Real-life example: The same way a school might change its rules after seeing problems.

School example: A teacher changes teaching methods after seeing students struggle.

Home example: A family changes routines after learning what works best.

Nigerian example: A business changes how it serves customers after hearing complaints.

Illustration:

  2001: 17 developers meet
       |
       V
  Write the Agile Manifesto
       |
       V
  Share it with the world
       |
       V
  Agile grows everywhere 🎉
  

Mini summary: Agile began in 2001 with the Agile Manifesto. It was created by software developers.

Lesson 3: The Old Way – Waterfall

Definition: Waterfall is a way of working where you do all steps in one long order, one after the other.

Why it is important: Knowing Waterfall helps us see why Agile is better for many projects.

Simple explanation: Like walking down a waterfall. You cannot go back up.

Real-life example: Building a bridge where you plan everything first.

School example: Doing all research, then all writing, then all editing – without stopping to check.

Home example: Cooking all the food before tasting any of it.

Nigerian example: Printing 1,000 flyers before checking if the design is right.

Illustration:

  Waterfall:

  Plan → Design → Build → Test → Deliver
  (all in one long line, no going back)
  

Mini summary: Waterfall does everything in one long order. It is hard to change once you start.

Lesson 4: Why Agile is Different

Definition: Agile is different because it works in small cycles, checks often, and welcomes change.

Why it is important: Agile helps teams fix problems early and stay on track.

Simple explanation: Instead of one long line, Agile goes in small circles, improving each time.

Real-life example: Software teams release small updates every week.

School example: Group projects checked weekly with the teacher.

Home example: Cooking and tasting in small steps.

Nigerian example: A trader testing small batches before buying in bulk.

Illustration:

  Waterfall:   Plan → Build → Deliver (once)

  Agile:       Plan → Do → Check → Improve
                   ↑                |
                   |________________|
                   (repeat often) 🎉
  

Mini summary: Agile works in small cycles. It checks often and improves each time.

Lesson 5: The Agile Manifesto

Definition: The Agile Manifesto is a short document that explains what Agile values most.

Why it is important: It is the heart of Agile thinking.

Simple explanation: Like a list of promises for how to work well.

Real-life example: Banks that value people and teamwork over strict rules.

School example: A class that values learning and teamwork over just marks.

Home example: A family that values time together over strict schedules.

Nigerian example: A business that values customer happiness over paperwork.

Illustration:

  Agile Manifesto:

  "We value these four things more than the old way."
  

Mini summary: The Agile Manifesto describes what Agile values most. It has four main values.

Lesson 6: Agile Value 1 – People and Interactions

Definition: Agile values people and their communication more than strict processes and tools.

Why it is important: Tools do not solve problems. People do.

Simple explanation: A good team with simple tools beats a bad team with fancy tools.

Real-life example: Banks invest in training staff, not just buying software.

School example: A team that talks and helps each other beats one that only follows rules.

Home example: Families that talk openly work better together.

Nigerian example: A market where traders help each other succeeds more than one where nobody talks.

Illustration:

  Value 1:

  People and Interactions  >  Processes and Tools
  

Mini summary: Agile values people and communication over tools and rules.

Lesson 7: Agile Value 2 – Working Results

Definition: Agile values working results more than long documents and plans.

Why it is important: A finished product is more useful than a stack of papers.

Simple explanation: A working bicycle is better than a hundred pages about bicycles.

Real-life example: Banks prefer an app that works over a huge design document.

School example: A finished project is better than just a plan.

Home example: A cooked meal is better than just a recipe.

Nigerian example: A trader who sells goods succeeds more than one who only talks about them.

Illustration:

  Value 2:

  Working Results  >  Documents and Plans
  

Mini summary: Agile values real, working results over long documents.

Lesson 8: Agile Value 3 – Teamwork with Customers

Definition: Agile values teamwork with customers more than strict contracts.

Why it is important: When customers are part of the team, the result is better.

Simple explanation: Like working with a friend on a project instead of just following instructions.

Real-life example: Banks work with customers to design apps they love.

School example: Students work with teachers to plan projects.

Home example: Families plan trips together.

Nigerian example: A trader listens to customers and changes products to match their needs.

Illustration:

  Value 3:

  Teamwork with Customers  >  Strict Contracts
  

Mini summary: Agile values teamwork with customers over strict contracts.

Lesson 9: Agile Value 4 – Responding to Change

Definition: Agile values responding to change more than sticking to a fixed plan.

Why it is important: The world changes. Good teams change with it.

Simple explanation: Like changing direction when you see a better path.

Real-life example: Banks change their apps when customers want new features.

School example: Students change their project when the teacher gives new ideas.

Home example: Families change plans when the weather changes.

Nigerian example: A trader changes prices when market conditions change.

Illustration:

  Value 4:

  Responding to Change  >  Following a Fixed Plan
  

Mini summary: Agile values responding to change over sticking to a fixed plan.

Lesson 10: The 12 Agile Principles – Part 1

Definition: The 12 Agile Principles are rules that guide Agile teams.

Why it is important: They turn values into daily actions.

Simple explanation: Like the rules of a game that everyone follows.

Real-life example: Banks use these principles in project planning.

School example: Students use them for group work.

Home example: Families use them in chores.

Nigerian example: Businesses use them for customer service.

Illustration:

  Principles 1–4:

  1. Satisfy the customer with early and continuous delivery.
  2. Welcome changing requirements, even late in the project.
  3. Deliver working results frequently.
  4. Business people and developers must work together daily.
  

Mini summary: Principles 1–4 focus on customers, change, frequent delivery, and teamwork.

Lesson 11: The 12 Agile Principles – Part 2

Definition: The next four principles focus on people and quality.

Why it is important: They keep teams motivated and produce good work.

Simple explanation: Like rules about how to treat your team well.

Real-life example: Banks keep teams small and well-motivated.

School example: Groups have clear roles and trust each other.

Home example: Families share chores fairly.

Nigerian example: Businesses keep teams small and focused.

Illustration:

  Principles 5–8:

  5. Build projects around motivated people.
  6. Face-to-face conversation is the best communication.
  7. Working results are the main measure of progress.
  8. Agile processes promote sustainable work.
  

Mini summary: Principles 5–8 focus on motivated teams, talking, real results, and steady pace.

Lesson 12: The 12 Agile Principles – Part 3

Definition: The last four principles focus on quality and improvement.

Why it is important: They help teams stay excellent and keep getting better.

Simple explanation: Like rules for always improving your work.

Real-life example: Banks review their work every week.

School example: Students review group work and improve.

Home example: Families discuss and improve routines.

Nigerian example: Businesses review customer feedback and improve.

Illustration:

  Principles 9–12:

   9. Continuous attention to quality.
  10. Simplicity – do only what is needed.
  11. Best results come from self-organising teams.
  12. The team reflects and improves regularly.
  

Mini summary: Principles 9–12 focus on quality, simplicity, self-organisation, and improvement.

Lesson 13: Agile Mindset vs Agile Methods

Definition: The Agile mindset is a way of thinking. Agile methods (like Scrum and Kanban) are ways of doing.

Why it is important: You can use Agile methods without the mindset and still fail.

Simple explanation: Mindset is the heart. Methods are the hands.

Real-life example: Banks with the mindset welcome change, not just follow the steps.

School example: A group that truly helps each other is using the mindset.

Home example: A family that listens is using the mindset.

Nigerian example: A business that changes to serve customers better has the mindset.

Illustration:

  Mindset:
   - Trust
   - Openness
   - Feedback
   - Change is good

  Methods:
   - Scrum
   - Kanban
   - Standups
   - Sprints
  

Mini summary: The Agile mindset is a way of thinking. Agile methods are ways of working.

Lesson 14: Common Mistakes in Agile

Definition: Mistakes happen. Knowing them helps you avoid them.

Why it is important: Agile can fail if used wrongly.

Simple explanation: Like using a bicycle as a chair – it works, but it is not the point.

Real-life example: Teams that have standups but never improve.

School example: Groups that talk a lot but never finish work.

Home example: Families that plan but never do.

Nigerian example: Businesses that write Agile words but still work the old way.

Table of common mistakes:

Mini summary: Common mistakes: only ceremonies, no feedback, fear of change. Focus on the mindset.

Lesson 15: Best Practices for Agile Beginners

Definition: Best practices are good habits that help Agile work well.

Why it is important: Good habits make Agile feel easy.

Simple explanation: Like training before a race – it makes you ready.

Real-life example: Banks start with small Agile teams first.

School example: Students start with small group projects.

Home example: Families start with one small habit change.

Nigerian example: Businesses start Agile on one product at a time.

List of best practices:

• Start small – one team, one project.
• Work in small cycles.
• Check with users often.
• Welcome feedback.
• Keep meetings short.
• Keep teams small and trusted.
• Focus on real results.
• Improve after every cycle.
• Learn the mindset, not just the steps.
• Celebrate small wins.

Mini summary: Best practices: start small, work in cycles, get feedback, improve each time.

Lesson 16: Putting It All Together – Your Agile Foundation

You now have a strong foundation in Agile thinking.

What you learned:

• What Agile is
• Where it came from
• What Waterfall is and why Agile is different
• The 4 Agile values
• The 12 Agile principles
• Mindset vs methods
• Common mistakes and best practices

Next steps: In Module Two, you will learn about Agile teams, roles, and ceremonies.

Illustration:

  Your Learning Journey:

  Module 1: Foundations
       |
       V
  Module 2: Teams & Ceremonies
       |
       V
  Module 3: Scrum & Kanban
       |
       V
  Module 4: Real Life & Certification
       |
       V
  Agile Expert 🎉
  

Mini summary: You now understand the basics of Agile. Time to learn how Agile teams work!

Key Vocabulary

Important Concepts

• Agile works in small steps: Check and improve often.
• Agile began in 2001: With the Agile Manifesto.
• Waterfall is the old way: One long order, no going back.
• Four Agile values: People, results, teamwork, change.
• Twelve Agile principles: Rules that guide Agile teams.
• Mindset is heart: Methods are hands.
• Common mistakes: Doing ceremonies without mindset.
• Best practices: Start small, improve often.
• Feedback matters: Improves every cycle.
• Change is welcome: It makes results better.

Step-by-step Explanations

How to start using Agile step by step

1. Choose a small project.
2. Break it into small steps.
3. Work on one step at a time.
4. Check with users or teacher after each step.
5. Improve based on feedback.
6. Repeat until done.
7. Celebrate your finished work.

How to work in a small Agile cycle step by step

1. Plan what you will do.
2. Do the work.
3. Check the result.
4. Learn from feedback.
5. Improve for next time.

How to choose between Waterfall and Agile step by step

1. Is the task likely to change? → Choose Agile.
2. Is the task fixed and simple? → Waterfall may work.
3. Do you have access to users? → Agile works well.
4. Do you need to deliver slowly? → Agile works well.
5. When in doubt, try Agile.

How to give good feedback step by step

1. Say something positive first.
2. Mention what could be better.
3. Suggest how to improve.
4. Be kind and clear.
5. Listen to the other person.

How to improve after every cycle step by step

1. Ask: What went well?
2. Ask: What went wrong?
3. Ask: What will we change?
4. Write down your ideas.
5. Try one change next cycle.

Real-life Examples

• Software companies: Release updates every week.
• Banks: Add new app features based on customer feedback.
• Schools: Do group projects in weekly steps.
• Homes: Plan meals and change based on taste.
• Startups: Test small ideas before going big.

Nigerian Examples

• Lagos fintechs: Release app updates every month.
• Abuja restaurants: Try new dishes with a few customers first.
• Port Harcourt traders: Buy small stock and see what sells.
• Onitsha tailors: Make one dress first before a full order.
• Kano schools: Group projects checked weekly.

Fun Examples Children Can Relate To

• Building a LEGO set: One section at a time, checking as you go.
• Baking: Taste the batter before baking the cake.
• Drawing: Show a friend and improve.
• Sports: Practice one skill at a time.
• Homework: Do one question, then check.

Everyday Examples

• Shopping: Buy a little, see if you like it, buy more later.
• Cooking: Taste as you cook and adjust.
• Homework: Write one paragraph, then read it again.
• Cleaning: Clean one room, then move on.
• Learning: Study in short blocks with small quizzes.

Parent Tips

• Show your child how small steps help.
• Encourage them to ask for feedback often.
• Teach them to improve each time.
• Help them see change as a good thing.
• Read stories of teams that used Agile well.
• Try small Agile habits at home.
• Praise them for finishing small steps.
• Talk about the 4 values at home.
• Celebrate improvement over perfection.
• Support their learning journey.

Interesting Facts

• The Agile Manifesto is only 68 words long.
• Agile is now used in schools, banks, and hospitals.
• Teams using Agile often finish projects faster.
• Agile helps teams make fewer big mistakes.
• Nigerian fintechs use Agile every day.
• Some Agile teams deliver new results every week.
• Agile has spread from software to farming and fashion.
• Agile welcomes change – it does not fear it.

Did You Know?

• Did you know Agile means "able to move quickly"?
• Did you know 17 people wrote the Agile Manifesto?
• Did you know Agile is popular in Nigerian banks?
• Did you know some schools teach Agile to students?
• Did you know Agile teams plan only a few weeks ahead?
• Did you know Agile works well for group projects?
• Did you know Agile helps teams hear customer feedback early?
• Did you know the Agile mindset matters more than methods?

Remember This

• Agile works in small steps.
• Agile began in 2001.
• Waterfall is the old way.
• Agile has 4 values and 12 principles.
• Mindset matters more than methods.
• Feedback improves the work.
• Change is welcome in Agile.
• Start small when using Agile.
• Keep improving each cycle.
• Celebrate small wins.

Common Mistakes

• Only doing ceremonies without mindset.
• Not getting customer feedback.
• Too many rules.
• Ignoring feedback.
• Fearing change.
• Big team, no trust.
• Forgetting to reflect.
• Not celebrating wins.

Best Practices

• Start small – one team, one project.
• Work in small cycles.
• Check with users often.
• Welcome feedback.
• Keep meetings short.
• Keep teams small and trusted.
• Focus on real results.
• Improve after every cycle.
• Learn the mindset, not just the steps.
• Celebrate small wins.

Illustrations and Diagrams

Waterfall vs Agile

  Waterfall:  Plan → Design → Build → Test → Deliver

  Agile:      Plan → Do → Check → Improve
                  ↑                |
                  |________________|
                    Repeat often 🎉
  

The 4 Agile Values

  People       >  Tools
  Results      >  Documents
  Teamwork     >  Contracts
  Change       >  Fixed Plan
  

Agile Cycle

  Plan → Do → Check → Improve
  

Mindset vs Methods

  Mindset: Trust, Openness, Feedback
  Methods: Scrum, Kanban, Standups
  

Your Learning Journey

  Module 1: Foundations
       |
       V
  Module 2: Teams & Ceremonies
       |
       V
  Module 3: Scrum & Kanban
       |
       V
  Module 4: Real Life & Certification
       |
       V
  Agile Expert 🎉
  

Comparison Tables

Waterfall vs Agile

Mindset vs Methods

4 Agile Values

Agile vs No Agile

Lesson Summaries

Lesson 1: Agile means working in small steps with feedback.

Lesson 2: Agile began in 2001 with the Agile Manifesto.

Lesson 3: Waterfall does everything in one long order.

Lesson 4: Agile works in small cycles and improves each time.

Lesson 5: The Agile Manifesto describes what Agile values.

Lesson 6: Agile values people over tools.

Lesson 7: Agile values working results over long documents.

Lesson 8: Agile values teamwork with customers over strict contracts.

Lesson 9: Agile values responding to change over fixed plans.

Lesson 10: Principles 1–4 focus on customers, change, delivery, teamwork.

Lesson 11: Principles 5–8 focus on motivation, talking, results, pace.

Lesson 12: Principles 9–12 focus on quality, simplicity, self-organisation, improvement.

Lesson 13: Mindset is a way of thinking; methods are ways of doing.

Lesson 14: Common mistakes: only ceremonies, no feedback.

Lesson 15: Best practices: start small, work in cycles, improve often.

Lesson 16: You now have a strong Agile foundation.

End-of-Module Summary

Congratulations! You have finished Module One of the Agile Fundamentals course. You learned what Agile is and why it matters. You learned where Agile came from and what Waterfall is. You learned the 4 Agile values and the 12 Agile principles. You learned the difference between an Agile mindset and Agile methods. You learned common mistakes and best practices. Most importantly, you now understand that Agile means working in small steps, checking often, and improving as you go. In the next module, you will learn about Agile teams, roles, and ceremonies. Keep learning, and you will become an Agile expert!

Frequently Asked Questions

1. What is Agile? A way of working in small steps with feedback.
2. Where did Agile come from? From the Agile Manifesto in 2001.
3. What is Waterfall? The old way of doing everything in one long order.
4. What are the 4 Agile values? People, results, teamwork, change.
5. What are the 12 Agile principles? Rules that guide Agile teams.
6. What is the Agile mindset? A way of thinking that welcomes trust and feedback.
7. What is an Agile method? A way of doing, like Scrum or Kanban.
8. Why is Agile better for changing tasks? It welcomes change often.
9. Can I use Agile at school? Yes, for group projects and study plans.
10. Can I use Agile at home? Yes, for chores, cooking, and planning.

Matching Exercises

Match the term to its meaning.

Answers: 1-C, 2-A, 3-D, 4-B, 5-E

Scenario-based Exercises

1. Scenario: Your teacher gives a four-week project. What is the Agile way?
   Answer: Work in weekly steps and check often.
2. Scenario: Your team planned everything but the teacher wants changes. What do you do?
   Answer: Welcome the change and adjust the plan.
3. Scenario: You finish a small part of your project. What do you do?
   Answer: Show it to the teacher for feedback.
4. Scenario: Your group keeps arguing. What can help?
   Answer: Focus on people and communication (Value 1).
5. Scenario: You are unsure if Agile is right. What do you do?
   Answer: Try it on a small project first.

Group Activity

Title: “Agile vs Waterfall Together”

Instructions: In groups of 3–4, choose a small task (like planning a class party). Split into two groups: one plans in Waterfall style, one in Agile style. Then compare: Which group finished faster? Which got better feedback? Which would you use again? Present your findings to the class.

Goal: Experience the difference between Agile and Waterfall.

Individual Activity

Task: Choose a small personal task (like cleaning your room or writing an essay). Then:

• Write a plan using Waterfall style.
• Write a plan using Agile style.
• Try the Agile plan for one day.
• Write down what felt different.

Hint: Notice how checking and improving changes the work.

Mini Project

Project: “My Agile Mini Plan”

Choose a small project at home or school. Then create an Agile plan with:

• Title of the project.
• The 4 values you will follow.
• Three small steps (cycles).
• When you will check for feedback.
• What you will improve each cycle.
• How you will celebrate at the end.

Example:

  Project: Build a family budget tracker
  Values: People, results, teamwork, change
  Steps: Week 1 gather income; Week 2 add expenses; Week 3 review
  Feedback: Show family each week
  Improve: Add categories they ask for
  Celebrate: Family pizza night 🎉
  

Practical Assignment

Assignment: Interview a teacher, parent, or family friend. Ask them:

1. Have they ever worked on a project that changed halfway?
2. What did they do when things changed?
3. Would Agile have helped?
4. What small Agile habit could they try?

Then write a one-page report connecting their answers to Agile values and principles.

Submit: Your report with at least three Agile ideas.

Key Takeaways

• Agile works in small steps.
• Agile began in 2001.
• Waterfall is the old way.
• Agile has 4 values and 12 principles.
• Mindset matters more than methods.
• Feedback improves the work.
• Change is welcome in Agile.
• Start small when using Agile.
• Keep improving each cycle.
• Celebrate small wins.

Classroom Discussion Questions

1. What is Agile, and why was it created?
2. How is Agile different from Waterfall?
3. Which of the 4 Agile values do you like most, and why?
4. Why are the 12 principles important?
5. What is the difference between an Agile mindset and an Agile method?
6. Can Agile work at home? Give an example.
7. Why is feedback so important in Agile?
8. What mistake do teams often make with Agile?
9. What would you like to try with Agile first?
10. What did Chidi learn from Ada’s group project?

Preparation for Module Two

In Module Two, we will learn about Agile teams, roles, and ceremonies. We will cover:

• Cross-functional teams.
• Common Agile roles.
• Daily standups.
• Sprint planning and review.
• Retrospectives.
• Working agreements.

To prepare, complete the practical assignment and bring your Agile mini plan. Review the key vocabulary. Think about what makes a great team. Bring your curiosity!

See you in Module Two!

End of Module One – Agile Fundamentals

Module Three: Scrum, Kanban and Common Agile Practices – Choosing Your Agile Way

“Agile Fundamentals” – A beginner’s guide to working smarter together

Module Introduction

Welcome back, young Agile explorer! In Module One, you learned what Agile is – its values and principles. In Module Two, you learned how Agile teams work – their roles and ceremonies like standups, sprint planning, reviews, and retrospectives.

Now it is time to explore the frameworks – the actual methods that teams use to apply Agile. The two most popular frameworks are Scrum and Kanban. A framework is like a recipe. It tells you what steps to follow. Scrum and Kanban are two different recipes for working in an Agile way.

Think of it like this: Agile is the idea of "cooking healthy meals". Scrum and Kanban are two different ways to plan, cook, and serve those meals. One is more structured (Scrum). One is more flexible (Kanban). Both work well.

In this module, we will learn about Scrum and Kanban in simple language. We will learn about backlogs, user stories, estimation, prioritisation, velocity, and flow. By the end, you will be able to choose the right framework for your team.

Let’s begin!

Learning Objectives

After finishing this module, you will be able to:

• Explain what a framework is.
• Describe Scrum in simple words.
• Describe Kanban in simple words.
• Explain what a backlog is.
• Write a simple user story.
• Explain estimation and prioritisation.
• Understand velocity and flow.
• Compare Scrum and Kanban.
• Choose the right framework for a task.
• Complete a mini project and practical assignment.

Warm-up Story: Ngozi’s Two Bakeries

Ngozi is 14 years old and lives in Ibadan. Her family owns two small bakeries. One bakery is called "Bread Sprint". The other is called "Bread Flow".

Ngozi noticed that the two bakeries worked differently.

At Bread Sprint, the bakers worked in two-week cycles. At the start of each cycle, they chose a small list of things to bake: "This cycle we will bake 100 loaves of bread, 50 meat pies, and 30 cakes." They called this list their "sprint backlog".

Every morning, the bakers held a standup. They answered three questions. They had a "Product Owner" who decided what to bake next. They had a "Scrum Master" who helped remove problems.

At the end of two weeks, they reviewed what they baked and improved for the next cycle. This worked very well. Bread Sprint always finished its goals on time.

At Bread Flow, the bakers worked differently. They had one big list of things to bake – not split into cycles. They called this list "the board". The board had three columns: "To Bake", "Baking", and "Done". As bread moved through the bakery, it moved across the board.

The bakers at Bread Flow did not work in cycles. They just kept the bread flowing. They had a rule: "No more than three loaves in the 'Baking' column at once." If the column was full, they could not start another loaf until one moved to "Done". This stopped them from being overloaded.

Bread Flow was very flexible. If a customer ordered 20 cakes suddenly, they could add it to the board right away.

Ngozi asked her mother, "Which bakery is better?" Her mother said, "Both are good. Bread Sprint is better for planned work. Bread Flow is better for changing work. It depends on what the bakery needs."

Ngozi understood. She learned that Scrum and Kanban are two ways to do Agile. Each fits different situations.

Moral of the story: Scrum works in cycles with clear goals. Kanban works with a flowing board and limits work in progress. Both are good – choose the one that fits your task.

Main Lessons

Lesson 1: What is an Agile Framework?

Definition: An Agile framework is a set of rules and practices for using Agile.

Why it is important: Frameworks help teams apply Agile in a structured way.

Simple explanation: Like a recipe for baking a cake. Follow the steps, and you get a good result.

Real-life example: Banks use Scrum and Kanban as frameworks.

School example: A group project can use Scrum or Kanban.

Home example: Families plan chores using Scrum or Kanban.

Nigerian example: Traders use Kanban for daily market tasks.

Illustration:

  Agile = Idea

  Frameworks = Recipes

  Scrum     Kanban     Others
  

Mini summary: Agile frameworks are recipes for working in an Agile way. Scrum and Kanban are the most popular.

Lesson 2: What is Scrum?

Definition: Scrum is an Agile framework where teams work in short cycles called sprints.

Why it is important: Scrum gives teams clear structure and goals.

Simple explanation: Like working in two-week "seasons" with a clear goal for each season.

Real-life example: Banks use Scrum to build new app features.

School example: Groups work in weekly cycles to finish a project.

Home example: Families plan two-week projects like repainting a room.

Nigerian example: A trader runs a two-week sprint to prepare for a big market day.

Illustration:

  Scrum Sprints:

  Sprint 1  →  Sprint 2  →  Sprint 3
  (2 weeks)    (2 weeks)    (2 weeks)
  

Mini summary: Scrum works in short cycles called sprints. Each sprint has a clear goal.

Lesson 3: What is Kanban?

Definition: Kanban is an Agile framework that uses a visual board to track work flowing through stages.

Why it is important: Kanban helps teams see what is happening and avoid overload.

Simple explanation: Like a board with columns: To Do, Doing, Done.

Real-life example: Banks use Kanban for customer support tickets.

School example: Groups use a Kanban board for homework tasks.

Home example: Families use a Kanban board for chores.

Nigerian example: A tailor uses Kanban for tailoring orders.

Illustration:

  Kanban Board:

  +--------+  +--------+  +--------+
  | To Do  |  | Doing  |  | Done   |
  +--------+  +--------+  +--------+
  | Task A |  | Task C |  | Task E |
  | Task B |  | Task D |  |        |
  +--------+  +--------+  +--------+
  

Mini summary: Kanban uses a visual board to track work. It shows what is happening at a glance.

Lesson 4: What is a Backlog?

Definition: A backlog is a list of all the work that needs to be done.

Why it is important: A backlog keeps work organised and visible.

Simple explanation: Like a shopping list of everything you need to buy.

Real-life example: Banks keep a backlog of app features.

School example: Groups list all tasks for a project.

Home example: Families keep a backlog of chores.

Nigerian example: Traders list all goods to restock.

Illustration:

  Backlog Example:

  1. Design homepage
  2. Add login button
  3. Test on phones
  4. Write help page
  

Mini summary: A backlog is a list of all work. It keeps the team organised.

Lesson 5: The Product Backlog and Sprint Backlog

Definition: The Product Backlog is the full list. The Sprint Backlog is the small list chosen for one sprint.

Why it is important: Splitting the big list makes work manageable.

Simple explanation: Like a full shopping list (Product Backlog) and today’s short list (Sprint Backlog).

Real-life example: Banks keep a product backlog of all features.

School example: Groups choose three tasks for the week.

Home example: Families pick today’s chores from a big list.

Nigerian example: Traders choose today’s goods from a big stock list.

Illustration:

  Product Backlog:         Sprint Backlog:
  - 20 items total         - 3 items this sprint

  Big list        →        Small list
  

Mini summary: The Product Backlog is the full list. The Sprint Backlog is the short list for one sprint.

Lesson 6: What is a User Story?

Definition: A user story is a short description of something a user wants.

Why it is important: User stories keep work focused on real needs.

Simple explanation: Like writing: "As a student, I want a study plan so I can pass my exams."

Real-life example: Banks write user stories for customers.

School example: Groups write user stories for teachers.

Home example: Families write stories like "As a family, we want a simple chore chart."

Nigerian example: A trader writes: "As a customer, I want to order by WhatsApp."

Illustration:

  User Story Format:

  As a [user],
  I want [something],
  So that [reason].

  Example:
  As a student, I want a study plan, so that I pass my exams.
  

Mini summary: User stories describe what users want. They follow a simple format.

Lesson 7: Estimation – Guessing Size

Definition: Estimation means guessing how big or long a task will take.

Why it is important: It helps teams plan how much work fits in a sprint.

Simple explanation: Like guessing: "This homework is small, this one is big."

Real-life example: Banks estimate story points for features.

School example: Groups estimate time per subject.

Home example: Families estimate time for chores.

Nigerian example: Traders estimate how long a delivery will take.

Illustration:

  Estimation Example:

  Small:  1 point   (quick task)
  Medium: 3 points  (few hours)
  Large:  5 points  (a full day)
  XL:     8 points  (too big — split it)
  

Mini summary: Estimation guesses the size of tasks. It helps plan sprints.

Lesson 8: Prioritisation – What First?

Definition: Prioritisation means deciding which tasks to do first.

Why it is important: You cannot do everything at once.

Simple explanation: Like packing the most important items first when travelling.

Real-life example: Banks prioritise features customers need most.

School example: Students do the most urgent homework first.

Home example: Families do urgent chores first.

Nigerian example: Traders prioritise fast-selling goods.

Illustration:

  Prioritisation Example:

  High: Pay rent today
  Medium: Buy food this week
  Low: Watch a movie

  Do high first!
  

Mini summary: Prioritisation means choosing what to do first. Do the most important tasks early.

Lesson 9: Velocity – How Fast Is Your Team?

Definition: Velocity is how much work a team finishes in one sprint.

Why it is important: Velocity helps teams plan how much to take on.

Simple explanation: Like measuring how many laps a runner runs in 10 minutes.

Real-life example: Banks track velocity to predict future work.

School example: Groups track how many tasks they finish per week.

Home example: Families track how many chores get done on weekends.

Nigerian example: Traders track how many orders are delivered per day.

Illustration:

  Velocity:

  Sprint 1: 20 points
  Sprint 2: 22 points
  Sprint 3: 21 points
  Average: 21 points per sprint
  

Mini summary: Velocity is how much work a team finishes in a sprint. It helps plan future sprints.

Lesson 10: Flow – Keeping Work Moving

Definition: Flow is how smoothly work moves from start to finish.

Why it is important: Good flow means fast delivery.

Simple explanation: Like water flowing through a pipe. No blockages.

Real-life example: Banks track flow in customer service queues.

School example: Groups track flow in group work.

Home example: Families track flow of chores.

Nigerian example: Traders track flow of orders from customer to delivery.

Illustration:

  Flow Example:

  Good flow:        Bad flow:
  Task → Task → Done   Task → Stuck → Stuck → Done
  (fast!)             (slow!)
  

Mini summary: Flow shows how smooth the work is. Good flow means fast delivery.

Lesson 11: Work In Progress (WIP) Limits

Definition: A WIP limit is a rule that says how many tasks can be "in progress" at once.

Why it is important: Too many tasks at once slows everything down.

Simple explanation: Like cooking. Too many pots at once makes a mess.

Real-life example: Banks limit open tickets per agent.

School example: Groups limit how many tasks to work on at once.

Home example: Families limit chores in progress.

Nigerian example: Traders limit open deliveries in one day.

Illustration:

  WIP Limit Example:

  To Do     Doing (max 3)    Done
  Task A    Task C
  Task B    Task D
  Task E    Task F

  New task waits until one moves to Done.
  

Mini summary: WIP limits stop teams from doing too much at once. It keeps flow smooth.

Lesson 12: Scrum vs Kanban

Definition: Scrum and Kanban are both Agile frameworks but work differently.

Why it is important: Knowing the difference helps you choose the right one.

Simple explanation: Scrum is like a relay race (batches). Kanban is like a flowing river (continuous).

Real-life example: Banks use Scrum for new projects and Kanban for support.

School example: Groups use Scrum for projects and Kanban for homework.

Home example: Families use Scrum for big events and Kanban for daily chores.

Nigerian example: Traders use Scrum for big market seasons and Kanban for daily selling.

Illustration:

  Scrum:            Kanban:

  Sprint 1          To Do → Doing → Done
  Sprint 2          Continuous flow
  Sprint 3
  (cycles)          (continuous)
  

Mini summary: Scrum works in cycles. Kanban works continuously. Choose based on your task.

Lesson 13: Other Agile Frameworks

Definition: Agile has many frameworks besides Scrum and Kanban.

Why it is important: Different teams need different tools.

Simple explanation: Like different tools in a toolbox.

Real-life example: Banks use SAFe for large teams.

School example: Groups can use Scrumban (a mix).

Home example: Families can invent their own style.

Nigerian example: Businesses choose frameworks that fit their size.

Illustration:

  Other Agile Frameworks:

  - Scrumban (Scrum + Kanban)
  - XP (Extreme Programming)
  - SAFe (Scaled Agile Framework)
  - Lean
  - Crystal
  

Mini summary: Many Agile frameworks exist. Choose one that fits your team size and task.

Lesson 14: Common Mistakes with Frameworks

Definition: Mistakes happen. Knowing them helps you avoid them.

Why it is important: Using the wrong framework or misusing it hurts the team.

Simple explanation: Like using a hammer for screws. It works, but not well.

Real-life example: Banks sometimes over-complicate Scrum.

School example: Groups follow steps without understanding.

Home example: Families copy routines that do not fit.

Nigerian example: Businesses use Agile words but work the old way.

Table of common mistakes:

Mini summary: Common mistakes: wrong framework, no goal, too many tasks. Fix them early.

Lesson 15: Best Practices for Choosing a Framework

Definition: Best practices help you pick and use the right framework.

Why it is important: A good fit makes work easier.

Simple explanation: Like choosing the right shoes for the right activity.

Real-life example: Banks use Scrum for big projects and Kanban for support.

School example: Groups pick Scrumban for mixed work.

Home example: Families pick a simple board for chores.

Nigerian example: Businesses start simple and improve.

List of best practices:

• Start simple.
• Match framework to the task.
• Use Scrum for planned work.
• Use Kanban for continuous work.
• Keep goals clear.
• Set WIP limits.
• Estimate tasks roughly.
• Prioritise by value.
• Review and improve.
• Do not over-complicate.

Mini summary: Best practices: keep it simple, match framework to task, improve each cycle.

Lesson 16: Putting It All Together – Your Framework Toolkit

You now know how to use Scrum and Kanban.

What you learned:

• What an Agile framework is
• Scrum basics
• Kanban basics
• Backlogs and user stories
• Estimation and prioritisation
• Velocity and flow
• WIP limits
• Scrum vs Kanban
• Other frameworks
• Common mistakes and best practices

Next steps: In Module Four, you will apply Agile in real life and complete your certification project.

Illustration:

  Your Learning Journey:

  Module 1: Foundations
       |
       V
  Module 2: Teams & Ceremonies
       |
       V
  Module 3: Scrum & Kanban
       |
       V
  Module 4: Real Life & Certification
       |
       V
  Agile Expert 🎉
  

Mini summary: You now know Scrum and Kanban. Time to use Agile in real life!

Key Vocabulary

Important Concepts

• Frameworks are recipes: Scrum and Kanban are the most popular.
• Scrum works in sprints: Short cycles with clear goals.
• Kanban works in flow: Tasks move across a board.
• Backlogs organise work: Big list (Product) and small list (Sprint).
• User stories focus on real needs: They follow a simple format.
• Estimation helps planning: Guess the size of tasks.
• Prioritisation decides order: Do important work first.
• Velocity shows speed: How much a team finishes per sprint.
• WIP limits keep flow smooth: Do not overload the team.
• Choose the right framework: Match to your task and team.

Step-by-step Explanations

How to set up a Scrum board step by step

1. Create a Product Backlog.
2. Choose items for the Sprint Backlog.
3. Set a sprint goal.
4. Break work into tasks.
5. Estimate each task.
6. Start the sprint.

How to set up a Kanban board step by step

1. Draw columns: To Do, Doing, Done.
2. Add all tasks as cards.
3. Move cards as work progresses.
4. Set a WIP limit for each column.
5. Review the board daily.
6. Improve flow continuously.

How to write a user story step by step

1. Choose the user (student, customer, teacher).
2. Write: "As a [user]..."
3. Add: "I want [something]..."
4. Add: "So that [reason]."
5. Keep it short and clear.

How to estimate tasks step by step

1. List each task.
2. Compare sizes (small, medium, large).
3. Assign points (1, 3, 5, 8).
4. Agree with the team.
5. Split tasks that are too big.

How to improve flow step by step

1. Set WIP limits.
2. Watch the board daily.
3. Find where tasks get stuck.
4. Fix the blockage.
5. Review weekly.
6. Keep improving.

Real-life Examples

• Banks: Scrum for new features, Kanban for support.
• Schools: Scrum for projects, Kanban for homework.
• Homes: Scrum for events, Kanban for chores.
• Startups: Kanban for daily work, Scrum for launches.
• Hospitals: Kanban for patient flow.

Nigerian Examples

• Lagos fintechs: Scrum for new app features.
• Abuja restaurants: Kanban for lunch orders.
• Port Harcourt tailors: Kanban for stitching orders.
• Onitsha traders: Scrumban for market season prep.
• Kano schools: Scrum for term projects.

Fun Examples Children Can Relate To

• LEGO build: Scrum for big builds, Kanban for small tasks.
• Homework: Kanban board for assignments.
• Birthday party: Scrum for two-week prep.
• Games: Kanban for finishing levels.
• Reading: Kanban for book list.

Everyday Examples

• Shopping: Kanban for shopping list.
• Cleaning: Scrum for weekend deep clean.
• Homework: Kanban for daily tasks.
• Cooking: Kanban for recipes to try.
• Learning: Scrum for a 2-week topic sprint.

Parent Tips

• Show your child a simple Kanban board at home.
• Try a two-week Scrum sprint for a family project.
• Teach them the user story format.
• Practice prioritising chores together.
• Read about Scrum and Kanban.
• Celebrate finishing each sprint or column.
• Encourage simple over complicated.
• Review what worked each week.
• Let them teach you what they learned.
• Support their learning journey.

Interesting Facts

• Scrum is the most used Agile framework in the world.
• Kanban means "signboard" in Japanese.
• Scrum sprints are usually 1–4 weeks long.
• Kanban boards work well in factories and offices.
• WIP limits often make teams finish faster.
• Velocity is measured in "story points".
• Scrumban mixes Scrum and Kanban.
• Nigerian fintechs use both Scrum and Kanban daily.

Did You Know?

• Did you know Kanban was invented in Toyota factories?
• Did you know Scrum teams have a "Definition of Done"?
• Did you know Kanban boards can be as simple as sticky notes?
• Did you know sprint lengths can be adjusted?
• Did you know some teams run daily Kanban reviews?
• Did you know Agile frameworks are used in hospitals and schools?
• Did you know Scrumban is popular in startups?
• Did you know Nigerian banks use multiple frameworks at once?

Remember This

• Frameworks are recipes for Agile.
• Scrum works in sprints.
• Kanban works in flow.
• Backlogs organise work.
• User stories focus on needs.
• Estimation guesses size.
• Prioritisation decides order.
• Velocity shows speed.
• WIP limits keep flow smooth.
• Choose the right framework.

Common Mistakes

• Choosing the wrong framework.
• No clear sprint goal.
• Too many WIP items.
• Ignoring backlog order.
• No estimation.
• Following rules blindly.
• Over-complicating.
• Not improving each cycle.

Best Practices

• Start simple.
• Match framework to the task.
• Use Scrum for planned work.
• Use Kanban for continuous work.
• Keep goals clear.
• Set WIP limits.
• Estimate tasks roughly.
• Prioritise by value.
• Review and improve.
• Do not over-complicate.

Illustrations and Diagrams

Scrum Sprints

  Sprint 1 → Sprint 2 → Sprint 3
  (2 weeks)  (2 weeks)  (2 weeks)
  

Kanban Board

  +--------+  +--------+  +--------+
  | To Do  |  | Doing  |  | Done   |
  +--------+  +--------+  +--------+
  | Task A |  | Task C |  | Task E |
  | Task B |  | Task D |  |        |
  +--------+  +--------+  +--------+
  

User Story

  As a [user],
  I want [something],
  So that [reason].
  

WIP Limit

  Doing (max 3):

  Task C   Task D   Task F

  New task waits until one moves to Done.
  

Your Learning Journey

  Module 1: Foundations
       |
       V
  Module 2: Teams & Ceremonies
       |
       V
  Module 3: Scrum & Kanban
       |
       V
  Module 4: Real Life & Certification
       |
       V
  Agile Expert 🎉
  

Comparison Tables

Scrum vs Kanban

Product Backlog vs Sprint Backlog

Velocity vs Flow

Scrum vs Scrumban

Lesson Summaries

Lesson 1: Agile frameworks are recipes for working.

Lesson 2: Scrum works in short cycles called sprints.

Lesson 3: Kanban uses a visual board for flow.

Lesson 4: A backlog is a list of all work.

Lesson 5: Product Backlog is the full list; Sprint Backlog is the short list.

Lesson 6: User stories describe user needs.

Lesson 7: Estimation guesses the size of tasks.

Lesson 8: Prioritisation decides what to do first.

Lesson 9: Velocity is work done per sprint.

Lesson 10: Flow shows how smooth the work is.

Lesson 11: WIP limits keep flow smooth.

Lesson 12: Scrum works in cycles; Kanban flows continuously.

Lesson 13: Other frameworks include Scrumban, XP, SAFe.

Lesson 14: Common mistakes: wrong framework, no goal.

Lesson 15: Best practices: simple, matched, reviewed.

Lesson 16: You now know Scrum and Kanban.

End-of-Module Summary

Congratulations! You have finished Module Three of the Agile Fundamentals course. You learned what an Agile framework is. You learned Scrum and Kanban in simple language. You learned about backlogs, user stories, estimation, prioritisation, velocity, flow, and WIP limits. You learned how Scrum and Kanban compare and when to use each. You learned about other frameworks like Scrumban, XP, and SAFe. You learned common mistakes and best practices. Most importantly, you can now choose the right framework for a task and use it to work smarter. In the next module, you will apply Agile to real life and complete your certification project. Keep learning, and you will become an Agile expert!

Frequently Asked Questions

1. What is an Agile framework? A recipe for working in an Agile way.
2. What is Scrum? An Agile framework with short cycles called sprints.
3. What is Kanban? An Agile framework with a visual board.
4. What is a backlog? A list of all work.
5. What is a user story? A short description of a user need.
6. What is estimation? Guessing the size of a task.
7. What is prioritisation? Deciding what to do first.
8. What is velocity? Work finished per sprint.
9. What is flow? How smooth work moves.
10. What is a WIP limit? A rule on how many tasks can be active.

Matching Exercises

Match the term to its meaning.

Answers: 1-D, 2-A, 3-B, 4-C, 5-E

Scenario-based Exercises

1. Scenario: Your team has a big planned project. What framework fits?
   Answer: Scrum.
2. Scenario: Your team gets new tasks all day. What framework fits?
   Answer: Kanban.
3. Scenario: The board is overloaded in "Doing". What do you do?
   Answer: Add a WIP limit.
4. Scenario: Your tasks look unclear. What do you do?
   Answer: Write user stories.
5. Scenario: Your team plans too much each sprint. What do you check?
   Answer: Velocity.

Group Activity

Title: “Scrum or Kanban – You Choose”

Instructions: In groups of 3–4, choose a small project. First plan with Scrum (sprint goal, backlog, estimation). Then plan with Kanban (board, WIP limits). Compare which fits better. One person writes Scrum, one writes Kanban, one compares, and one presents. Share with the class.

Goal: Experience Scrum and Kanban in the same project.

Individual Activity

Task: Choose a personal task list (home or school). Then:

• Write it as a Product Backlog.
• Pick a Sprint Backlog for one week.
• Write two user stories.
• Estimate each task.
• Choose a framework: Scrum or Kanban.
• Explain your choice in 3 sentences.

Hint: Keep it small and clear.

Mini Project

Project: “My First Scrum or Kanban Board”

Create a plan for a two-week project using Scrum or Kanban. Include:

• Project title and goal.
• Backlog list (at least 8 items).
• Sprint Backlog or Kanban columns.
• Two user stories.
• Estimation for each task.
• WIP limit (if Kanban) or sprint goal (if Scrum).
• Review date and retrospective date.

Example:

  Project: My Study Plan for Exams
  Framework: Kanban
  Columns: To Do | Doing (max 2) | Done
  User Story: As a student, I want notes summarised, so I revise faster.
  Estimation: Small (1) to Large (5).
  Review: Every Sunday.
  Retrospective: Every Sunday after review.
  

Practical Assignment

Assignment: Pick a real group (family, school club, or small business). Then:

1. Choose Scrum or Kanban.
2. Set up a backlog or board.
3. Run it for one week.
4. Track results (velocity or flow).
5. Hold a review and a retrospective.
6. Write a one-page report of what happened.

Submit: Your report with a screenshot or sketch of your board/backlog.

Key Takeaways

• Frameworks are recipes for Agile.
• Scrum works in sprints.
• Kanban works in flow.
• Backlogs organise work.
• User stories focus on needs.
• Estimation guesses size.
• Prioritisation decides order.
• Velocity shows speed.
• WIP limits keep flow smooth.
• Choose the right framework.

Classroom Discussion Questions

1. What is an Agile framework, and why do we need one?
2. What is the difference between Scrum and Kanban?
3. Why is a backlog useful?
4. How can user stories help a team stay focused?
5. Why do we estimate tasks?
6. How does prioritisation help a team deliver more value?
7. What does velocity tell us?
8. Why does flow matter in Kanban?
9. What happens if a team ignores WIP limits?
10. What did Ngozi learn from her family’s two bakeries?

Preparation for Module Four

In Module Four, we will apply Agile in real life and complete the certification project. We will cover:

• Agile outside software (school, home, business).
• Agile for students and personal projects.
• Common Agile mistakes.
• Agile metrics and improvement.
• The certification project and presentation.

To prepare, complete the practical assignment and bring your board or backlog. Review the key vocabulary. Think about a real project where you would like to use Scrum or Kanban. Bring your curiosity!

See you in Module Four!

End of Module Three – Agile Fundamentals

Module Four: Agile in Real Life and Certification – Using Agile Everywhere

“Agile Fundamentals” – A beginner’s guide to working smarter together

Module Introduction

Welcome to the final module, young Agile expert! You have come a very long way. In Module One, you learned what Agile is. In Module Two, you learned about Agile teams, roles, and ceremonies. In Module Three, you learned about Scrum, Kanban, and other frameworks.

Now it is time to see Agile in real life. Agile is not just for software companies. It works for schools, families, small businesses, churches, sports teams, and even personal projects. Anything that has steps and needs feedback can be done with Agile.

In this module, we will learn how to use Agile at school, at home, and in business. We will also learn about common Agile mistakes, how to measure success, and how to keep improving. Finally, you will complete your certification project and present it.

By the end of this module, you will be a Certified Agile Expert, ready to bring Agile thinking to everything you do.

Let’s begin!

Learning Objectives

After finishing this module, you will be able to:

• Explain how Agile works outside software.
• Use Agile for school projects and study plans.
• Use Agile for personal and family projects.
• Use Agile in small businesses and market settings.
• Describe common Agile mistakes to avoid.
• Explain Agile metrics (velocity, flow, cycle time).
• Hold a simple review and retrospective.
• Prepare and present a certification project.
• Review everything you learned across all modules.
• Plan your next steps as an Agile expert.

Warm-up Story: Emeka’s Family Market Day

Emeka is 15 years old and lives in Port Harcourt. His family sells food at a big market every Saturday. Every week, the family struggled. Some items were missing. Others were too many. Customers complained about waiting too long.

Emeka remembered what he learned about Agile. He said, "Mummy, Daddy, let’s try Agile for our market day."

First, Emeka helped them create a backlog of everything needed for market day: buy rice, buy beans, buy oil, cook, pack, set up the stall, and so on.

Next, the family held a short sprint planning meeting each Thursday. They chose the most important items for that Saturday. They called this their "market sprint".

On market day, they used a Kanban board drawn on cardboard. Three columns: "To Do", "Doing", and "Done". As each task was finished, it moved across the board. Everyone could see what was happening.

After the market, the family held a retrospective. They asked:

• What went well?
• What went wrong?
• What will we change next week?

The first week, they learned that they needed more spoons. The second week, they learned to prepare food faster. The third week, they learned to arrange the stall better.

After one month, the family was much more organised. Sales went up. Customers were happier. Emeka’s father said, "This Agile thing works!"

Moral of the story: Agile works everywhere – even at a market stall. Backlogs, sprints, Kanban boards, and retrospectives help any family or business improve.

Main Lessons

Lesson 1: Agile Outside Software

Definition: Agile outside software means using Agile ideas for non-computer projects.

Why it is important: Agile works for any task that has steps and needs feedback.

Simple explanation: Like using a football strategy for a different game – the ideas still work.

Real-life example: Schools, hospitals, and shops use Agile ideas.

School example: Group projects use sprints and reviews.

Home example: Families use Kanban boards for chores.

Nigerian example: Market traders use backlogs and reviews.

Illustration:

  Agile Everywhere:

  School     Home     Business
  Projects   Chores   Sales
  

Mini summary: Agile works outside software too. Schools, homes, and businesses can all use it.

Lesson 2: Agile for School Projects

Definition: Agile for school means using backlogs, sprints, and reviews for class projects.

Why it is important: School projects often need feedback and changes.

Simple explanation: Like a group project split into weekly sprints with teacher check-ins.

Real-life example: Students use Kanban boards for homework.

School example: A science project done in weekly sprints.

Home example: A study plan split into weekly goals.

Nigerian example: Nigerian students use backlogs for exam prep.

Illustration:

  School Agile:

  Week 1 Sprint → Review → Week 2 Sprint → Review → Final
  

Step-by-step:

1. Write all tasks as a backlog.
2. Choose weekly sprint goals.
3. Hold quick standups with your group.
4. Show work to your teacher each week.
5. Hold a short retrospective.
6. Improve each week.

Mini summary: Agile makes school projects easier. Use sprints, reviews, and retrospectives.

Lesson 3: Agile for Study Plans

Definition: Agile study plans split learning into short focused sprints.

Why it is important: Spaced study with feedback works better than cramming.

Simple explanation: Like studying one topic per week and testing yourself.

Real-life example: Students use sprints for exam prep.

School example: Weekly subject sprints.

Home example: Family reading plans in sprints.

Nigerian example: Students use sprints before WAEC or JAMB.

Illustration:

  Study Sprint Example:

  Sprint 1: Maths basics
  Sprint 2: Maths practice
  Sprint 3: Review + test
  

Step-by-step:

1. List all topics.
2. Group into weekly sprints.
3. Set a goal per sprint.
4. Test yourself at the end.
5. Retrospect: what to change?
6. Move to the next sprint.

Mini summary: Agile study plans use short, focused sprints with self-tests.

Lesson 4: Agile for Personal Projects

Definition: Agile for personal projects uses backlogs and reviews for things you want to achieve.

Why it is important: Big personal goals feel easier in small sprints.

Simple explanation: Like building a reading habit in weekly sprints.

Real-life example: Personal fitness or learning new skills.

School example: Learning to code with sprints.

Home example: Learning a new recipe each week.

Nigerian example: Learning to play the talking drum in weekly sprints.

Illustration:

  Personal Sprint Example:

  Goal: Read 5 books this year
  Sprint 1: Book 1
  Sprint 2: Book 2
  Sprint 3: Book 3
  

Mini summary: Personal projects get easier with sprints and reviews.

Lesson 5: Agile for Families

Definition: Agile for families uses boards, sprints, and retrospectives for home tasks.

Why it is important: Families work better when tasks are clear and shared.

Simple explanation: Like a chore board with To Do, Doing, and Done.

Real-life example: Families use Kanban for chores.

School example: Families use sprints for homework routines.

Home example: Weekend sprint for cleaning the house.

Nigerian example: Family sprints for preparing for a big event.

Illustration:

  Family Board:

  To Do: Sweep, Wash plates
  Doing: Cook dinner
  Done: Take out trash
  

Step-by-step:

1. Write all chores on cards.
2. Draw three columns on a board.
3. Move cards as work is done.
4. Hold a short family review each week.
5. Retrospect: what can we improve?

Mini summary: Agile families use boards and reviews. Chores become easier and fairer.

Lesson 6: Agile for Small Businesses

Definition: Agile for small businesses means using sprints, boards, and reviews to serve customers better.

Why it is important: Small businesses need to change fast.

Simple explanation: Like trying a new product each month and checking sales.

Real-life example: Shops test new items in small batches.

School example: School shops try new snacks each term.

Home example: Family businesses try new markets.

Nigerian example: Nigerian market traders try new products in sprints.

Illustration:

  Small Business Sprint:

  Sprint 1: Try new product
  Review: Did customers like it?
  Sprint 2: Adjust and try again
  

Mini summary: Small businesses use sprints to try and improve products.

Lesson 7: Agile for Community Projects

Definition: Agile for community projects uses sprints and reviews for group goals.

Why it is important: Community projects involve many people and change often.

Simple explanation: Like planning a community clean-up in short sprints.

Real-life example: Churches and clubs plan events in sprints.

School example: Sports teams prepare in weekly sprints.

Home example: Neighbourhood meetings use backlogs.

Nigerian example: Nigerian youth groups use sprints for events.

Illustration:

  Community Sprint:

  Week 1: Plan
  Week 2: Invite people
  Week 3: Do the project
  Week 4: Review and celebrate 🎉
  

Mini summary: Community projects run better with sprints and shared boards.

Lesson 8: Common Agile Mistakes in Real Life

Definition: Mistakes happen. Knowing them helps you avoid them.

Why it is important: Agile can fail if used wrongly.

Simple explanation: Like using too many rules for a small project.

Real-life example: Teams doing ceremonies without improving.

School example: Groups that talk but do not work.

Home example: Families that plan but forget to act.

Nigerian example: Businesses that use Agile words but work the old way.

Table of common mistakes:

Mini summary: Common mistakes: no goal, too many meetings, no reviews. Fix them early.

Lesson 9: Agile Metrics – Simple Measurements

Definition: Agile metrics are numbers that show how well your team is doing.

Why it is important: What you measure, you can improve.

Simple explanation: Like a score in a game – it shows how well you are playing.

Real-life example: Banks track velocity and cycle time.

School example: Groups track how many tasks they finish weekly.

Home example: Families track chores completed.

Nigerian example: Traders track daily sales and deliveries.

Illustration:

  Key Agile Metrics:

  - Velocity: work done per sprint
  - Cycle Time: time from start to finish
  - Throughput: items completed per week
  - Flow Efficiency: smoothness of work
  

Step-by-step:

1. Choose a metric (like velocity).
2. Record it every sprint.
3. Compare with past sprints.
4. Look for improvements or drops.
5. Make changes to improve.

Mini summary: Agile metrics measure how well the team is doing. Track them every sprint.

Lesson 10: Cycle Time and Lead Time

Definition: Cycle time is how long a task takes from when you start it to when you finish. Lead time is from when it was requested to when it is delivered.

Why it is important: Shorter times mean happier users.

Simple explanation: Like ordering food at a restaurant. Lead time is from order to eating. Cycle time is from cooking start to plate.

Real-life example: Banks track how long transactions take.

School example: Students track how long each subject takes.

Home example: Families track how long cooking takes.

Nigerian example: Traders track order-to-delivery time.

Illustration:

  Lead Time:  Order → Delivered
  Cycle Time: Started → Finished

  Shorter = Better 🎉
  

Mini summary: Cycle time and lead time show how fast the team delivers. Shorter is better.

Lesson 11: Review and Retrospective in Real Life

Definition: Review is showing work. Retrospective is improving the team.

Why it is important: Both keep teams focused and learning.

Simple explanation: Like a class presentation and a class discussion after.

Real-life example: Banks hold reviews and retros every sprint.

School example: Groups show work, then discuss improvement.

Home example: Families show chores, then talk about what to change.

Nigerian example: Market traders show new products, then discuss.

Illustration:

  Review: What did we show?
  Retro: What did we learn?
  

Step-by-step:

1. Show the finished work to users.
2. Listen to feedback.
3. Hold a separate retrospective.
4. Discuss: went well, went wrong, change.
5. Pick one change to try next cycle.

Mini summary: Review shows work to users. Retrospective improves the team.

Lesson 12: Agile at Home – A Real Plan

Let’s build a real Agile plan for a Nigerian family.

Goal: Prepare for a family event in 4 weeks.

Backlog: Invite guests, plan menu, buy food, cook, decorate, arrange seats, welcome guests.

Sprints:

• Week 1: Invites and menu.
• Week 2: Buy food and prepare.
• Week 3: Cook and decorate.
• Week 4: Event day and review.

Kanban Board: To Do | Doing | Done

Review: After the event, ask guests what they liked.

Retrospective: Family discusses what to improve next time.

Illustration:

  Week 1 → Week 2 → Week 3 → Week 4
  (Invites) (Shopping)(Cooking) (Event)
  

Mini summary: Agile helps families plan big events in small sprints with reviews.

Lesson 13: Agile in Nigerian Businesses

Definition: Nigerian businesses use Agile to grow faster and serve customers better.

Why it is important: Agile helps them change quickly with the market.

Simple explanation: Like a trader who tries small batches before buying in bulk.

Real-life example: Banks use Scrum for new features.

School example: Business clubs use sprints for events.

Home example: Home-based businesses use Kanban.

Nigerian example: Lagos fintechs use Scrum; Abuja restaurants use Kanban.

Illustration:

  Nigerian Businesses Using Agile:

  Fintech  → Scrum for features
  Retail   → Kanban for orders
  Farms    → Sprints for planting
  Schools  → Sprints for events
  

Mini summary: Nigerian businesses use Agile to stay fast, flexible, and customer-focused.

Lesson 14: Preparing for the Certification Project

Your certification project brings everything together.

Project idea: Plan and run a real Agile project in school, home, or a small business.

Steps:

1. Choose a real project.
2. Write a backlog.
3. Choose a framework (Scrum or Kanban).
4. Run it for 2–4 weeks.
5. Hold standups, reviews, and retrospectives.
6. Track metrics (velocity, cycle time).
7. Write a report.
8. Present to your class.

Illustration:

  Project Flow:

  Choose project
       |
       V
  Backlog
       |
       V
  Framework (Scrum/Kanban)
       |
       V
  Run sprints + reviews
       |
       V
  Metrics
       |
       V
  Report + Present 🎉
  

Mini summary: The certification project applies everything. Plan carefully and present well.

Lesson 15: Reviewing Everything You Learned

You have learned a lot. Let’s review.

Module One: Foundations – Agile values, principles, Waterfall vs Agile.

Module Two: Teams and ceremonies – roles, standups, reviews, retrospectives.

Module Three: Scrum and Kanban – backlogs, user stories, WIP limits, velocity.

Module Four: Real life – school, home, business, metrics, certification.

Illustration:

  Your Skills:

  +----------------+
  | Foundations    |
  +----------------+
  +----------------+
  | Teams          |
  +----------------+
  +----------------+
  | Scrum/Kanban   |
  +----------------+
  +----------------+
  | Real Life      |
  +----------------+
  +----------------+
  | Certification  |
  +----------------+
  

Mini summary: You have mastered foundations, teams, frameworks, and real-life Agile.

Lesson 16: Your Certification and Beyond

Your certification is proof that you are an Agile Expert.

Next steps:

• Complete your certification project.
• Use Agile in all your projects.
• Teach others in your school and home.
• Help small businesses use Agile.
• Keep learning new Agile tools.
• Stay humble and keep improving.

Illustration:

  Certification
       |
       V
  Portfolio
       |
       V
  Share with others
       |
       V
  Help others learn
       |
       V
  Apply skills
       |
       V
  Agile Expert 🎉
  

Mini summary: Your certification opens doors. Keep growing, sharing, and leading.

Key Vocabulary

Important Concepts

• Agile works everywhere: School, home, business, community.
• School sprints help projects: Weekly cycles with teacher feedback.
• Study plans benefit from sprints: Short, focused sessions.
• Families use boards: Simple Kanban for chores.
• Small businesses use sprints: Test small, then scale.
• Metrics show progress: Velocity, cycle time, throughput.
• Reviews give feedback: Users tell you what they want.
• Retrospectives improve teams: Three questions each cycle.
• Common mistakes can be avoided: Clear goals, short meetings.
• Certification proves your skills: Complete a real project.

Step-by-step Explanations

How to run an Agile school project step by step

1. Write a backlog with your group.
2. Set weekly sprint goals.
3. Hold quick daily standups.
4. Show work to your teacher weekly.
5. Hold a retrospective each week.
6. Improve before the next sprint.

How to set up a family Kanban board step by step

1. Draw three columns: To Do, Doing, Done.
2. Write each chore on a card.
3. Place cards in To Do.
4. Move cards as work is done.
5. Hold a weekly family review.
6. Improve as a family.

How to run a personal sprint step by step

1. Choose a goal for the week.
2. Break it into 3–5 tasks.
3. Work daily.
4. Check progress each day.
5. Hold a personal review Sunday.
6. Improve for next week.

How to track metrics step by step

1. Choose one metric (like velocity).
2. Record it each sprint.
3. Compare with past numbers.
4. Look for improvements or drops.
5. Make changes to improve.

How to prepare the certification project step by step

1. Choose a real project.
2. Write a backlog.
3. Choose a framework.
4. Run it for 2–4 weeks.
5. Hold reviews and retrospectives.
6. Track metrics.
7. Write a report.
8. Present to your class.

Real-life Examples

• Banks: Use Agile for features, teams, and metrics.
• Schools: Use sprints for projects and study plans.
• Homes: Use boards for chores and events.
• Startups: Use sprints for product testing.
• Communities: Use sprints for group events.

Nigerian Examples

• Lagos fintechs: Scrum for weekly releases.
• Abuja restaurants: Kanban for kitchen orders.
• Port Harcourt families: Family boards for chores.
• Onitsha traders: Sprints for market seasons.
• Kano schools: Sprints for exam prep.

Fun Examples Children Can Relate To

• LEGO build: Sprints for each section.
• Reading: Weekly book sprints.
• Sports: Sprints for skills.
• Chores: Family Kanban board.
• Birthday party: Four-week sprint plan.

Everyday Examples

• Shopping: Kanban list for items.
• Budget: Sprint for monthly savings.
• Homework: Daily standups with parents.
• Cleaning: Weekend sprints for deep cleaning.
• Learning: Two-week learning sprints.

Parent Tips

• Set up a family Kanban board.
• Try two-week sprints for home projects.
• Hold short family reviews and retrospectives.
• Teach your child to track simple metrics.
• Read stories of Agile at home and school.
• Celebrate small wins each sprint.
• Encourage clear goals over busy work.
• Keep it simple and fun.
• Let them teach you.
• Support their learning journey.

Interesting Facts

• Agile is now used in hospitals, schools, and farms.
• Some Nigerian schools teach Agile to students.
• Kanban boards can be drawn on paper or cardboard.
• Velocity is often measured in "story points".
• Cycle time helps teams find and fix delays.
• Reviews and retrospectives improve teams 10x faster.
• Agile is used in the Nigerian movie industry (Nollywood).
• Agile helps families plan big events smoothly.

Did You Know?

• Did you know Agile helps save money in home projects?
• Did you know sprint goals can be as simple as "clean the kitchen"?
• Did you know Kanban boards work in classrooms?
• Did you know some families use retrospectives every Sunday?
• Did you know Agile helps students prepare for exams?
• Did you know market traders can use backlogs?
• Did you know banks use Agile metrics every day?
• Did you know Nigerian startups use Agile to compete globally?

Remember This

• Agile works outside software.
• Schools use sprints and reviews.
• Families use boards and retrospectives.
• Businesses use sprints to test ideas.
• Metrics measure progress.
• Cycle time and lead time show speed.
• Reviews show work; retrospectives improve teams.
• Common mistakes can be avoided.
• Certification proves your skills.
• Keep learning and improving.

Common Mistakes

• No clear goal.
• Too many ceremonies.
• No review or retrospective.
• No estimation.
• Ignoring feedback.
• Too big a team.
• Not tracking metrics.
• Not celebrating wins.

Best Practices

• Start with a small project.
• Set clear sprint goals.
• Keep meetings short.
• Hold reviews and retrospectives every cycle.
• Estimate tasks roughly.
• Track one metric per sprint.
• Ask for feedback often.
• Improve every cycle.
• Celebrate small wins.
• Keep it simple.

Illustrations and Diagrams

Agile in Real Life

  School   Home    Business   Community
  Sprints  Boards  Sprints    Sprints
  

Review and Retrospective

  Review: Show work → Get feedback
  Retro:  Ask 3 questions → Pick 1 change
  

Cycle Time and Lead Time

  Lead Time:  Order → Delivered
  Cycle Time: Started → Finished
  

Certification Flow

  Choose project
       |
       V
  Backlog → Sprint → Review → Retrospect
       |
       V
  Report → Present 🎉
  

Your Learning Journey

  Module 1: Foundations
       |
       V
  Module 2: Teams & Ceremonies
       |
       V
  Module 3: Scrum & Kanban
       |
       V
  Module 4: Real Life & Certification
       |
       V
  Agile Expert 🎉
  

Comparison Tables

Agile for School vs Home

Cycle Time vs Lead Time

Velocity vs Throughput

Family Sprint vs Business Sprint

Lesson Summaries

Lesson 1: Agile works outside software too.

Lesson 2: Agile helps school projects with sprints and reviews.

Lesson 3: Study plans work better in short sprints.

Lesson 4: Personal projects get easier with sprints.

Lesson 5: Families use boards and reviews for chores.

Lesson 6: Small businesses use sprints to test ideas.

Lesson 7: Community projects run well with sprints.

Lesson 8: Common mistakes: no goal, too many meetings.

Lesson 9: Metrics show progress. Track them each sprint.

Lesson 10: Cycle time and lead time show speed.

Lesson 11: Reviews show work; retrospectives improve teams.

Lesson 12: Agile helps plan family events in sprints.

Lesson 13: Nigerian businesses use Agile daily.

Lesson 14: The certification project applies everything.

Lesson 15: Review of foundations, teams, frameworks, real life.

Lesson 16: Certification opens doors. Keep growing.

End-of-Module Summary

Congratulations! You have finished Module Four and the entire Agile Fundamentals course. You learned how Agile works outside software. You learned how to use Agile at school, at home, and in small businesses and community projects. You learned about common mistakes and best practices. You learned about Agile metrics like velocity, cycle time, and lead time. You learned to hold reviews and retrospectives. You prepared and completed your certification project. Most importantly, you are now a Certified Agile Expert. Keep using Agile, keep sharing it, and keep learning!

Frequently Asked Questions

1. Can Agile be used outside software? Yes, anywhere with steps and feedback.
2. How do I use Agile for school? Use sprints, reviews, and retrospectives.
3. How do families use Agile? Simple boards and weekly reviews.
4. What metrics should I track? Velocity, cycle time, throughput.
5. What is cycle time? Time from starting to finishing a task.
6. What is lead time? Time from request to delivery.
7. What is a review? Showing work to users.
8. What is a retrospective? A meeting to improve the team.
9. What is the certification project? A real Agile project you plan and run.
10. What are the next steps? Keep using and teaching Agile.

Matching Exercises

Match the term to its meaning.

Answers: 1-C, 2-A, 3-B, 4-E, 5-D

Scenario-based Exercises

1. Scenario: Your family is planning a big event. What do you do?
   Answer: Create a backlog and run weekly sprints.
2. Scenario: Your school group keeps missing deadlines. What do you do?
   Answer: Add weekly sprints and reviews.
3. Scenario: Your team is slow. What do you measure?
   Answer: Cycle time and lead time.
4. Scenario: You want to improve each week. What do you do?
   Answer: Hold a retrospective.
5. Scenario: You want to try new products in business. What do you do?
   Answer: Run small sprints and check with customers.

Group Activity

Title: “Run a Real Agile Project Together”

Instructions: In groups of 3–4, choose a real small project (like planning a class event or a study sprint). Write a backlog. Choose Scrum or Kanban. Run the project for 1–2 weeks. Hold standups, a review, and a retrospective. Track one metric. Present results to the class.

Goal: Experience Agile in a real project.

Individual Activity

Task: Choose a personal goal for the next two weeks. Then:

• Write a backlog of tasks.
• Set a sprint goal each week.
• Hold daily personal standups.
• Hold a review with a friend or parent.
• Do a personal retrospective.
• Track one metric (like tasks completed).

Hint: Keep it small and realistic.

Mini Project

Project: “My Real-Life Agile Plan”

Create a complete Agile plan for a school, home, or community project. Include:

• Project name and goal.
• Backlog with at least 8 items.
• Framework chosen (Scrum or Kanban).
• Sprint plan (2–4 weeks).
• Two user stories.
• Review and retrospective dates.
• Metric to track.
• How you will celebrate success.

Example:

  Project: Family market day
  Backlog: buy rice, buy beans, cook, pack, stall setup, sell, cleanup.
  Framework: Kanban
  Sprints: Weekly Thursday planning.
  User Stories: "As a customer, I want quick service."
  Review: After market.
  Retro: Sunday evening.
  Metric: Items sold.
  Celebrate: Family outing 🎉
  

Practical Assignment

Assignment: Complete your certification project. Choose a real project in school, home, or a small business. Then:

1. Write a project plan with a backlog.
2. Choose Scrum or Kanban.
3. Run it for 2–4 weeks.
4. Hold standups, reviews, and retrospectives.
5. Track one metric each sprint.
6. Write a report with results and lessons learned.
7. Present to your class.

Submit: Your plan, board/backlog, metric data, report, and presentation slides.

Key Takeaways

• Agile works outside software.
• Schools use sprints and reviews.
• Families use boards and retrospectives.
• Businesses use sprints to test ideas.
• Metrics measure progress.
• Cycle time and lead time show speed.
• Reviews show work; retrospectives improve teams.
• Common mistakes can be avoided.
• Certification proves your skills.
• Keep learning and improving.

Classroom Discussion Questions

1. How can Agile help you at school?
2. How can Agile help your family?
3. Why do metrics matter in Agile?
4. What is the difference between cycle time and lead time?
5. What is the point of a retrospective?
6. How can Agile help small Nigerian businesses?
7. What mistakes should we avoid in real-life Agile?
8. What project will you use for your certification?
9. What did Emeka’s family learn from using Agile at their market stall?
10. What is the most important thing you learned in this course?

Next Steps After Certification

Congratulations! You have completed the entire Agile Fundamentals course. Here are some next steps you can take:

• Practice: Use Agile in every group project.
• Share: Teach family, friends, or classmates about Agile.
• Explore: Learn Scrum and Kanban tools (like Trello, Jira, or Notion).
• Lead: Become the Agile helper in your class or family.
• Apply: Use Agile in small business projects or school clubs.
• Keep learning: Agile keeps growing – there is always more to learn.

Remember, this is just the beginning. You are now a Certified Agile Expert. Keep using Agile, keep teaching it, and keep improving!

End of Module Four – Agile Fundamentals

🎉 Congratulations! You have completed the entire Agile Fundamentals course! 🎉