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

“Agile Methodology for Beginners” – A friendly guide to working smarter together

Module Introduction

Welcome, young explorer! Have you ever started 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:

Mistake	What Happens	How to Fix
Only using ceremonies	No real improvement	Focus on the mindset
No customer feedback	Wrong product	Show work often
Too many rules	Slows the team	Keep it simple
Ignoring feedback	Repeat mistakes	Improve each cycle
Fear of change	Stuck with old ideas	Welcome change
Big team, no trust	Poor results	Small, trusted team

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

Word	Simple Definition
Agile	A way of working in small steps with feedback.
Waterfall	The old way of doing everything in one long order.
Manifesto	A short document of important ideas.
Values	What we believe is most important.
Principles	Rules that guide how we work.
Cycle	A small round of work and feedback.
Mindset	A way of thinking.
Method	A way of doing something.
Feedback	Comments that help you improve.
Self-organising team	A team that plans its own work.
Motivated	Feeling excited and ready to work.
Continuous	Happening again and again, without stopping.
Simplicity	Doing only what is needed.
Reflection	Thinking about how to improve.
Result	The finished work.

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

Feature	Waterfall	Agile
Approach	One long order	Many small cycles
Change	Hard	Welcome
Feedback	At the end	Often
Risk	High	Low
Best for	Fixed tasks	Changing tasks

Mindset vs Methods

Feature	Mindset	Methods
Type	Way of thinking	Way of doing
Examples	Trust, feedback	Scrum, Kanban
Importance	Very high	Useful

4 Agile Values

#	Value More	Value Less
1	People and interactions	Processes and tools
2	Working results	Documents and plans
3	Teamwork with customers	Strict contracts
4	Responding to change	Fixed plan

Agile vs No Agile

Feature	Without Agile	With Agile
Feedback	Late	Often
Change	Hard	Easy
Teamwork	Less	More
Result quality	Varies	Higher

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 Methodology for Beginners 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.

Term	Meaning
1. Agile	A. Old way of working in one long order
2. Waterfall	B. A way of thinking
3. Manifesto	C. Working in small steps with feedback
4. Mindset	D. A short document of big ideas
5. Method	E. A way of doing, like Scrum

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 Methodology for Beginners

Module Two: Agile Teams, Roles and Ceremonies – How Agile Teams Work Together

“Agile Methodology for Beginners” – A friendly guide to working smarter together

Module Introduction

Welcome back, young Agile explorer! In Module One, you learned what Agile is, where it came from, and what it values. You learned the 4 values and the 12 principles. You learned that Agile means working in small steps, checking often, and improving as you go.

Now it is time to meet the people behind Agile. In Module Two, we will learn about Agile teams, roles, and ceremonies. A team is a group of people working together. A role is the job each person does. A ceremony is a special meeting that Agile teams hold regularly.

Think of an Agile team as a football team. Everyone has a position, and they meet often to talk, plan, and improve. Without a good team, great ideas never become reality. In this module, we will learn how Agile teams are built, how they talk, and how they improve every week.

By the end of this module, you will know how to describe an Agile team, run simple Agile meetings, and help any group work better together.

Let’s begin!

Learning Objectives

After finishing this module, you will be able to:

• Explain what an Agile team is.
• Describe the meaning of a cross-functional team.
• Name the common roles in an Agile team.
• Explain what a Product Owner, Scrum Master, and Development Team do.
• Describe what a daily standup is and how to run one.
• Explain what sprint planning and sprint review are.
• Describe a retrospective and why it matters.
• Understand what a working agreement is.
• Give Nigerian examples of Agile team practices.
• Complete a mini project and practical assignment.

Warm-up Story: Ada’s Debate Team

Ada is 14 years old and lives in Enugu. Her school entered a national debate competition. The teacher chose five students: Ada, Chidi, Ngozi, Tunde, and Emeka. They had three weeks to prepare.

At first, the team was confused. Nobody knew who was doing what. Chidi wanted to write all the speeches. Ngozi wanted to do all the research. Tunde and Emeka argued about who would speak first. Ada felt lost.

Then Ada remembered what she learned in Module One. She said, "Let’s work like an Agile team. Let’s choose clear roles, talk every day, and improve as we go."

The team agreed. They chose roles:

• Ada became the "Product Owner" – she decided what mattered most in the debate topic.
• Chidi became the "Scrum Master" – he helped the team talk and stay on track.
• Ngozi, Tunde, and Emeka became the "Team" – they did the research, wrote arguments, and practised speaking.

Every morning, the team held a "daily standup." They stood in a circle and each person answered three questions:

• What did I do yesterday?
• What will I do today?
• Is anything blocking me?

The standup took only 10 minutes, but it helped the team stay on track.

At the end of each week, they did a "sprint review." They practised their debate in front of their teacher. The teacher gave feedback. Then they did a "retrospective" – they asked: What went well? What could be better? What will we change?

After three weeks, the team was amazing. They won second place in the competition. But more importantly, they learned how to work as a real Agile team.

Moral of the story: Agile teams have clear roles, meet often, and improve together. Standups, reviews, and retrospectives help teams win.

Main Lessons

Lesson 1: What is an Agile Team?

Definition: An Agile team is a small group of people who work together in short cycles to deliver results.

Why it is important: Agile teams are the heart of Agile work.

Simple explanation: Imagine a small group of friends working on a project and checking with each other every day. That is an Agile team.

Real-life example: A software team building an app together.

School example: A debate team preparing for a competition.

Home example: A family planning a birthday party.

Nigerian example: A group of traders planning a market day together.

Illustration:

  Agile Team:

  +-------+  +-------+  +-------+
  | Person|  | Person|  | Person|
  +-------+  +-------+  +-------+
       |          |          |
       +----------+----------+
                  |
            Working Together 🎉
  

Mini summary: An Agile team is a small group that works together in short cycles.

Lesson 2: Small Teams are Better

Definition: Agile teams are usually small – often 5 to 9 people.

Why it is important: Small teams talk more easily and move faster.

Simple explanation: Like a small group of friends planning a trip. It is easier than planning with 50 people.

Real-life example: Banks keep teams small so they can decide quickly.

School example: Group projects work best with 4–5 students.

Home example: A family of four can plan faster than a family of twenty.

Nigerian example: A small trader team can adjust prices faster than a big market association.

Illustration:

  Small Team:            Big Team:
  Fast talking           Slow talking
  Easy decisions         Many arguments
  Quick changes          Hard to change
  

Mini summary: Agile teams are small. Small teams talk and decide faster.

Lesson 3: What is a Cross-Functional Team?

Definition: A cross-functional team has people with different skills who can cover all parts of the work.

Why it is important: The team does not need to wait for outside help.

Simple explanation: Like a football team with a goalkeeper, defenders, midfielders, and strikers. Everyone has a role.

Real-life example: A bank team with a developer, a designer, and a tester.

School example: A group with a writer, a researcher, and a presenter.

Home example: A family with a cook, a cleaner, and a shopper.

Nigerian example: A team of traders with a cook, a seller, and a driver.

Illustration:

  Cross-Functional Team:

  Writer + Researcher + Presenter = Complete Team 🎉
  

Mini summary: Cross-functional teams have different skills. They can handle all parts of the work.

Lesson 4: The Common Agile Roles

Definition: Agile teams usually have three main roles: Product Owner, Scrum Master, and Team.

Why it is important: Clear roles prevent confusion.

Simple explanation: Like different jobs in a school play – director, stage manager, and actors.

Real-life example: Banks use these roles in every Agile project.

School example: A group project with a leader, a helper, and workers.

Home example: A family with a planner, an organiser, and helpers.

Nigerian example: A market group with a lead trader, an organiser, and sellers.

Illustration:

  Common Agile Roles:

  +-----------------+  +-----------------+  +-----------------+
  | Product Owner   |  | Scrum Master    |  | Team            |
  +-----------------+  +-----------------+  +-----------------+
  What to build?       Helps and removes     Builds the work
                       blockers
  

Mini summary: Agile teams have three main roles: Product Owner, Scrum Master, and Team.

Lesson 5: The Product Owner

Definition: The Product Owner decides what the team should build and in what order.

Why it is important: Without this role, the team might build the wrong thing.

Simple explanation: Like the captain of a team who chooses the game plan.

Real-life example: Banks have Product Owners to prioritise features.

School example: A project leader who decides what to do first.

Home example: A parent who decides what chores are most important.

Nigerian example: A shop owner who decides which products to stock first.

Illustration:

  Product Owner:

  Decides:
  - What to build
  - What is most important
  - What comes first
  

Mini summary: The Product Owner decides what the team builds and in what order.

Lesson 6: The Scrum Master

Definition: The Scrum Master helps the team work smoothly and removes obstacles.

Why it is important: They keep the team moving forward.

Simple explanation: Like a coach who helps players do their best.

Real-life example: Banks use Scrum Masters to keep teams on track.

School example: A team helper who makes sure everyone can work.

Home example: A sibling who helps solve family problems.

Nigerian example: A group organiser who helps traders solve disputes.

Illustration:

  Scrum Master:

  - Helps the team
  - Removes blockers
  - Keeps meetings on track
  - Protects the team
  

Mini summary: The Scrum Master helps the team and removes blockers.

Lesson 7: The Development Team

Definition: The Development Team does the work – building, testing, and delivering.

Why it is important: Without them, nothing gets made.

Simple explanation: Like the players in a football match.

Real-life example: Banks have developers, designers, and testers in the team.

School example: The students who write, research, and present.

Home example: Family members who cook, clean, and shop.

Nigerian example: Traders who sell, pack, and deliver goods.

Illustration:

  Development Team:

  - Build the work
  - Test the work
  - Deliver the work
  

Mini summary: The Development Team does the real work.

Lesson 8: What is a Ceremony?

Definition: A ceremony is a special meeting Agile teams hold regularly.

Why it is important: Ceremonies keep the team aligned and improving.

Simple explanation: Like a class assembly. It keeps everyone informed.

Real-life example: Banks hold weekly ceremonies for every team.

School example: Teachers hold daily class meetings.

Home example: Families have dinner together to talk.

Nigerian example: Traders meet at the market each morning.

Illustration:

  Common Agile Ceremonies:

  - Daily Standup
  - Sprint Planning
  - Sprint Review
  - Retrospective
  

Mini summary: Ceremonies are special meetings. They keep the team aligned.

Lesson 9: The Daily Standup

Definition: The daily standup is a short meeting where everyone shares progress and blockers.

Why it is important: It keeps the team connected every day.

Simple explanation: Like a quick group chat each morning.

Real-life example: Banks do standups in 15 minutes.

School example: Groups check in for 10 minutes.

Home example: Families plan the day at breakfast.

Nigerian example: Traders greet each other before opening stalls.

Illustration:

  Daily Standup:

  Three Questions:

  1. What did I do yesterday?
  2. What will I do today?
  3. What is blocking me?
  

Step-by-step:

1. Stand in a circle.
2. Each person answers the three questions.
3. Keep it short (no long stories).
4. Note any blockers.
5. Fix blockers after the meeting.

Mini summary: A daily standup is short. It keeps the team up to date.

Lesson 10: Sprint Planning

Definition: Sprint Planning is a meeting where the team chooses what to do in the next short cycle (a sprint).

Why it is important: It gives the team clear goals.

Simple explanation: Like planning your week before it starts.

Real-life example: Banks plan sprints every two weeks.

School example: Groups plan what to do next week.

Home example: Families plan their weekend.

Nigerian example: Traders plan what to buy for the next market day.

Illustration:

  Sprint Planning:

  Sprint Goal + List of Tasks = Ready to Work 🎉
  

Step-by-step:

1. Review the big list of work (backlog).
2. Choose what to do this sprint.
3. Split into tasks.
4. Estimate time.
5. Agree on the sprint goal.
6. Start working.

Mini summary: Sprint Planning chooses what to do next. It gives the team a clear goal.

Lesson 11: Sprint Review

Definition: Sprint Review is a meeting where the team shows the finished work to users or customers.

Why it is important: Feedback from users makes the work better.

Simple explanation: Like a school show-and-tell after finishing a project.

Real-life example: Banks show new app features to customers.

School example: Students show their project to the teacher.

Home example: Family shows a new meal to relatives.

Nigerian example: A trader shows new products to customers.

Illustration:

  Sprint Review:

  Team shows work → Users give feedback → Team improves
  

Step-by-step:

1. Prepare the finished work.
2. Invite users or customers.
3. Show what was built.
4. Listen to feedback.
5. Write down ideas for next sprint.

Mini summary: Sprint Review shows finished work to users. Feedback makes it better.

Lesson 12: The Retrospective

Definition: A retrospective is a meeting where the team talks about what went well and what to improve.

Why it is important: Teams get better by talking honestly.

Simple explanation: Like a family meeting about the past week.

Real-life example: Banks hold retrospectives every sprint.

School example: Groups discuss what worked after a project.

Home example: Families talk about what went well on a trip.

Nigerian example: Traders discuss how to improve after each market day.

Illustration:

  Retrospective:

  - What went well?
  - What went wrong?
  - What will we change?
  

Step-by-step:

1. Set a friendly mood.
2. Ask the three questions.
3. Write down answers.
4. Choose one or two changes.
5. Try them next cycle.

Mini summary: A retrospective helps teams improve. Ask the three questions.

Lesson 13: Working Agreements

Definition: A working agreement is a short list of rules the team makes for itself.

Why it is important: Agreements prevent confusion and arguments.

Simple explanation: Like class rules, but made by the class itself.

Real-life example: Banks have team rules about meetings and communication.

School example: Groups agree on when to meet and who does what.

Home example: Families agree on chores and quiet times.

Nigerian example: Traders agree on prices and shared services.

Illustration:

  Working Agreement Examples:

  - We start meetings on time.
  - We speak one at a time.
  - We ask for help when stuck.
  - We finish what we start.
  - We give kind feedback.
  

Step-by-step:

1. Bring the team together.
2. Ask: What rules will help us work well?
3. Write down 5–7 simple rules.
4. Agree on them.
5. Post them where everyone can see.
6. Review them after each sprint.

Mini summary: Working agreements are team-made rules. They prevent confusion.

Lesson 14: Common Mistakes in Agile Teams

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

Why it is important: Agile teams can fail if they use the wrong habits.

Simple explanation: Like a team that talks but never plays.

Real-life example: Banks that only follow the steps and forget the mindset.

School example: Groups that meet but never get work done.

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:

Mistake	What Happens	How to Fix
Standups too long	Team loses focus	Keep them under 15 minutes
No clear roles	Confusion	Assign roles early
Skipping retrospectives	No improvement	Hold them every cycle
Fear of speaking up	Problems grow	Make it safe to share
Too big a team	Slow decisions	Keep 5–9 people
No working agreement	Arguments	Make rules together

Mini summary: Common mistakes: long standups, no roles, skipping retrospectives. Fix them early.

Lesson 15: Best Practices for Agile Teams

Definition: Best practices are good habits that help Agile teams succeed.

Why it is important: Good habits make the team strong.

Simple explanation: Like brushing your teeth every day – it keeps things healthy.

Real-life example: Banks train their Agile teams on best practices.

School example: Groups follow rules and help each other.

Home example: Families talk openly and share chores.

Nigerian example: Businesses keep teams small and focused.

List of best practices:

• Keep the team small (5–9 people).
• Assign clear roles.
• Hold short standups every day.
• Review work with users every sprint.
• Hold retrospectives every sprint.
• Create a working agreement.
• Trust each other.
• Talk face-to-face often.
• Celebrate small wins.
• Always be improving.

Mini summary: Best practices: small teams, clear roles, short meetings, and trust.

Lesson 16: Putting It All Together – Your Agile Team Toolkit

You now know how Agile teams work.

What you learned:

• What an Agile team is
• Why small teams are better
• What a cross-functional team is
• Common Agile roles
• Product Owner, Scrum Master, Team
• Common ceremonies: standup, planning, review, retrospective
• Working agreements
• Common mistakes and best practices

Next steps: In Module Three, you will learn about Scrum, Kanban, and common Agile frameworks.

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 Agile teams and ceremonies. Time to explore frameworks!

Key Vocabulary

Word	Simple Definition
Agile Team	A small group working in short cycles.
Cross-functional	Having many skills in one team.
Role	The job a person does.
Product Owner	Decides what to build and when.
Scrum Master	Helps the team and removes blockers.
Development Team	Does the work.
Ceremony	A regular Agile meeting.
Standup	A short daily meeting.
Sprint	A short working cycle.
Sprint Planning	A meeting to plan the sprint.
Sprint Review	A meeting to show work to users.
Retrospective	A meeting to improve the team.
Blocker	Something stopping the work.
Working Agreement	Rules made by the team.
Trust	Believing in each other.

Important Concepts

• Agile teams are small: 5–9 people.
• Teams are cross-functional: Different skills together.
• Three main roles: Product Owner, Scrum Master, Team.
• Standups are short: Three questions, under 15 minutes.
• Planning sets the goal: What to do this sprint.
• Reviews show progress: Users give feedback.
• Retrospectives improve: Ask three questions.
• Working agreements prevent fights: Rules made together.
• Trust is key: Speak up safely.
• Keep improving: Small wins add up.

Step-by-step Explanations

How to set up an Agile team step by step

1. Choose 5–9 people.
2. Assign the three main roles.
3. Write a working agreement.
4. Plan the first sprint.
5. Start working in small cycles.

How to run a daily standup step by step

1. Stand in a circle.
2. Each person answers three questions.
3. Keep it short.
4. Note blockers.
5. Fix blockers after the meeting.

How to run sprint planning step by step

1. Review the backlog.
2. Choose items for this sprint.
3. Split into tasks.
4. Estimate time.
5. Agree on the sprint goal.

How to run a sprint review step by step

1. Prepare finished work.
2. Invite users or customers.
3. Show what was done.
4. Listen to feedback.
5. Write new ideas for next sprint.

How to run a retrospective step by step

1. Set a friendly mood.
2. Ask: What went well?
3. Ask: What went wrong?
4. Ask: What will we change?
5. Choose one or two changes to try.

Real-life Examples

• Banks: Use Agile teams for every app feature.
• Schools: Group projects run like Agile teams.
• Homes: Families use standups for chores.
• Startups: Small teams deliver fast results.
• Hospitals: Cross-functional teams improve services.

Nigerian Examples

• Lagos fintechs: Small Agile teams ship updates weekly.
• Abuja restaurants: Teams use standups before lunch rush.
• Port Harcourt traders: Groups divide roles for market days.
• Onitsha tailors: Teams use reviews to check dresses.
• Kano schools: Students run Agile-style group projects.

Fun Examples Children Can Relate To

• Football team: Roles like goalkeeper, defender, striker.
• Class play: Director, helpers, actors.
• Birthday party: Family roles: cook, decorator, greeter.
• Group study: Roles: note-taker, quizzer, summariser.
• LEGO build: Everyone builds a section and checks.

Everyday Examples

• Shopping: Team splits tasks: list maker, buyer, checker.
• Homework: Study group with clear roles.
• Cleaning: Family divides rooms and checks each other.
• Cooking: Cook, helper, taster roles.
• Trips: Planner, driver, packer roles.

Parent Tips

• Show your child how roles help teams.
• Run a quick family standup each morning.
• Encourage retrospectives at home: what went well?
• Help them create working agreements for chores.
• Read stories of Agile teams winning.
• Celebrate small wins as a family.
• Teach them to speak up safely.
• Practice short, focused meetings.
• Encourage trust and honesty.
• Support their learning journey.

Interesting Facts

• Daily standups usually last 15 minutes or less.
• Agile teams are usually 5–9 people.
• Retrospectives are one of the most loved Agile ceremonies.
• Product Owners in banks often manage huge backlogs.
• Scrum Masters are called "servant leaders".
• Cross-functional teams deliver 2–3x faster.
• Many Nigerian fintechs run standups every morning.
• Working agreements can improve team happiness.

Did You Know?

• Did you know standups are held standing up to keep them short?
• Did you know retrospectives are sometimes called "retros"?
• Did you know the Scrum Master does not give orders?
• Did you know the Product Owner often talks to customers?
• Did you know working agreements are posted where everyone can see them?
• Did you know banks run dozens of Agile teams at once?
• Did you know Agile teams celebrate every small win?
• Did you know Nigerian startups use Agile teams too?

Remember This

• Agile teams are small (5–9 people).
• Cross-functional means many skills.
• Three roles: Product Owner, Scrum Master, Team.
• Standups are short and daily.
• Planning sets the sprint goal.
• Reviews show work to users.
• Retrospectives improve the team.
• Working agreements prevent fights.
• Trust is essential.
• Keep improving each cycle.

Common Mistakes

• Standups too long.
• No clear roles.
• Skipping retrospectives.
• Fear of speaking up.
• Too big a team.
• No working agreement.
• Ignoring user feedback.
• Not celebrating wins.

Best Practices

• Keep the team small (5–9 people).
• Assign clear roles.
• Hold short standups every day.
• Review work with users every sprint.
• Hold retrospectives every sprint.
• Create a working agreement.
• Trust each other.
• Talk face-to-face often.
• Celebrate small wins.
• Always be improving.

Illustrations and Diagrams

Three Agile Roles

  +-----------------+  +-----------------+  +-----------------+
  | Product Owner   |  | Scrum Master    |  | Team            |
  +-----------------+  +-----------------+  +-----------------+
  Decides "what"       Removes blockers      Does the work
  

Agile Ceremonies Cycle

  Plan → Work → Review → Retrospect
    ↑                          |
    |__________________________|
  

Daily Standup

  Three Questions:

  1. What did I do yesterday?
  2. What will I do today?
  3. What is blocking me?
  

Working Agreement

  - Start on time
  - Speak one at a time
  - Ask for help
  - Finish what we start
  

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

Product Owner vs Scrum Master

Feature	Product Owner	Scrum Master
Focus	What to build	How the team works
Talks to	Users and business	Team and leaders
Best at	Prioritising	Removing blockers

Standup vs Sprint Review

Feature	Standup	Sprint Review
Frequency	Daily	End of sprint
Length	10–15 min	30–60 min
Who joins	Team	Team + users

Retrospective vs Sprint Review

Feature	Retrospective	Sprint Review
Focus	Team improvement	Product feedback
Who joins	Team only	Team + users
Output	Changes to try	New ideas

Big Team vs Small Team

Feature	Big Team	Small Team
Decisions	Slow	Fast
Talking	Hard	Easy
Change	Hard	Easy

Lesson Summaries

Lesson 1: An Agile team is a small group working in short cycles.

Lesson 2: Small teams talk and decide faster.

Lesson 3: Cross-functional teams have many skills.

Lesson 4: Agile has three main roles.

Lesson 5: The Product Owner decides what to build.

Lesson 6: The Scrum Master helps and removes blockers.

Lesson 7: The Team does the real work.

Lesson 8: Ceremonies are regular Agile meetings.

Lesson 9: Standups are short and daily.

Lesson 10: Sprint planning sets the goal.

Lesson 11: Sprint reviews show work to users.

Lesson 12: Retrospectives improve the team.

Lesson 13: Working agreements prevent confusion.

Lesson 14: Common mistakes: long standups, no roles.

Lesson 15: Best practices: small teams, clear roles, trust.

Lesson 16: You now understand Agile teams and ceremonies.

End-of-Module Summary

Congratulations! You have finished Module Two of the Agile Methodology for Beginners course. You learned what an Agile team is and why small teams work better. You learned what cross-functional teams are and the three main roles: Product Owner, Scrum Master, and Development Team. You learned about common Agile ceremonies: standups, sprint planning, sprint reviews, and retrospectives. You learned what working agreements are and how they help. You learned common mistakes and best practices. Most importantly, you now know how Agile teams work together, talk often, and improve every cycle. In the next module, you will learn about Scrum, Kanban, and other common Agile frameworks. Keep learning, and you will become an Agile expert!

Frequently Asked Questions

1. What is an Agile team? A small group working in short cycles.
2. Why are Agile teams small? Small teams talk and decide faster.
3. What is cross-functional? Having many skills in one team.
4. What are the three Agile roles? Product Owner, Scrum Master, Team.
5. What does the Product Owner do? Decides what to build.
6. What does the Scrum Master do? Helps the team and removes blockers.
7. What is a standup? A short daily meeting.
8. What is a retrospective? A meeting to improve the team.
9. What is a working agreement? Rules made by the team.
10. How do Agile teams improve? By checking and adjusting each cycle.

Matching Exercises

Match the term to its meaning.

Term	Meaning
1. Product Owner	A. Short daily meeting
2. Scrum Master	B. Decides what to build
3. Standup	C. Team-made rules
4. Retrospective	D. Helps and removes blockers
5. Working Agreement	E. Meeting to improve the team

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

Scenario-based Exercises

1. Scenario: A team has no clear roles. What do you do?
   Answer: Assign Product Owner, Scrum Master, and Team roles.
2. Scenario: A standup lasts 45 minutes. What do you do?
   Answer: Cut it to 15 minutes with three questions.
3. Scenario: The team keeps making the same mistakes. What do you do?
   Answer: Hold a retrospective and pick one change.
4. Scenario: Users never see the work until the end. What do you do?
   Answer: Hold sprint reviews with users.
5. Scenario: A family argues about chores. What can help?
   Answer: Create a working agreement.

Group Activity

Title: “Run an Agile Team Together”

Instructions: In groups of 4–5, choose a small task (like planning a class event). Assign roles (Product Owner, Scrum Master, Team). Write a working agreement. Run one standup with the three questions. Plan one sprint. Present to the class how it went.

Goal: Experience Agile team roles and ceremonies.

Individual Activity

Task: Choose a small task at home or school. Then:

• Write what role you would take (Product Owner, Scrum Master, or Team).
• Write 3 questions you would answer in a standup.
• Write 3 working agreements for your team.
• Write 2 things to improve in the next cycle.

Hint: Keep it short and clear.

Mini Project

Project: “My Agile Team Plan”

Create a one-page plan for a small Agile team:

• Team name and purpose.
• List 4–5 team members and their roles.
• 3 working agreements.
• One sprint goal.
• Daily standup time.
• Review and retrospective plan.
• How you will celebrate success.

Example:

  Team: Class Project Squad
  Purpose: Build a class magazine
  Roles: Ada (PO), Chidi (SM), Ngozi, Tunde, Emeka (Team)
  Agreements: Start on time; one speaker at a time; help when stuck.
  Sprint Goal: Finish first draft of all articles.
  Standup: Every day at 4pm.
  Review: Show magazine to teacher Friday.
  Retro: Discuss after review.
  Celebrate: Pizza with team 🎉
  

Practical Assignment

Assignment: Choose a group you belong to (school, family, club). Then:

1. List the current roles.
2. Suggest 1–2 role improvements.
3. Write 3 working agreements.
4. Design a 1-week sprint plan.
5. Run one standup.
6. Write what you learned.

Submit: A one-page report with your plan and experience.

Key Takeaways

• Agile teams are small (5–9 people).
• Cross-functional means many skills.
• Three roles: Product Owner, Scrum Master, Team.
• Standups are short and daily.
• Planning sets the sprint goal.
• Reviews show work to users.
• Retrospectives improve the team.
• Working agreements prevent fights.
• Trust is essential.
• Keep improving each cycle.

Classroom Discussion Questions

1. Why do Agile teams work in small groups?
2. What does it mean to be cross-functional?
3. Which Agile role do you find most interesting, and why?
4. Why is the daily standup short and daily?
5. What is the purpose of a sprint review?
6. Why is the retrospective important for improvement?
7. How can working agreements help a team?
8. What mistakes do teams often make?
9. What best practice do you want to try in your next group project?
10. What did Ada’s debate team learn from using Agile?

Preparation for Module Three

In Module Three, we will explore Scrum, Kanban, and common Agile frameworks. We will cover:

• Scrum basics.
• Kanban basics.
• Backlogs and user stories.
• Estimation and prioritisation.
• Velocity and flow.
• Choosing a framework.

To prepare, complete the practical assignment and bring your Agile team plan. Review the key vocabulary. Think about which framework (Scrum or Kanban) might suit your group. Bring your curiosity!

See you in Module Three!

---

End of Module Two – Agile Methodology for Beginners

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

“Agile Methodology for Beginners” – A friendly 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:

Mistake	What Happens	How to Fix
No clear goal	Confusion	Set a sprint goal
Too many ceremonies	Wasted time	Keep meetings short
No review or retrospective	No improvement	Hold them every sprint
No estimation	Overloaded team	Estimate tasks
Ignoring feedback	Stuck with old ideas	Listen and change
Too big a team	Slow decisions	Keep 5–9 people

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

Word	Simple Definition
Agile Everywhere	Using Agile outside software.
Personal Sprint	A short cycle for personal goals.
Family Board	A Kanban board for household tasks.
Business Sprint	A short cycle for a business goal.
Community Sprint	A short cycle for a community project.
Metrics	Numbers that show how well things are going.
Velocity	Work done per sprint.
Cycle Time	Time from starting to finishing a task.
Lead Time	Time from request to delivery.
Throughput	Items completed per week.
Review	Showing work to users.
Retrospective	Meeting to improve the team.
Feedback	Comments that help you improve.
Improvement	Getting better each cycle.
Certification	Proof of your skills.

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

Feature	School	Home
Framework	Sprints	Kanban
Reviews	Teacher feedback	Family discussion
Goal	Grades and learning	Smooth routines

Cycle Time vs Lead Time

Feature	Cycle Time	Lead Time
Starts	When work begins	When requested
Ends	When finished	When delivered
Focus	Team speed	Customer experience

Velocity vs Throughput

Feature	Velocity	Throughput
Measures	Points per sprint	Items per week
Used in	Scrum	Kanban
Purpose	Planning	Flow

Family Sprint vs Business Sprint

Feature	Family Sprint	Business Sprint
Goal	Event or chore	Product or service
Review with	Family	Customers
Length	1–2 weeks	1–4 weeks

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 Methodology for Beginners 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.

Term	Meaning
1. Cycle Time	A. Time from request to delivery
2. Lead Time	B. Work done per sprint
3. Velocity	C. Time from start to finish
4. Review	D. A meeting to improve the team
5. Retrospective	E. Showing work to users

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 Methodology for Beginners 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 Methodology for Beginners

🎉 Congratulations! You have completed the entire Agile Methodology for Beginners course! 🎉