📘 Module 1: Agile Mindset & Principles

“Thinking differently to build amazing things, together.”

🌟 Module Introduction

Welcome to the first step on your Agile journey! This module is like the key that opens the door to a whole new way of working and thinking. Have you ever tried to build a big Lego castle, but you kept changing the design as you went along? That’s a bit like Agile!

In this module, we will learn the heart of Agile: the mindset and the principles. We will discover why Agile is used all over the world, from Nigeria to Japan, to build software, run businesses, and even organise school projects. We will use simple words, fun stories, and lots of examples so that anyone – even a 10-year-old – can understand.

By the end of this module, you will think like an Agile practitioner. You will know how to welcome change, work as a team, and keep improving little by little. Let’s begin!

🎯 Learning Objectives

• Explain what “Agile” means using your own words.
• Name the 4 values of the Agile Manifesto.
• List at least 5 of the 12 Agile principles.
• Understand why the Agile mindset is like a “growth mindset”.
• Tell the difference between Agile and traditional (waterfall) ways of working.
• Give everyday examples of Agile thinking at home, school, and in Nigeria.

📖 Warm-up Story: The Magic Cooking Pot

Imagine you are in a village in Nigeria. Your grandmother gives you a magic cooking pot that can make any stew you dream of. But here is the twist: you don’t know the exact recipe, and the pot changes its taste every hour!

If you try to write down one fixed recipe and never change it, your stew will taste bad. But if you taste the stew every 10 minutes, add a little salt, then some pepper, then maybe a bit of crayfish – you end up with a delicious meal that everyone loves.

That is exactly how Agile works. Instead of planning everything perfectly at the start, we try, learn, and adjust along the way. Agile is like cooking with a magic pot: you keep tasting and improving until it’s just right.

Now let’s learn the ingredients of this magic mindset!

📚 Main Lessons

Lesson 1: What is Agile?

Definition: Agile is a way of working where you deliver small pieces of value quickly, then learn and adapt.

Why important: The world changes fast. Agile helps us keep up and build what people really need.

Simple explanation: Instead of building a whole house at once, you build one room, show it to the family, then build the next room based on their feedback.

Real-life example: A phone app that gets a new feature every two weeks instead of waiting a whole year.

School example: Writing a book report paragraph by paragraph and asking your teacher for advice after each paragraph.

Home example: Cleaning your room one corner at a time, showing your parents, and then cleaning the next corner.

Nigerian example: A small business in Lagos selling “small chops” – they try a new flavour, see if customers like it, then make more.

ASCII illustration:

    Traditional way (Waterfall):
    Plan ➜ Build ➜ Test ➜ Launch (takes ages!)
    
    Agile way (Iterative):
    Plan ➜ Build small ➜ Show ➜ Learn ➜ Plan again ➜ Build more ➜ Show ➜ Learn ...
    

Lesson 2: The Agile Mindset

Definition: A mindset is the way you think about things. The Agile mindset is open, curious, and not afraid of change.

Why important: Without the right mindset, tools and methods won’t work.

Simple explanation: It is like being a scientist in a lab – you try an experiment, see what happens, and try again.

Real-life example: A chef who tastes the soup and adds spices bit by bit.

School example: When you get a math problem wrong, you don’t give up – you try a different way to solve it.

Home example: You rearrange your furniture until it feels just right.

Nigerian example: A tailor who makes a dress, asks the customer to try it on, then adjusts the seams.

    Mindset spectrum:
    Fixed Mindset  ------------  Agile Mindset
    “I can’t do it.”            “I can learn.”
    “Change is bad.”            “Change is opportunity.”
    

Lesson 3: The 4 Values of the Agile Manifesto

In 2001, a group of smart people wrote the Agile Manifesto. It has 4 values. Let’s learn them with easy examples.

Value	Simple meaning	Example
Individuals and interactions over processes and tools	People matter more than rules or software.	Talk to your teammate instead of sending 20 emails.
Working software over comprehensive documentation	A product that works is better than a huge manual.	A game you can play is better than a 100-page design doc.
Customer collaboration over contract negotiation	Work with the customer, don’t fight over terms.	Ask the customer what they want, don’t just follow a strict contract.
Responding to change over following a plan	It’s okay to change the plan if you learn something new.	If a new flavour of ice-cream is popular, change the menu!

Nigerian example: A market woman in Onitsha – she talks to her customers (interaction), sells fresh yams (working product), listens to what they want (collaboration), and changes her prices or stock based on the day (responding to change).

Lesson 4: The 12 Agile Principles (part 1)

The 12 principles are like the “rules of the road” for Agile. We’ll cover 6 now and 6 later.

• 1. Our highest priority is to satisfy the customer – through early and continuous delivery of valuable stuff.
• 2. Welcome changing requirements – even late in the project. Agile uses change to help the customer.
• 3. Deliver working product frequently – every few weeks, or even every day.
• 4. Business people and developers must work together daily – talk every day.
• 5. Build projects around motivated individuals – give them the environment they need and trust them.
• 6. The most efficient way to communicate is face-to-face – talking is better than writing long emails.

Everyday example: You and your friend are building a treehouse. You talk face-to-face (principle 6), you show a small part of the treehouse every day (principle 3), and when your friend says “I want a slide instead of a ladder” – you change the plan (principle 2).

Lesson 5: The 12 Agile Principles (part 2)

• 7. Working product is the primary measure of progress – not how many papers you wrote, but what actually works.
• 8. Agile processes promote sustainable development – everyone keeps a steady pace, no burnout.
• 9. Continuous attention to technical excellence – do things well, not just fast.
• 10. Simplicity – the art of maximising the amount of work not done – don’t do unnecessary things.
• 11. The best architectures emerge from self-organising teams – teams that decide together create better designs.
• 12. At regular intervals, the team reflects on how to become more effective – then adjusts accordingly.

Nigerian example: A group of students in Ibadan preparing for a quiz – they don’t study everything, they focus on what’s important (simplicity). Every Friday they review what worked and what didn’t (reflect and adjust).

Lesson 6: Agile vs Traditional (Waterfall)

Traditional way (Waterfall) is like building a bridge: you plan everything, then build, then test at the very end. Changes are very expensive.

Agile is like baking a cake: you taste the batter, add sugar, bake a little, then add icing, taste again … you keep adjusting until it’s perfect.

Waterfall	Agile
Big plan upfront	Plan a little, then adapt
Changes are difficult	Changes are welcome
Testing at the end	Testing all the time
One big delivery	Many small deliveries
Customer sees product only at the end	Customer sees product early and often

    Waterfall timeline:
    [ Research ] → [ Design ] → [ Build ] → [ Test ] → [ Launch ]
    (if something is wrong, go back to start – painful!)
    
    Agile timeline:
    [Plan] → [Build] → [Test] → [Show] → [Learn] → [Plan again] → ...
    (each cycle is short, and you improve each time)
    

Lesson 7: The Agile Team – Who does what?

An Agile team is like a football team. Everyone has a role, but they all work together to score goals.

• Product Owner – the person who knows what the customer wants. They decide what is most important to build next. (Like the coach who decides the game strategy.)
• Scrum Master / Agile Coach – the person who helps the team follow Agile rules and removes obstacles. (Like the referee who makes sure the game is fair.)
• Development Team – the people who actually build the product. They are self-organising – they decide how to do the work. (Like the players on the pitch.)

School example: For a class project – the Product Owner is the student who decides the topic, the Scrum Master is the student who keeps everyone organised, and the team does the research and presentation.

Lesson 8: Agile Artifacts – the things we use

Artifacts are just tools or documents that help us stay on track.

• Product Backlog – a list of everything we might need to build, ordered by importance. (Like a grocery list, with the most urgent items at the top.)
• Sprint Backlog – a list of items we will build in the next short period (called a Sprint).
• Increment – the finished piece of work at the end of a Sprint. Something that works and could be shown to a customer.

    Product Backlog (ordered list)
    -----------------------------
    1. Login screen (most important)
    2. Profile picture upload
    3. Friend request button
    4. Chat feature
    ...
    
    Sprint Backlog (for this 2-week Sprint)
    -----------------------------
    - Login screen
    - Profile picture upload (partially)
    

Lesson 9: Agile Events – the ceremonies

Agile teams hold regular meetings (events) to stay in sync.

• Sprint Planning – at the start of a Sprint, the team decides what they will build.
• Daily Stand-up – a quick 15-minute meeting every day. Each person says: what I did yesterday, what I will do today, any blockers.
• Sprint Review – at the end of the Sprint, the team shows what they built to the customer.
• Sprint Retrospective – the team looks back at the Sprint and decides how to improve next time.

    Sprint cycle (usually 1–4 weeks):
    [ Planning ] → [ Daily Stand-ups (every day) ] → [ Build ] → [ Review ] → [ Retrospective ] → then back to Planning
    

Lesson 10: Why Agile works in Nigeria

Nigeria is a country full of energy, creativity, and change. Agile fits perfectly because:

• Markets change fast – like the price of tomatoes.
• People are great at collaborating – like in “ajo” (savings groups).
• We love to find solutions – “we manage” spirit.

Example: A fintech startup in Lagos builds a mobile money app. They release a simple version that allows transfers. They listen to users, then add bill payments, then add savings. They deliver value early and keep improving.

Lesson 11: Everyday Agile thinking

You already use Agile thinking in your daily life without realising it!

• When you plan a birthday party – you start with a few friends, see if it works, then invite more.
• When you learn to play an instrument – you practise one song, get feedback, then move to the next.
• When you write a story – you write a paragraph, read it aloud, then edit.

📌 Key Vocabulary

🧠 Important Concepts

• Inspect and Adapt – look at what you have done, then change your plan based on what you see. Like checking your work and fixing mistakes.
• Empiricism – making decisions based on what you observe, not just on guesses. “Try it and see.”
• Self-Organisation – the team decides how to do their work, not a boss. But they still align with the goal.

🔢 Step-by-step: How to apply Agile mindset

1. Think of a goal – e.g., “I want to improve my grades.”
2. Break it into small pieces – “study one topic per day”.
3. Do a piece – study topic 1.
4. Check – did you understand it? Test yourself.
5. Learn and adjust – if you didn’t understand, try a different method.
6. Repeat – do the next piece.

🌍 Real-life Examples

• Construction: Instead of building a whole skyscraper, builders use Agile to complete floors one at a time and get feedback from the owner.
• Education: Teachers use Agile when they give a short quiz every week instead of one big exam at the end.

🇳🇬 Nigerian Examples

• Okada (motorcycle) delivery: A delivery company tests a new route with 5 bikes, checks if it’s faster, then expands.
• Nollywood: Film producers release a short teaser, see audience reactions, then adjust the movie ending.
• Farming: A farmer plants a small plot with a new seed, observes growth, then plants more if it works.

🧸 Fun Examples for Children

• Lego building: You build a small house, show your friend, then add a garden, then a pool – step by step.
• Drawing a comic: Draw one panel, show it, then draw the next based on what your friends find funny.
• Video game: You play a level, if it’s too hard, you change your strategy before the next level.

🏠 Everyday Examples

• Planning a family dinner: cook one dish, taste it, then cook the next.
• Organising your wardrobe: arrange one shelf, see if it works, then do the next.

👪 Parent Tips

• Encourage your child to try things and make mistakes – that’s how they learn.
• Help them break big tasks into small steps. “Let’s do 10 minutes of homework, then break.”
• Praise effort and learning, not just results.

💡 Interesting Facts

• The Agile Manifesto was written by 17 people in a ski resort in Utah, USA.
• Agile is used not just in software, but in marketing, education, and even space exploration!
• The word “Agile” means “able to move quickly and easily”.

❓ Did You Know?

• Many Nigerian startups use Agile to launch products faster.
• Agile teams often have “retrospectives” where they eat snacks and talk about what they learned.

🔔 Remember This

• Agile is about people, not processes.
• Feedback is a gift – use it to improve.
• Small steps lead to big results.
• Change is not bad – it’s an opportunity.

⚠️ Common Mistakes

• “Agile means no planning.” – Wrong! Agile plans, but in small chunks and with flexibility.
• “We don’t need documentation.” – Agile values working product, but some documentation is still useful.
• “Agile is only for developers.” – No, it works for any team.
• “We skip retrospections because we’re busy.” – Big mistake! Retrospectives are how you get better.

✅ Best Practices

• Have a clear Product Backlog and keep it updated.
• Hold a Daily Stand-up every day, even if it’s short.
• Never skip the Retrospective – it’s your improvement engine.
• Involve the customer early and often.
• Celebrate small wins!

📊 Diagrams

    Agile Feedback Loop
    ┌───────────────────────────────┐
    │  Plan (what to do)            │
    │         ↓                      │
    │  Do (build a small piece)     │
    │         ↓                      │
    │  Check (show to customer)     │
    │         ↓                      │
    │  Act (improve based on feedback)│
    └───────────────────────────────┘
    (repeat many times)
    

📝 End-of-Module Summary

❓ Frequently Asked Questions

• Q1: Is Agile only for tech?
  No! It’s for any project – school, business, even planning a party.
• Q2: Do we need special tools for Agile?
  You can start with a whiteboard and sticky notes.
• Q3: What if the customer changes their mind all the time?
  Agile welcomes that – it’s a chance to build something even better.
• Q4: How long is a Sprint?
  Usually 1 to 4 weeks. The team decides.
• Q5: Can one person be both Product Owner and Scrum Master?
  It’s not recommended – they have different focuses.
• Q6: Do we have to use Scrum?
  No, there are other Agile frameworks like Kanban and XP.
• Q7: What if the team is in different cities?
  Agile works with virtual meetings, video calls, and online boards.
• Q8: Is Agile expensive?
  It can save money because you don’t build things nobody wants.
• Q9: How do we measure progress in Agile?
  By working product – something that actually works and delivers value.
• Q10: Do we need a big upfront design?
  No, we do just enough design to start, then refine as we go.

🔗 Matching Exercise

Match the term on the left with its correct description.

Term	Description
1. Product Owner	A. List of work to be done, ordered by importance
2. Sprint	B. Short meeting every day to sync
3. Backlog	C. Person who represents the customer
4. Stand-up	D. Fixed period (1-4 weeks) to complete work

(Answers: 1-C, 2-D, 3-A, 4-B)

🎭 Scenario-based Exercise

Scenario: You are organising a school sports day. You have 2 months to plan. The principal says they want a fun day, but they are not sure about the activities.

Question: How would you use Agile to plan the sports day? Describe the steps you would take.

👥 Group Activity

In groups of 3–4, act out a Daily Stand-up meeting. One person is the Product Owner, one is the Scrum Master, and the others are the team. Each team member says: what they did yesterday, what they will do today, and any blockers. The Scrum Master helps remove blockers.

✍️ Individual Activity

Write down a personal goal (e.g., “learn to cook jollof rice”). Break it into 5 small steps. For each step, write how you will check if you are doing it well.

🛠️ Mini Project

Create a simple “Product Backlog” for a project of your choice (e.g., a mobile app for school news). List at least 10 items, ordered from most important to least important. Use a table to show priority and description.

📋 Practical Assignment

Over the next week, use the Agile mindset in your daily routine. Pick a task (like doing homework). Each day, plan a small part, do it, review it, and adjust. Write a short report about what you learned.

🔑 Key Takeaways

• Agile is about delivering value in small pieces and adapting.
• The Agile manifesto gives us 4 values and 12 principles.
• Agile teams are self-organising and have clear roles.
• Continuous feedback and improvement are at the core.

💬 Classroom Discussion Questions

• Why do you think “responding to change” is more important than following a plan?
• Can you think of a time when you had to change your plan because something unexpected happened?
• How can Agile help a Nigerian business grow?
• What is the hardest part about working in a team? How can Agile help?

🔜 Preparation for Module 2

In the next module, we will dive deeper into Agile frameworks – especially Scrum and Kanban. You will learn how to run a Sprint, manage a backlog, and visualise your work. Start thinking about a project you would like to manage using Agile – it could be a school event, a hobby, or even planning a trip!

---

You have completed Module 1 – well done!

📘 Module 2: Agile Frameworks – Scrum & Kanban

“Two powerful ways to put Agile into action.”

🌟 Module Introduction

In Module 1, we learned the mindset and principles of Agile. Now it’s time to see how we actually do Agile. Think of Agile like a sport – the mindset is the spirit of the game, but you need rules and positions to play. That’s what frameworks give us.

In this module, we will explore two of the most popular Agile frameworks: Scrum and Kanban. We will learn their roles, events, boards, and how they help teams deliver value. We’ll use simple stories, Nigerian examples, and fun analogies so that even a 10-year-old can understand. Let’s jump in!

🎯 Learning Objectives

• Define what a framework is and why we need it.
• Explain the main parts of Scrum: roles, events, and artifacts.
• Describe how Kanban uses a visual board to manage work.
• Compare Scrum and Kanban and tell when to use each.
• Give examples of how Scrum and Kanban are used in Nigeria.
• Start using a simple Kanban board for your own tasks.

📖 Warm-up Story: The Kitchen of Many Chefs

Imagine a busy kitchen in a big restaurant in Abuja. There are many chefs, and they all want to cook delicious meals for customers. But if everyone just does whatever they want, there will be chaos – some dishes will be burnt, others will be late.

So the head chef introduces two ways to organise the kitchen:

• Scrum way: The chefs work in short “sprints”. Every two weeks, they plan a menu, cook those dishes, and then show them to the customers for feedback. They have a daily 15-minute meeting to coordinate.
• Kanban way: They put a big whiteboard on the wall with columns: “To Do”, “Cooking”, “Tasting”, “Done”. Each dish is a sticky note that moves across the board. They limit how many dishes can be “Cooking” at once so they don’t get overwhelmed.

Both methods help the kitchen run smoothly. In this module, we’ll learn both so you can choose the best one for your project!

📚 Main Lessons

Lesson 1: What is an Agile Framework?

Definition: A framework is a set of rules, roles, and practices that help you follow Agile principles.

Why important: A framework gives you a clear path. Without it, Agile can be too vague.

Simple explanation: Think of a framework like a recipe. The Agile mindset is the idea of cooking tasty food, but the recipe tells you exactly what ingredients to mix and in what order.

Real-life example: A school club that meets every week – they have a president, a secretary, and an agenda. That’s a framework!

Nigerian example: A traditional “ajo” savings group – they have rules for contributions, collection, and sharing. That’s a framework.

    Agile Mindset (the "why")
            |
            V
    Framework (the "how")
      /            \
    Scrum         Kanban
    

Lesson 2: Scrum – The Basics

Definition: Scrum is an Agile framework that uses fixed-length cycles called Sprints (usually 2–4 weeks) to deliver working product.

Why important: Scrum is the most popular Agile framework – many companies use it.

Simple explanation: Imagine you are making a comic book. With Scrum, you plan to draw 5 pages every 2 weeks. At the end of 2 weeks, you show those pages to your fans, get feedback, and plan the next 5 pages.

Real-life example: A team building a mobile app releases a new feature every Sprint.

School example: Every Friday, you present one chapter of your project to the class.

Home example: Every weekend, you clean one room of the house and show your parents.

Nigerian example: A small business in Kano that makes handmade soap – they produce a batch every week, test it on customers, and improve the recipe.

    Scrum cycle:
    Sprint Planning → Daily Stand-ups → Build → Sprint Review → Retrospective → repeat
    

Lesson 3: Scrum Roles – Who does what?

Scrum has three key roles:

• Product Owner (PO): The voice of the customer. They decide what is most important to build. They manage the Product Backlog.
• Scrum Master (SM): The coach. They make sure the team follows Scrum rules. They remove blockers so the team can focus.
• Development Team: The builders. They are self-organising – they decide how to complete the work.

Analogies:

• PO = a restaurant owner who decides the menu.
• SM = the head waiter who makes sure everything runs smoothly.
• Team = the chefs who cook the food.

Lesson 4: Scrum Events (Ceremonies)

Scrum has 4 main events:

• Sprint Planning: At the start of each Sprint, the team selects items from the Product Backlog and plans how to complete them.
• Daily Stand-up (Daily Scrum): A 15-minute meeting every day. Each team member answers: What did I do yesterday? What will I do today? Any blockers?
• Sprint Review: At the end of the Sprint, the team shows what they built to stakeholders and gets feedback.
• Sprint Retrospective: The team looks back at the Sprint and decides what to improve next time.

    Sprint timeline (2 weeks):
    Day 1: Sprint Planning
    Days 2–11: Daily Stand-ups + building
    Day 12: Sprint Review & Retrospective
    

Lesson 5: Scrum Artifacts

Artifacts are the “things” we use in Scrum:

• Product Backlog: A list of all desired features, ordered by priority. It changes as we learn more.
• Sprint Backlog: The items we commit to complete in the current Sprint. They are broken into tasks.
• Increment: The sum of all completed Product Backlog items at the end of a Sprint. It must be “Done” – meaning it works and meets quality standards.

    Product Backlog (ordered)
    -------------------------
    1. User login (high priority)
    2. Profile page
    3. Search bar
    ...
    
    Sprint Backlog (for Sprint 1)
    -----------------------------
    - User login (design + code + test)
    - Profile page (design only)
    

Lesson 6: Kanban – The Visual Way

Definition: Kanban is an Agile framework that uses a visual board to manage work. Work flows through columns like “To Do”, “In Progress”, “Done”.

Why important: Kanban is simple and flexible. It helps teams see bottlenecks and manage capacity.

Simple explanation: Imagine you have a whiteboard with sticky notes. Each note is a task. You move the notes from left to right as you work on them. You limit how many notes can be in each column so you don’t get stuck.

Real-life example: A hospital uses Kanban to track patients: “Waiting”, “With Doctor”, “Tests”, “Discharged”.

School example: A teacher uses a Kanban board to track homework: “Not Started”, “Working”, “Needs Review”, “Finished”.

Nigerian example: A printing press in Enugu uses a Kanban board to track jobs: “Order Received”, “Designing”, “Printing”, “Quality Check”, “Delivered”.

    Kanban board (simple)
    ┌────────────┬────────────┬────────────┐
    │  To Do     │  Doing     │  Done      │
    │            │  (WIP: 3)  │            │
    │ Task 1     │ Task 4     │ Task 7     │
    │ Task 2     │ Task 5     │ Task 8     │
    │ Task 3     │ Task 6     │            │
    └────────────┴────────────┴────────────┘
    

Lesson 7: WIP Limits – Why they matter

Definition: WIP stands for Work In Progress. A WIP limit is the maximum number of tasks you can have in a column at one time.

Why important: WIP limits prevent overload. When you have too many tasks in progress, nothing gets finished quickly.

Simple explanation: If you try to juggle 5 balls, you will drop them all. But if you juggle 3 balls, you can do it well. WIP limits are like that.

Real-life example: A bakery bakes only 2 types of bread at a time so they don’t burn anything.

Home example: You do only one homework subject at a time instead of mixing them.

Lesson 8: Scrum vs Kanban – A Comparison

Feature	Scrum	Kanban
Cadence	Fixed Sprints (e.g., 2 weeks)	Continuous flow (no fixed cycles)
Roles	PO, SM, Team	No fixed roles – everyone collaborates
Planning	At Sprint start	Continuous – reprioritise anytime
Change	Changes can happen between Sprints	Changes can happen at any time
WIP limits	Not mandatory	Mandatory (core rule)
Best for	Projects with clear priorities, teams that need structure	Support teams, maintenance, or unpredictable work

Nigerian example: A software startup building a new app might use Scrum. A customer support team handling daily requests might use Kanban.

Lesson 9: Combining Scrum and Kanban – Scrumban

Some teams mix both frameworks. They use Scrum’s structure (Sprints, roles) but add Kanban’s visual board and WIP limits. This is called Scrumban.

Example: A team uses 2-week Sprints, but they have a Kanban board inside the Sprint to visualise their tasks and limit how many tasks are “In Progress”.

Lesson 10: Kanban in Nigerian Small Business

In Nigeria, many small businesses use Kanban informally. A tailor in Aba has a notebook with columns: “Orders”, “Cutting”, “Sewing”, “Finishing”, “Delivered”. They limit the number of orders they start cutting so they don’t get overwhelmed.

A food vendor in Lagos uses a whiteboard to track orders: “Received”, “Cooking”, “Packing”, “Delivered”. This helps them serve customers faster.

Lesson 11: How to start a Kanban board

• Step 1: Draw columns: “Backlog”, “To Do”, “Doing”, “Done”.
• Step 2: Write tasks on sticky notes and place them in “Backlog”.
• Step 3: Move tasks to “To Do” when they are ready.
• Step 4: Move to “Doing” when you start working (limit WIP).
• Step 5: Move to “Done” when finished.
• Step 6: Review and improve the board regularly.

Lesson 12: Agile frameworks in Nigerian Tech Hubs

In Lagos, Abuja, and Port Harcourt, many tech hubs (like CcHub, Andela, and Co-Creation Hub) use Scrum and Kanban. They train young Nigerians to become Scrum Masters and Product Owners. Agile is helping Nigeria build world-class software and services.

📌 Key Vocabulary

🧠 Important Concepts

• Flow efficiency – how smoothly work moves through the system. Kanban helps improve flow.
• Pull system – in Kanban, you “pull” work into the next column only when you have capacity. You don’t push work to people.
• Commitment – in Scrum, the team commits to completing a set of work each Sprint.

🔢 Step-by-step: Setting up a Scrum Sprint

1. Ensure your Product Backlog is ready – with items ordered by priority.
2. Hold Sprint Planning – decide which items to build in the Sprint.
3. Create Sprint Backlog – break items into tasks.
4. Hold Daily Stand-ups – sync every day.
5. Build the Increment – complete the tasks.
6. Sprint Review – show the increment to stakeholders.
7. Sprint Retrospective – discuss improvements.
8. Repeat – start the next Sprint.

🌍 Real-life Examples

• Google: Many teams use Scrum to build features for Gmail and Maps.
• Spotify: Uses a mix of Scrum and Kanban to deliver music features every week.
• Nigerian banks: Use Scrum to update their mobile apps regularly.

🧸 Fun Examples for Children

• Class project: Use a Kanban board with columns: “Research”, “Writing”, “Drawing”, “Presenting”. Limit “Writing” to 2 groups at a time.
• Video game quest: Plan your quests in a Sprint – “This week, I will complete 5 levels.”

🏠 Everyday Examples

• Using a whiteboard to plan your week – Monday to Sunday, with tasks moving across days.
• Family chores board – “To Do”, “In Progress”, “Done” – with WIP limit of 2 chores per person.

👪 Parent Tips

• Help your child create a simple Kanban board for homework. Use sticky notes and a whiteboard.
• Encourage them to limit the number of subjects they work on at once (WIP limit).
• Celebrate when they move tasks to “Done” – it builds motivation.

💡 Interesting Facts

• Kanban comes from Japanese manufacturing – it means “signboard” or “card”.
• Scrum was inspired by a rugby strategy – the whole team works together to move the ball forward.
• Many Nigerian companies now hire “Scrum Masters” – it’s a growing career.

❓ Did You Know?

• Kanban can be used for personal goal setting – like a fitness board with exercises.
• Some schools in Nigeria use Kanban to track student assignments.

🔔 Remember This

• Scrum = fixed Sprints, roles, and events.
• Kanban = visual board, WIP limits, and continuous flow.
• You can choose the framework that best fits your team and project.
• Both help you deliver value early and often.

⚠️ Common Mistakes

• “We use Scrum, but we skip the Retrospective.” – Big mistake! Retrospectives are key to improvement.
• “Kanban has no roles, so we don’t need a leader.” – You still need someone to facilitate and make decisions.
• “We set a WIP limit of 10 and never change it.” – WIP limits should be adjusted as you learn.
• “The Product Owner is just a secretary.” – No, the PO is the vision-holder and decision-maker.

✅ Best Practices

• Keep Sprints short (1–4 weeks) to get fast feedback.
• Make your Kanban board visible to everyone (physical or digital).
• Review your WIP limits regularly – adjust them if work piles up.
• Involve the whole team in planning and retrospectives.
• Celebrate completed increments – it motivates the team.

📊 Diagrams

    Scrum vs Kanban Flow
    Scrum (Sprint-based):
    [Sprint 1] → [Sprint 2] → [Sprint 3] → ...
    (fixed length, with reviews after each)
    
    Kanban (continuous):
    Backlog → To Do → Doing → Done (flow, no fixed cycles)
    

📝 End-of-Module Summary

❓ Frequently Asked Questions

• Q1: Do I have to use either Scrum or Kanban?
  No, there are other frameworks like XP and Lean. But Scrum and Kanban are the most popular.
• Q2: Can I use Kanban without any roles?
  Yes, but it helps to have a facilitator or manager who oversees the board.
• Q3: How long should my Sprint be?
  2 weeks is common, but you can start with 1 week and adjust.
• Q4: What if I finish all tasks in the Sprint early?
  Great! You can pull in the next most important item from the Product Backlog.
• Q5: What if I don’t finish all Sprint tasks?
  That’s a learning opportunity – in Retrospective, discuss why and adjust.
• Q6: Is Kanban easier than Scrum?
  It’s simpler to start, but both have their challenges.
• Q7: Can I use Scrum without a Product Owner?
  Not really – the PO is essential for prioritisation.
• Q8: What is a “burndown chart”?
  It’s a graph that shows how much work is left in a Sprint. We’ll cover it later.
• Q9: Can a team use both Scrum and Kanban at the same time?
  Yes, that’s Scrumban – many teams do it.
• Q10: Which framework is best for a startup?
  Scrum is great for building new products; Kanban is good for support and operations.

🔗 Matching Exercise

Match the framework term with its description.

Term	Description
1. Sprint	A. Visual board with columns and WIP limits
2. Kanban	B. Fixed period of work (1–4 weeks)
3. Product Owner	C. Coach who removes blockers
4. Scrum Master	D. Represents the customer and prioritises

(Answers: 1-B, 2-A, 3-D, 4-C)

🎭 Scenario-based Exercise

Scenario: You run a small printing shop in Ibadan. You have 5 employees and many orders. Orders often get delayed because people start too many jobs at once.

Question: Which framework would you recommend to improve the workflow? How would you set it up?

👥 Group Activity

In groups of 4, create a Kanban board for a school event (like a cultural day). Draw the board on paper with columns. Add WIP limits. Then simulate moving tasks across the board.

✍️ Individual Activity

Set up a personal Kanban board for your week. Use a piece of paper or a digital tool. Track your homework, chores, and personal tasks. Limit your “Doing” column to 3 items. Review at the end of the week.

🛠️ Mini Project

Plan a 2-week Scrum project for a small app (e.g., a “Daily Motivation” app). Write a Product Backlog with 10 items, create a Sprint Backlog for the first Sprint, and list the roles (PO, SM, Team) with names.

📋 Practical Assignment

For one week, observe a process in your home or school (e.g., doing laundry, preparing meals, or homework). Draw a Kanban board for that process. Identify bottlenecks and suggest improvements.

🔑 Key Takeaways

• Scrum and Kanban are two popular Agile frameworks.
• Scrum uses Sprints, roles, and events to structure work.
• Kanban uses a visual board and WIP limits to manage flow.
• Choose the framework that fits your work type – or combine them!
• Both frameworks help teams deliver value and improve continuously.

💬 Classroom Discussion Questions

• Which framework do you think is easier to start with – Scrum or Kanban? Why?
• Can you think of a situation where Scrum would be better than Kanban?
• How would you explain Kanban to a friend who has never heard of Agile?
• Why is it important to limit work in progress?

🔜 Preparation for Module 3

In Module 3, we will dive into Agile Planning and Estimation. You will learn how to estimate effort, prioritise tasks, and create release plans. We’ll explore story points, planning poker, and velocity. Start thinking about a project you’d like to plan – it could be a school event, a small app, or even a family trip!

---

You have completed Module 2 – fantastic!

📘 Module 3: Agile Planning & Estimation

“Knowing how much work you can do, and planning smartly.”

🌟 Module Introduction

In Modules 1 and 2, we learned the Agile mindset and the two most popular frameworks – Scrum and Kanban. But how do we know how long a project will take? How do we decide which tasks are most important? That’s what planning and estimation are all about.

Imagine you are planning a big trip. You need to know how much money to save, how many days to take, and what to pack. Agile planning is like that – but for projects. We break big goals into smaller pieces, guess how much effort each piece needs, and then adjust as we go.

In this module, we will learn story points, velocity, planning poker, release planning, and prioritisation techniques. We’ll use simple words, fun examples, and Nigerian stories to make everything clear. Let’s dive in!

🎯 Learning Objectives

• Explain why we estimate in Agile and how it differs from traditional planning.
• Define story points and velocity.
• Use relative sizing to estimate effort.
• Play “Planning Poker” to estimate as a team.
• Prioritise a backlog using MoSCoW and other techniques.
• Create a release plan for a project.

📖 Warm-up Story: The School Fair

Your school is organising a big fair. There are 10 stalls, games, and food. The principal asks you: “How long will it take to set everything up?”

You have never done this before. But you have a team of 10 students. Instead of guessing wildly, you break the work into small tasks: setting up a stall takes 1 hour, decorating takes 30 minutes, and practising games takes 2 hours. You count the tasks and add them up. You also know that some tasks are bigger than others – the “food stall” is huge, while the “balloon stand” is small.

You assign points to each task based on size. Then you track how many points your team can complete per day. That is exactly how Agile estimation works – it’s like planning a school fair, but for software or any project!

📚 Main Lessons

Lesson 1: Why estimate in Agile?

Definition: Estimation is a way to guess how much effort a task will need.

Why important: Estimates help us plan, set expectations, and decide what to work on next.

Simple explanation: When you pack for a trip, you guess how many clothes you need. That’s an estimate. It’s not perfect, but it helps.

Real-life example: A chef estimates how many plates of food to cook for a party.

School example: A teacher estimates how long it will take for students to finish a test.

Home example: You estimate how long it will take to clean your room.

Nigerian example: A tailor in Kano estimates how much fabric is needed for a customer’s outfit.

    Estimation helps us:
    - Plan better
    - Set realistic goals
    - Avoid being too busy or too idle
    

Lesson 2: Traditional estimation vs Agile estimation

Traditional way: Estimate in hours or days. But humans are bad at estimating time – we are often wrong.

Agile way: Estimate in relative size. We compare tasks to each other. For example, Task A is twice as big as Task B.

Why relative is better: It’s easier to say “this is bigger than that” than to say “this takes exactly 5 hours”.

Traditional (hours)	Agile (relative)
“This takes 10 hours.”	“This is a 3-point task.”
“That takes 6 hours.”	“That is a 2-point task.”
Often wrong, hard to compare.	Easier to compare, more consistent.

Lesson 3: Story Points – The units of estimation

Definition: A story point is a number that represents the size of a task. It includes effort, complexity, and uncertainty.

Why important: Story points help teams estimate consistently.

Simple explanation: Think of story points like “T-shirt sizes” – XS, S, M, L, XL. We give each task a size instead of a time.

Example scale: 1 = very small, 2 = small, 3 = medium, 5 = large, 8 = very large, 13 = huge (we use numbers like Fibonacci).

Nigerian example: A tailor might estimate fabric needs: small = 2 yards, medium = 4 yards, large = 6 yards. That’s relative.

    Story point scale (Fibonacci-like):
    1, 2, 3, 5, 8, 13, 21
    (each number is roughly the sum of the previous two)
    

Lesson 4: Velocity – How fast your team moves

Definition: Velocity is the number of story points your team completes in one Sprint.

Why important: Velocity helps predict how much work you can do in future Sprints.

Simple explanation: If you complete 15 story points in Sprint 1, your velocity is 15. In Sprint 2, you can plan around 15 points.

Real-life example: A moving company knows they can move 3 houses per week – that’s their “velocity”.

School example: If you read 2 chapters per day, your velocity is 2 chapters/day.

Lesson 5: Planning Poker – Fun estimation game

Definition: Planning Poker is a game where the team estimates tasks together using cards with numbers.

Why important: It involves everyone and leads to better estimates through discussion.

How to play:

• Each person has cards with numbers (1, 2, 3, 5, 8, etc.).
• The Product Owner reads a task.
• Each person secretly picks a card that shows their estimate.
• Everyone reveals their card at the same time.
• If numbers differ, the team discusses and re-estimates until they agree.

Nigerian example: A team building a mobile app for a bank in Lagos uses Planning Poker to estimate features like “transfer money” and “check balance”.

    Planning Poker cards:
    [ 0 ] [ 1 ] [ 2 ] [ 3 ] [ 5 ] [ 8 ] [ 13 ] [ 21 ] [?] [∞]
    (Each team member holds one card face down)
    

Lesson 6: Prioritisation – Deciding what comes first

Definition: Prioritisation means ordering tasks from most important to least important.

Why important: We can’t do everything at once. We need to focus on what delivers the most value.

Simple explanation: When you pack for a trip, you pack your passport first, then clothes, then snacks. That’s prioritisation.

Technique – MoSCoW:

• Must have – essential (without it, the project fails).
• Should have – important but not critical.
• Could have – nice to have if time permits.
• Won’t have this time – will do later.

Nigerian example: A food delivery app in Abuja: “Must have” = menu and ordering, “Should have” = ratings, “Could have” = loyalty points.

Lesson 7: Release Planning – The big picture

Definition: Release planning is a long-term plan that shows when features will be delivered over several Sprints.

Why important: It helps stakeholders know when to expect new features.

Simple explanation: If you are building a house, release planning tells you when each room will be finished.

Steps:

• Estimate all items in the Product Backlog.
• Calculate your velocity (points per Sprint).
• Divide total points by velocity to get number of Sprints.
• That gives you your release date.

    Release Plan Example:
    Total Product Backlog points = 120
    Velocity = 20 points per Sprint
    Number of Sprints = 120 / 20 = 6 Sprints
    If each Sprint is 2 weeks, release in 12 weeks.
    

Lesson 8: Story Slicing – Breaking big tasks into smaller ones

Definition: Story slicing is breaking a large task into smaller, more manageable pieces.

Why important: Small tasks are easier to estimate, complete, and test.

Simple explanation: Instead of “build a whole website”, slice it into “homepage”, “contact page”, “about page”.

Nigerian example: A caterer doesn’t cook all meals at once – they cook jollof rice, then chicken, then salad.

Lesson 9: Estimating with T-shirt sizes

Some teams use T-shirt sizes instead of numbers: XS, S, M, L, XL.

This is a fun way to estimate, especially for beginners.

T-shirt size	Points (approx.)	Example
XS	1	Typo fix
S	2	Add a button
M	5	Create a login page
L	8	Add payment feature
XL	13	Build a whole reporting system

Lesson 10: Affinity Estimation – Grouping similar tasks

Definition: Affinity estimation is a technique where you group tasks by size without assigning exact numbers.

Why important: It’s fast and helps when you have many items to estimate.

How to do it: Put tasks on sticky notes. Move them into groups: “small”, “medium”, “large”. Then assign points to each group.

Lesson 11: Re-estimation – When to change your guess

As you learn more, your estimates might change. That’s okay – Agile welcomes change.

If a task turns out to be bigger than you thought, you can re-estimate it.

Example: You thought “add search bar” was a 2-point task, but you discover it needs a lot of testing – you change it to 5 points.

📌 Key Vocabulary

🧠 Important Concepts

• Relative sizing – it’s easier to compare than to guess exact time.
• Velocity consistency – once you know your velocity, you can predict future Sprints.
• Collaboration – estimation is a team activity, not one person’s job.

🔢 Step-by-step: How to estimate a backlog

1. Gather the team – everyone who will work on the tasks.
2. Choose a scale – e.g., Fibonacci numbers or T-shirt sizes.
3. Pick a reference task – choose one task that everyone agrees is “medium” (e.g., 5 points).
4. Estimate each task – compare each task to the reference.
5. Discuss disagreements – if estimates differ, talk about it until you agree.
6. Record estimates – write the point value next to each task.
7. Calculate velocity – after a Sprint, sum the points of completed tasks.

🌍 Real-life Examples

• Spotify: Uses story points to estimate new music features.
• Nigerian fintech: Uses Planning Poker to estimate mobile app updates.
• School project: You estimate each section of your project (research, writing, editing) using points.

🧸 Fun Examples for Children

• Lego building: Estimate how many bricks you need for a house – small house = 50 bricks, big house = 200 bricks.
• Drawing a comic: Estimate each page – a simple page = 1 point, a detailed page = 3 points.

🏠 Everyday Examples

• Homework: Estimate each subject: Maths = 2 points, English = 1 point, Science = 3 points.
• Chores: Washing dishes = 2 points, sweeping = 1 point, mopping = 3 points.

👪 Parent Tips

• Teach your child to break big tasks into small pieces – it reduces overwhelm.
• Play “estimation games” at home – guess how long it takes to walk to the shop, then check.
• Praise effort, not just accuracy – estimation is about learning.

💡 Interesting Facts

• Planning Poker was invented by James Grenning in 2002.
• Some teams use “bucket estimation” – they place tasks into buckets like “small”, “medium”, “large”.
• Velocity is not a performance metric – it’s a planning tool.

❓ Did You Know?

• Many Nigerian teams use Planning Poker with physical cards – it’s a great way to bond.
• Affinity estimation can be done with sticky notes and a whiteboard – no technology needed.

🔔 Remember This

• Estimates are not commitments – they are guesses that help us plan.
• Velocity is based on your team’s actual performance – it’s not a target.
• Estimate together – team collaboration leads to better results.
• Re-estimate when you learn something new.

⚠️ Common Mistakes

• “We must get the estimate exactly right.” – Wrong! Estimates are always uncertain.
• “Velocity is a competition.” – No, it’s a planning aid.
• “One person can estimate everything.” – Not true – team estimation is better.
• “We never re-estimate.” – Bad idea – re-estimate when you have more info.

✅ Best Practices

• Use a consistent scale (e.g., Fibonacci) across the team.
• Involve the whole team in estimation sessions.
• Track velocity over several Sprints to get a reliable average.
• Slice big stories into smaller ones before estimating.
• Celebrate when your estimates become more accurate over time.

📊 Diagrams

    Estimation Flow:
    Product Backlog → Estimate each item → Calculate total points
                ↓
    Velocity (points/Sprint) → Release Planning → Delivery date
    

📝 End-of-Module Summary

❓ Frequently Asked Questions

• Q1: What if I don't know how to estimate a task?
  That’s okay! Discuss it with your team. Break it down further.
• Q2: Can I estimate in hours instead of points?
  You can, but points are more consistent and less stressful.
• Q3: What is a good velocity?
  There is no “good” or “bad” velocity – it’s just a number for your team.
• Q4: How often should we re-estimate?
  Whenever you discover new information that changes the size of the task.
• Q5: Can we use Planning Poker for personal tasks?
  Yes! It’s a great way to involve family members in planning.
• Q6: What if the team can't agree on an estimate?
  Discuss the reasons – the person with the highest and lowest estimate explain their view.
• Q7: Should we estimate bugs?
  Yes, but they are often harder to estimate – you can use a smaller scale.
• Q8: Is velocity always constant?
  No, it can change based on team composition, holidays, or complexity.
• Q9: What is a “zero-point” story?
  A task that takes almost no effort (like changing a typo). Some teams use 0 or 0.5 points.
• Q10: Can I use T-shirt sizes for release planning?
  Yes, but you’ll need to convert them to points or time eventually.

🔗 Matching Exercise

Match the term with its correct definition.

Term	Definition
1. Story point	A. A number that represents the size of a task
2. Velocity	B. A game where the team estimates together
3. Planning Poker	C. Points completed per Sprint
4. MoSCoW	D. A prioritisation technique

(Answers: 1-A, 2-C, 3-B, 4-D)

🎭 Scenario-based Exercise

Scenario: You are leading a team of 5 students to build a school website. The Product Backlog has 20 items. Your team’s velocity is 10 points per Sprint. Each Sprint is 2 weeks.

Question: How many Sprints will you need to complete all 20 items if the total points are 40? How long will that take?

👥 Group Activity

In groups of 4, play a round of Planning Poker. Use a list of 5 tasks (e.g., “write a letter”, “draw a picture”, “build a small tower”). Each person uses cards (1, 2, 3, 5, 8). Discuss and reach consensus.

✍️ Individual Activity

Take a project you are working on (e.g., a school project, a hobby). Write down 5 tasks. Estimate each using T-shirt sizes (XS, S, M, L, XL). Then convert them to story points (e.g., XS=1, S=2, M=5, L=8, XL=13).

🛠️ Mini Project

Create a release plan for a small app (e.g., a “study timer” app). Write a Product Backlog with 10 items. Estimate each in story points. Assume a velocity of 8 points per Sprint. Plan how many Sprints you need.

📋 Practical Assignment

Over the next week, track your personal velocity for a chosen activity (e.g., reading pages per day, solving math problems). Calculate your average and use it to plan the following week.

🔑 Key Takeaways

• Estimation is about relative size, not exact time.
• Story points and velocity help you plan and forecast.
• Planning Poker is a fun, team-based estimation technique.
• Prioritise using MoSCoW to focus on what matters most.
• Release planning turns estimates into a timeline.
• Always slice big stories into smaller ones.

💬 Classroom Discussion Questions

• Why do you think relative sizing is better than guessing time?
• Have you ever estimated something and been wrong? What happened?
• How can we use velocity to help our school projects?
• Why is it important to involve the whole team in estimation?

🔜 Preparation for Module 4

In Module 4, we will explore Agile Metrics and Continuous Improvement. You will learn how to measure progress, track team health, and use data to get better. We’ll cover burndown charts, cumulative flow diagrams, and how to run effective retrospectives. Start thinking about how you might measure your own improvement – it could be in school, sports, or a hobby!

---

You have completed Module 3 – keep going!

📘 Module 4: Agile Metrics & Continuous Improvement

“What gets measured gets improved.” – Peter Drucker

🌟 Module Introduction

In the first three modules, we learned the Agile mindset, frameworks like Scrum and Kanban, and how to plan and estimate. But how do we know if we are actually getting better? How do we spot problems early?

That’s where metrics come in. Metrics are like the dashboard of a car – they tell you your speed, fuel level, and if something is wrong. In Agile, we use metrics to track progress, find bottlenecks, and improve continuously.

We will also talk about continuous improvement – the heart of Agile. It’s the idea that we should always look for ways to do better, little by little. We’ll use simple language, stories, and Nigerian examples to make everything clear. Let’s go!

🎯 Learning Objectives

• Define what an Agile metric is and why it’s useful.
• Read and interpret a Burndown Chart.
• Understand Cumulative Flow Diagrams.
• Use metrics to spot problems early.
• Explain the importance of the Sprint Retrospective.
• Apply continuous improvement to your daily life.

📖 Warm-up Story: The Football Coach

Imagine you are a football coach in Abuja. Your team plays every week, but you keep losing. You don’t know why.

One day, you start recording metrics: how many passes each player makes, how many shots on goal, how many fouls. After a few games, you see that your striker makes very few shots. You also see that the defense gives away many fouls.

Now you know what to fix. You practice shooting with the striker and teach the defense to tackle better. Your team improves!

That’s exactly what Agile metrics do – they give you information so you can improve. Let’s learn how.

📚 Main Lessons

Lesson 1: What are Agile Metrics?

Definition: Metrics are numbers or data that tell you how your project is going.

Why important: Without metrics, you are guessing. Metrics help you make smart decisions.

Simple explanation: Think of metrics like the scoreboard in a game. It tells you who is winning and where you need to improve.

Real-life example: A bakery tracks how many loaves of bread they sell each day – that’s a metric.

School example: Your test scores are metrics – they show how well you are learning.

Home example: You track how many chores you complete each week – that’s a metric.

Nigerian example: A small shop in Onitsha tracks how many customers come in each hour – to know when to add more staff.

    Metrics help you:
    - See progress
    - Spot problems early
    - Make decisions based on data, not feelings
    

Lesson 2: The Burndown Chart

Definition: A Burndown Chart shows how much work is left over time. It goes down (burns down) as you complete tasks.

Why important: It helps you see if you are on track to finish your Sprint on time.

Simple explanation: Imagine you have 10 chocolates. Each day you eat some. A burndown chart shows the number of chocolates left each day – it goes down!

Real-life example: A moving company tracks how many boxes are left to pack each day.

School example: You have 5 chapters to read in 5 days – each day you mark how many chapters are left.

Nigerian example: A tailor tracks how many dresses are left to sew each day before a wedding.

    Burndown Chart (Sprint of 10 days)
    Day 1: 30 points left
    Day 2: 28 points left
    Day 3: 25 points left
    ...
    Day 10: 0 points left (Sprint done!)
    (the line goes down like a slide)
    

Lesson 3: Cumulative Flow Diagram (CFD)

Definition: A CFD shows the amount of work in different states (To Do, Doing, Done) over time.

Why important: It helps you see bottlenecks – where work is piling up.

Simple explanation: Imagine a pipe. If water gets stuck, it’s a bottleneck. A CFD shows you where the clog is.

Real-life example: A car wash tracks how many cars are waiting, being washed, and finished.

Nigerian example: A printing press tracks jobs at each stage: “Ordered”, “Printing”, “Cutting”, “Delivered”.

    Cumulative Flow Diagram (simplified)
    Time →   | To Do | Doing | Done |
    Day 1    |  10   |   3   |   2   |
    Day 2    |   8   |   4   |   5   |
    Day 3    |   5   |   2   |   8   |
    (If “Doing” grows wide, you have a bottleneck)
    

Lesson 4: Cycle Time and Lead Time

Definitions:

• Lead Time: Total time from when a request is made until it’s delivered.
• Cycle Time: Time from when you start working on an item until it’s done.

Why important: Shorter times mean faster delivery and happier customers.

Simple explanation: At a restaurant, Lead Time = time from ordering to eating. Cycle Time = time from cooking to serving.

Real-life example: Online shopping – lead time is from order to delivery; cycle time is from packing to shipping.

Nigerian example: A generator repair shop – lead time is from when you bring it in to when you pick it up; cycle time is from when they start fixing it to when it’s fixed.

Lesson 5: Velocity – A key metric

We learned about velocity in Module 3. It’s the average number of story points completed per Sprint.

Why important: Velocity helps you forecast and plan future Sprints.

Simple explanation: If you run 2 km per day on average, you can predict how long it will take to run 10 km.

Remember: Velocity is not a performance target – it’s a planning tool.

Lesson 6: Throughput

Definition: Throughput is the number of tasks completed per unit of time (e.g., per week).

Why important: It shows how productive your team is, regardless of task size.

Simple explanation: If you send 10 emails per day, your throughput is 10 emails/day.

Nigerian example: A call centre in Lagos tracks how many customer calls they handle per hour – that’s throughput.

Lesson 7: WIP (Work In Progress) – A limit to improve flow

We covered WIP limits in Module 2. WIP is the number of tasks you are currently working on.

Tracking WIP helps you see if your team is overloaded. High WIP often means slower delivery.

Simple explanation: If you try to juggle 5 balls, you drop them. WIP limit = 3 balls – you juggle better.

Lesson 8: The Sprint Retrospective – The heart of improvement

Definition: The Sprint Retrospective is a meeting at the end of each Sprint where the team reflects and plans improvements.

Why important: This is where continuous improvement actually happens.

Simple explanation: It’s like a post-game review for a football team – you discuss what went well, what didn’t, and what to change.

Structure:

• What went well? (celebrate)
• What didn’t go well? (learn)
• What will we do differently next Sprint? (action)

Nigerian example: A group of students after a test – they discuss which topics were hard and plan extra study.

    Retrospective format:
    [ Start ] → [ Gather data ] → [ Insights ] → [ Decide actions ] → [ End ]
    (keep it positive and action-oriented)
    

Lesson 9: Continuous Improvement – The Agile way

Definition: Continuous improvement means always looking for small ways to get better.

Why important: Small improvements add up to big changes over time.

Simple explanation: If you improve 1% every day, you’ll be 37 times better after a year!

Real-life example: A basketball player practices free throws for 10 minutes extra each day – improves over time.

Nigerian example: A shopkeeper rearranges the shelf to make it easier for customers – a small improvement that boosts sales.

Lesson 10: Using metrics to improve – an example

Let’s put it all together. Your team sees that the Burndown Chart shows work is not decreasing fast enough. You look at the CFD and see that “Testing” has a huge backlog. You realise testing is the bottleneck.

You decide to add more testers or automate some tests. Next Sprint, the Burndown looks better. That’s using metrics to improve.

Lesson 11: Avoiding vanity metrics

Definition: Vanity metrics look good but don’t help you make decisions.

Example: “We wrote 100 pages of documentation” – but nobody reads it. That’s a vanity metric.

Better: “We completed 20 story points” – that actually matters.

📌 Key Vocabulary

🧠 Important Concepts

• Actionable vs Vanity metrics – use metrics that lead to action.
• Trends over individual numbers – one data point doesn’t tell you much; watch the trend.
• Improvement is a habit – not a one-time event.

🔢 Step-by-step: Running a Retrospective

1. Set the stage – explain the goal of the meeting.
2. Gather data – look at metrics, what happened.
3. Generate insights – ask “why” things happened.
4. Decide what to do – pick 1–2 improvements to try.
5. Close – thank the team and commit to actions.

🌍 Real-life Examples

• Google: Uses burndown charts to track project progress.
• Nigerian banks: Use cycle time to measure how fast they process loan applications.
• Schools: Teachers use test scores (metrics) to see which topics need more teaching.

🧸 Fun Examples for Children

• Video game: Track how many levels you complete each day – that’s your “velocity”.
• Lego building: Track how many bricks you use per hour – that’s throughput.

🏠 Everyday Examples

• Homework: Track how many assignments you finish per day – throughput.
• Chores: Track how long it takes to clean your room (cycle time) and improve it.

👪 Parent Tips

• Help your child track a simple metric (e.g., pages read per day) and watch them improve.
• Encourage them to reflect weekly – what went well, what didn’t, what to change.
• Celebrate improvements, no matter how small.

💡 Interesting Facts

• The Burndown Chart was inspired by project management charts used in the 1950s.
• Google’s Project Aristotle found that psychological safety is the #1 factor for team performance – retrospectives help build that.
• Many Nigerian companies now use Jira or Trello to track Agile metrics.

❓ Did You Know?

• You can use a simple notebook to track your own burndown chart – no software needed!
• Some teams celebrate “improvement days” where they only work on making things better.

🔔 Remember This

• Metrics are tools, not judgments.
• Always combine metrics with conversation – numbers alone don’t tell the whole story.
• Improvement is a journey, not a destination.

⚠️ Common Mistakes

• “We measure everything.” – Too many metrics confuse you. Focus on a few key ones.
• “We use velocity to compare teams.” – Never compare velocity across teams – it’s team-specific.
• “We don’t do retrospectives because we’re busy.” – This is a huge mistake – retrospectives save time in the long run.
• “We ignore metrics – they’re boring.” – Metrics help you win!

✅ Best Practices

• Track metrics that help you make decisions.
• Review metrics as a team every Sprint.
• Keep a log of improvements and their impact.
• Make retrospectives fun – use different activities.
• Always ask “What can we do better?”

📊 Diagrams

    Burndown Chart (simplified)
    Work left
      |
    30 | X
    25 |   X
    20 |     X
    15 |       X
    10 |         X
     5 |           X
     0 |_____________X___
        Day1 Day2 Day3 Day4 Day5
    
    CFD (simplified)
    | To Do | Doing | Done |
    |  10   |   2   |   3   |  Day1
    |   8   |   3   |   6   |  Day2
    |   5   |   3   |  10   |  Day3
    (Doing stays flat – may be a bottleneck)
    

📝 End-of-Module Summary

❓ Frequently Asked Questions

• Q1: What if our Burndown Chart goes up?
  That means new work was added – it’s okay! Just note it.
• Q2: How often should we look at metrics?
  At least every Sprint Review or Retrospective.
• Q3: Is velocity the most important metric?
  No – it’s useful, but not more important than team health or value delivered.
• Q4: Can we use metrics to punish people?
  Never – metrics are for improvement, not blame.
• Q5: What if our team doesn’t like retrospectives?
  Make them fun – use games, snacks, or change the format.
• Q6: How do we know which metric to track?
  Track what helps you answer: “Are we delivering value and improving?”
• Q7: Can I use a burndown chart for personal goals?
  Absolutely! Track your progress on a fitness or study goal.
• Q8: What is a “sprint goal”?
  It’s a short statement of what the Sprint aims to achieve – metrics help you see if you met it.
• Q9: How long should a Retrospective be?
  Usually 1 hour for a 2-week Sprint – but adapt to your team.
• Q10: What if we don’t have data to measure?
  Start small – even a simple “tasks done” list is a metric.

🔗 Matching Exercise

Match the metric with its description.

Metric	Description
1. Burndown Chart	A. Number of items completed per time
2. Velocity	B. Work in different states over time
3. Throughput	C. Points per Sprint
4. CFD	D. Work left over time

(Answers: 1-D, 2-C, 3-A, 4-B)

🎭 Scenario-based Exercise

Scenario: Your team’s Burndown Chart shows that at the end of Day 5 of a 10-day Sprint, you still have 60% of the work left. You look at the CFD and see that “Testing” has a huge backlog.

Question: What should you do? What metric would you use to track your improvement?

👥 Group Activity

In groups of 4, simulate a Sprint Retrospective. Each person shares one thing that went well, one thing that didn’t, and one improvement they suggest. Together, decide on two actions to try next Sprint.

✍️ Individual Activity

For one week, track a simple metric for a personal goal (e.g., pages read per day, exercise time). At the end of the week, reflect on what you learned and what you could improve.

🛠️ Mini Project

Create a Burndown Chart for a 5-day school project. Estimate the total work (e.g., 20 points). Each day, record how many points you have completed. Plot the chart and analyse if you are on track.

📋 Practical Assignment

In your next team meeting (or family meeting), run a mini-retrospective. Ask: “What went well?” “What didn’t?” “What will we change?” Document the actions and follow up.

🔑 Key Takeaways

• Metrics give you visibility into your project and team.
• Burndown charts show work remaining; CFDs show bottlenecks.
• Velocity, cycle time, lead time, throughput, and WIP are key metrics.
• The Sprint Retrospective is where improvement happens.
• Continuous improvement means always looking for small ways to get better.

💬 Classroom Discussion Questions

• Why do you think retrospections are so important?
• Can you think of a time when a metric helped you improve?
• What is the difference between a good metric and a bad metric?
• How could you use metrics in your daily life?

🔜 Preparation for Module 5

In Module 5, we will explore Advanced Agile Topics – including scaling Agile to large teams, distributed teams, and combining Agile with other practices like DevOps. You’ll also learn about the role of the Agile coach and how to lead change in an organisation.

Think about a large project (like building a whole school website) – how would you apply Agile with many teams? We’ll answer that next!

---

You have completed Module 4 – incredible progress!

📘 Module 5: Agile in the Real World – Scaling & Leadership

“Agile is not just for small teams – it can transform entire organisations.”

🌟 Module Introduction

Congratulations! You have learned the Agile mindset, frameworks, planning, estimation, and metrics. Now it’s time to see how Agile works in the real world – with big teams, remote workers, and entire companies.

In this final module, we will explore scaling Agile – how to use Agile when you have many teams working on the same product. We’ll also talk about Agile leadership – how to be a great servant leader, and how to lead change in an organisation.

We’ll use stories, examples from Nigeria, and simple language to make these advanced topics easy to understand. Let’s get started!

🎯 Learning Objectives

• Explain why Agile needs to be scaled for large projects.
• Describe the SAFe (Scaled Agile Framework) in simple terms.
• Understand the role of an Agile Coach.
• Identify challenges of distributed (remote) Agile teams and how to overcome them.
• Apply Agile principles to lead change in an organisation.
• Recognise how Agile is used in Nigerian companies and beyond.

📖 Warm-up Story: The Big Market

Imagine you are in a huge market in Lagos – like Balogun Market. There are hundreds of shops selling different things. Each shop works well on its own, but how do they all work together to make the market successful?

Now imagine that the market wants to become an online shopping platform. This is a massive project. One Agile team cannot do it alone – you need many teams: a team for the website, a team for payments, a team for delivery, and a team for customer service.

How do you coordinate all these teams? That’s what scaling Agile is all about. It’s like conducting an orchestra – each section plays its own part, but they all follow the same sheet music.

In this module, we learn how to conduct the orchestra!

📚 Main Lessons

Lesson 1: Why do we need to scale Agile?

Definition: Scaling Agile means using Agile methods for large projects with many teams.

Why important: Small teams can use Scrum or Kanban easily. But when you have 50 or 100 people, you need more coordination.

Simple explanation: Think of a small boat – one person can row it. A big ship needs a captain, a crew, and a system to steer it. That’s scaling.

Real-life example: Building a new airport – you have teams for construction, electrical, plumbing, and landscaping.

Nigerian example: A Nigerian bank building a new mobile app – they have a team for Android, iOS, backend, and security.

Lesson 2: SAFe – Scaled Agile Framework (simple version)

Definition: SAFe is the most popular framework for scaling Agile. It has levels: Team, Program, Large Solution, and Portfolio.

Why important: SAFe gives a clear structure for large organisations.

Simple explanation: SAFe is like a school system – you have classrooms (teams), grades (programs), and a principal (portfolio).

Key levels:

• Team level: Each team uses Scrum or Kanban.
• Program level: A group of teams (called an Agile Release Train or ART) works together on a product. They have a common vision and coordinate.
• Portfolio level: The highest level – decides what projects to invest in.

    SAFe Levels (simplified)
    ┌─────────────────────────────────┐
    │  Portfolio (strategy & funding) │
    ├─────────────────────────────────┤
    │  Program (ART – many teams)     │
    ├─────────────────────────────────┤
    │  Team (Scrum / Kanban)          │
    └─────────────────────────────────┘
    

Lesson 3: The Agile Release Train (ART)

Definition: An ART is a group of teams (usually 5–12) that work together to deliver a product or solution.

Why important: ART helps coordinate many teams so they don’t step on each other’s toes.

Simple explanation: Think of a train – the ART is the train, and each team is a carriage. They all move together.

Nigerian example: A telecom company in Lagos has an ART for their mobile money product – with teams for USSD, app, and backend.

Lesson 4: Agile Leadership – The Servant Leader

Definition: A servant leader puts the team first – they help the team succeed.

Why important: Agile teams need support, not control.

Simple explanation: Instead of being a “boss” who tells people what to do, a servant leader asks: “How can I help you?”

Real-life example: A football coach who brings water and gives encouragement – not just shouting orders.

School example: A teacher who walks around the classroom helping students who are stuck.

Nigerian example: A “chairman” of a local community who listens to people’s problems and finds solutions.

Lesson 5: The Agile Coach – The Change Agent

Definition: An Agile Coach helps teams and organisations adopt Agile practices.

Why important: Change is hard – a coach guides people through it.

Simple explanation: An Agile Coach is like a personal trainer for your team – they help you get fit in Agile.

Responsibilities:

• Teaching Agile principles.
• Coaching teams on Scrum and Kanban.
• Removing organisational barriers.
• Encouraging continuous improvement.

Lesson 6: Distributed (Remote) Agile Teams

Definition: Distributed teams work in different locations – sometimes in different cities or countries.

Why important: Many companies now have remote teams – especially after COVID-19.

Challenges:

• Time zone differences.
• Less face-to-face communication.
• Cultural differences.

Solutions:

• Use video calls for Stand-ups and Retrospectives.
• Use tools like Jira, Trello, or Slack.
• Overlap work hours by 2–3 hours for collaboration.
• Have a shared calendar and clear documentation.

Nigerian example: A Nigerian fintech has developers in Lagos, Abuja, and London – they use video calls and online boards to stay connected.

Lesson 7: Leading Change – The Kotter Model (simplified)

Dr. John Kotter created an 8-step model for leading change. Here’s the simple version:

1. Create urgency – make people see why change is needed.
2. Build a team – get people who support the change.
3. Create a vision – paint a picture of the future.
4. Communicate – talk about the vision often.
5. Remove obstacles – fix things that block change.
6. Create quick wins – show early success.
7. Keep going – don’t stop after one win.
8. Make it stick – embed the change in the culture.

Nigerian example: A company wants to go Agile – they start with one team (quick win), show success, then expand to other teams.

Lesson 8: Agile Culture – What it looks like

An Agile culture is one where people:

• Trust each other.
• Are not afraid to make mistakes.
• Collaborate instead of compete.
• Focus on value, not just activity.

Nigerian example: In some Nigerian companies, the culture is top-down. Agile culture encourages everyone to speak up – even junior staff.

Lesson 9: Agile in Nigerian Government and NGOs

Agile is not just for private companies. Some Nigerian government agencies and NGOs are starting to use Agile to deliver services faster.

Example: A state government uses Agile to build a portal for citizens to pay taxes – they release a simple version, get feedback, and improve.

Lesson 10: Agile and DevOps – A powerful combination

Definition: DevOps is a way to combine development (Dev) and operations (Ops) to deliver software faster and more reliably.

Why important: Agile focuses on building features; DevOps focuses on releasing them smoothly.

Simple explanation: Agile is like cooking, and DevOps is like plating and serving the food quickly.

Nigerian example: A Nigerian e-commerce company uses Agile to build new features and DevOps to deploy them every day.

Lesson 11: Your Agile Career – What next?

After learning all this, you might want to become:

• Scrum Master – help teams follow Agile.
• Product Owner – represent the customer.
• Agile Coach – guide teams and organisations.
• Agile Project Manager – lead Agile projects.

You can also get certified! The PMI-ACP is a great start. In Nigeria, many companies look for Agile professionals.

📌 Key Vocabulary

🧠 Important Concepts

• Organisational change – change is a journey, not an event.
• Psychological safety – people must feel safe to speak up.
• Continuous learning – Agile teams are always learning.

🔢 Step-by-step: Starting Agile in a large organisation

1. Start with one team – pilot project.
2. Get leadership buy-in – show them the value.
3. Train the team – teach Agile basics.
4. Run a few Sprints – learn by doing.
5. Show quick wins – demonstrate success.
6. Expand to more teams – scale gradually.
7. Create an Agile Centre of Excellence – support all teams.

🌍 Real-life Examples

• Amazon: Uses Agile with thousands of teams – each team is a “two-pizza team”.
• Nigerian banks: Are scaling Agile to deliver new digital products faster.
• Government: Some states are using Agile for citizen services.

🧸 Fun Examples for Children

• School fair: If your whole school is organising a fair, you have many teams – decorations, food, games, etc. That’s scaling!
• Video game: A big game like FIFA has hundreds of developers – they use scaled Agile.

🏠 Everyday Examples

• Family planning: If a large family plans a holiday, they have teams – one for bookings, one for packing, one for food.
• Community project: A community cleaning project has teams for different streets.

👪 Parent Tips

• Encourage your child to be a “servant leader” – help others succeed.
• Teach them that change is okay – and they can lead it.
• Get involved in community projects – a great way to practice scaling.

💡 Interesting Facts

• SAFe is used by over 70% of Fortune 500 companies.
• The Agile Coach role emerged because companies needed help transitioning.
• Nigeria has a growing community of Agile practitioners – many meetups and conferences.

❓ Did You Know?

• Some Agile teams use “virtual coffee breaks” to build connections in remote teams.
• Agile is used in healthcare, manufacturing, and even film production.

🔔 Remember This

• Agile is not just for small teams – it can be scaled.
• Leaders in Agile serve their teams.
• Change takes time – be patient.
• Always keep the customer at the centre.

⚠️ Common Mistakes

• “We will just use Scrum for all 100 teams.” – You need a scaling framework like SAFe.
• “We bought Jira – now we are Agile.” – Tools don’t make you Agile; mindset does.
• “We don’t need an Agile Coach.” – Coaching helps avoid common pitfalls.
• “We will change everything overnight.” – Change gradually – start small.

✅ Best Practices

• Start with a pilot team before scaling.
• Invest in Agile training for everyone.
• Use metrics to guide improvement, not punishment.
• Foster a culture of trust and psychological safety.
• Celebrate successes, big and small.

📊 Diagrams

    Scaling Agile Journey:
    Team 1 (pilot) → Team 2 → Team 3 → Program → Portfolio
    (start small, then expand)

    Change Model (Kotter simplified):
    Urgency → Team → Vision → Communicate → Remove Obstacles → Quick Wins → Keep Going → Make Stick
    

📊 Comparison: Small vs Scaled Agile

Feature	Small Team	Scaled (Large)
Number of teams	1–2	5–100+
Coordination	Daily Stand-ups	ART sync, Scrum of Scrums
Roles	PO, SM, Team	Plus Release Train Engineer, Solution Architect
Planning	Sprint Planning	PI Planning (Program Increment)

📝 End-of-Module Summary

❓ Frequently Asked Questions

• Q1: Is SAFe the only way to scale Agile?
  No – there are others like LeSS, Nexus, and DaD. SAFe is the most popular.
• Q2: Can I be an Agile Coach without experience?
  It’s best to start as a Scrum Master or team member first.
• Q3: How do we handle time zone differences?
  Find an overlap of 2–3 hours for key meetings.
• Q4: What if people resist Agile?
  Use the Kotter model – start with quick wins and communicate the vision.
• Q5: Is Agile expensive to implement?
  It can save money by reducing waste and delivering value faster.
• Q6: Can Agile work in government?
  Yes, many governments are adopting Agile for digital services.
• Q7: What is a “Scrum of Scrums”?
  A meeting where representatives from each team coordinate.
• Q8: How long does it take to scale Agile?
  It can take months to years – start small and grow.
• Q9: Do we need to change our organisational structure for Agile?
  Often yes – Agile works best with cross-functional, autonomous teams.
• Q10: What’s the next step after this course?
  Get certified (PMI-ACP), join Agile communities, and practice!

🔗 Matching Exercise

Match the scaling term with its description.

Term	Description
1. SAFe	A. A group of teams working together
2. ART	B. A leader who serves the team
3. Servant Leader	C. A framework for scaling Agile
4. Agile Coach	D. A guide for Agile adoption

(Answers: 1-C, 2-A, 3-B, 4-D)

🎭 Scenario-based Exercise

Scenario: Your company has 10 teams working on a single product. They are not coordinating well – features overlap, and releases are delayed. You are asked to help.

Question: What steps would you take to scale Agile in this company? Use the concepts from this module.

👥 Group Activity

In groups of 5, simulate a Program Increment (PI) Planning session. Each group represents a team. Together, plan a release for a large product (e.g., a school management system).

✍️ Individual Activity

Reflect on a time when you had to work with many people on a project. What challenges did you face? How could Agile scaling have helped?

🛠️ Mini Project

Design a scaled Agile structure for a fictional Nigerian company with 50 employees building a new product. Include team structures, roles, and a coordination plan.

📋 Practical Assignment

Interview a professional who works in a large organisation (or research online). Find out how they coordinate multiple teams. Write a short report comparing their approach to Agile scaling.

🔑 Key Takeaways

• Scaling Agile helps large organisations deliver value efficiently.
• SAFe is a popular framework for scaling.
• Servant leadership and Agile coaching are essential for success.
• Distributed teams need extra care and communication.
• Change is a process – use proven models like Kotter’s.
• Agile offers many rewarding career paths.

💬 Classroom Discussion Questions

• Why do you think some large companies struggle to adopt Agile?
• How would you convince a CEO to invest in Agile?
• What is the most important quality of an Agile leader?
• How can Agile help Nigeria’s development?

🏁 Congratulations – You’ve Completed All Modules!

You have now completed the full Certified Agile Practitioner course. You have learned:

• Module 1: Agile Mindset & Principles
• Module 2: Agile Frameworks – Scrum & Kanban
• Module 3: Agile Planning & Estimation
• Module 4: Agile Metrics & Continuous Improvement
• Module 5: Agile in the Real World – Scaling & Leadership

You are now ready to take the PMI-ACP certification exam or apply Agile in your projects. Keep learning, keep practicing, and never stop improving!

🎉 You are an Agile Practitioner! 🎉

---

Thank you for being part of this journey.

📘 Module 6: Agile Exam Prep & Career Pathways

“Your certification journey – turning knowledge into a career.”

🌟 Module Introduction

Congratulations! You have completed all five modules of this course. You now understand the Agile mindset, frameworks, planning, metrics, and even how to scale Agile in large organisations.

But what’s next? In this final module, we’ll help you prepare for the PMI-ACP certification exam and explore the career opportunities that Agile offers. We’ll give you tips, practice questions, and guidance on how to continue your learning journey.

Think of this module as your “launchpad” – it will give you the confidence to take the exam and start your Agile career. Let’s go!

🎯 Learning Objectives

• Understand the structure and content of the PMI-ACP exam.
• Apply study strategies and exam tips.
• Practice with sample questions.
• Identify career paths for Agile practitioners.
• Create a personal development plan for your Agile journey.

📖 Warm-up Story: The Big Exam

Imagine you have been training for a marathon for months. You’ve run many miles, you know the route, and you have the right shoes. On race day, you feel nervous but also excited. You know you are prepared.

The PMI-ACP exam is like that marathon. You’ve done the training (the five modules). Now it’s time to put your knowledge to the test. But don’t worry – just like a marathon, you can pace yourself, use strategies, and cross the finish line with confidence.

In this module, we’ll help you prepare so that exam day feels like just another training run – except this time, you get a certification at the end!

📚 Main Lessons

Lesson 1: Overview of the PMI-ACP Exam

Definition: The PMI-ACP (Agile Certified Practitioner) is a certification from the Project Management Institute (PMI) that validates your Agile knowledge.

Why important: It is one of the most recognised Agile certifications in the world.

Exam details:

• 120 questions (100 scored, 20 pretest).
• Time: 3 hours.
• Passing score: around 60-70% (varies).
• Cost: ~$435 for PMI members, ~$495 for non-members (subject to change).
• Based on the PMI-ACP Exam Content Outline.

Nigerian example: Many Nigerian professionals take the PMI-ACP to advance their careers in banks, tech hubs, and multinational companies.

Lesson 2: Exam Domains

The exam covers 7 domains (areas). We’ve covered all of them in this course!

• Domain 1: Agile Principles and Mindset (Module 1)
• Domain 2: Value-Driven Delivery (Module 1 & 3)
• Domain 3: Stakeholder Engagement (Module 1 & 2)
• Domain 4: Team Performance (Module 2 & 5)
• Domain 5: Adaptive Planning (Module 3)
• Domain 6: Problem Detection and Resolution (Module 4)
• Domain 7: Continuous Improvement (Module 4)

Illustration:

    PMI-ACP Domains (percentage of questions)
    ┌──────────────────────────────────────────────────────────────┐
    │ 1. Mindset         ████████░░░░ 16%                       │
    │ 2. Value Delivery  ████████░░░░ 16%                       │
    │ 3. Stakeholder     ████████░░░░ 16%                       │
    │ 4. Team Performance████████░░░░ 16%                       │
    │ 5. Adaptive Plan   ███████░░░░░ 12%                       │
    │ 6. Problem Solve   ██████░░░░░░ 10%                       │
    │ 7. Improvement     ██████░░░░░░ 10%                       │
    └──────────────────────────────────────────────────────────────┘
    

Lesson 3: Eligibility and Application

To apply for the PMI-ACP, you need:

• General project experience: 2,000 hours (about 1 year) of leading or managing projects.
• Agile project experience: 1,500 hours (about 8 months) of working on Agile projects.
• Training: 21 contact hours of Agile training (this course gives you that!).

Simple explanation: You need to have some experience, plus the training hours from this course.

Lesson 4: Study Strategies

• Review the modules: Go through all five modules again.
• Take practice exams: Simulate the real exam.
• Focus on weak areas: Use the domain percentages to guide you.
• Join study groups: Discuss with others.
• Use flashcards: For key terms.

Nigerian example: Many Nigerian candidates form WhatsApp study groups to share tips.

Lesson 5: Exam Day Tips

• Get a good night’s sleep.
• Eat a healthy breakfast.
• Arrive early (or log in early for online exams).
• Pace yourself: ~1.5 minutes per question.
• Flag difficult questions and come back later.
• Use process of elimination – remove obviously wrong answers.

    Exam time management:
    120 questions / 180 minutes = 1.5 minutes per question
    - Answer easy ones first
    - Flag hard ones
    - Use the last 10 minutes to review flagged questions
    

Lesson 6: Sample Questions (Part 1)

Question 1: The Agile Manifesto values “working software” over comprehensive documentation. Which of the following best reflects this?

• A) Writing detailed requirements before starting
• B) Creating a product that works and delivering value
• C) Writing 100 pages of design documents
• D) Testing only at the end of the project

Answer: B – working product is more valuable than extensive documentation.

Question 2: Which Scrum event is used to inspect and adapt the process?

• A) Sprint Planning
• B) Daily Stand-up
• C) Sprint Review
• D) Sprint Retrospective

Answer: D – the Retrospective is where the team improves its process.

Lesson 7: Sample Questions (Part 2)

Question 3: A Product Owner wants to add a new feature mid-Sprint. What should the team do?

• A) Add it immediately
• B) Add it after the Sprint
• C) Ask the Scrum Master to decide
• D) Cancel the Sprint

Answer: B – changes during a Sprint are discouraged; add it to the backlog for the next Sprint.

Question 4: Which metric shows work left over time in a Sprint?

• A) Cumulative Flow Diagram
• B) Burndown Chart
• C) Velocity
• D) Lead Time

Answer: B – Burndown Chart.

Lesson 8: Agile Career Paths

After certification, you can pursue many roles:

• Scrum Master: Help teams use Agile.
• Product Owner: Prioritise work and represent stakeholders.
• Agile Coach: Guide teams and organisations in Agile adoption.
• Agile Project Manager: Lead Agile projects.
• Release Train Engineer: Coordinate multiple teams in SAFe.

Nigerian example: In Nigeria, Scrum Masters and Product Owners are in high demand, especially in fintech and banking.

Lesson 9: Building Your Agile Network

• Join PMI Nigeria chapter.
• Attend Agile meetups and conferences.
• Connect with Agile practitioners on LinkedIn.
• Volunteer to speak or organise events.

Why important: Networking helps you learn, find mentors, and discover job opportunities.

Lesson 10: Continuous Learning

Agile is always evolving. To stay current:

• Read books (e.g., “Scrum” by Jeff Sutherland).
• Take advanced courses (e.g., SAFe, LeSS).
• Earn PDUs (Professional Development Units) to maintain your certification.
• Write articles or blog posts about your experiences.

Lesson 11: Your Personal Action Plan

Now it’s time to create your plan:

1. Set a goal: When will you take the exam? (e.g., within 3 months).
2. Review weak areas: Use the domain list to identify where you need more study.
3. Schedule study time: 1-2 hours per day.
4. Join a study group: Or find a study buddy.
5. Take mock exams: At least 3 before the real exam.
6. Apply for the exam: Submit your application on PMI’s website.
7. Book your exam date: Give yourself 4-6 weeks to prepare.

📌 Key Vocabulary

🧠 Important Concepts

• Certification is not the end – it’s a milestone.
• Experience matters – combine certification with practical application.
• Agile is a journey – keep learning and adapting.

🔢 Step-by-step: Your Certification Journey

1. Complete training – you’ve done this!
2. Gather experience – document your project work.
3. Submit application – on the PMI website.
4. Pay the fee – be ready for the exam cost.
5. Prepare and study – review modules, take practice tests.
6. Schedule and take the exam – choose a date.
7. Pass and celebrate!
8. Maintain certification – earn PDUs every 3 years.

🌍 Real-life Examples

• John, a Nigerian software developer: He took the PMI-ACP, got a Scrum Master job, and now leads three teams.
• Mary, a project manager: She earned her PMI-ACP and was promoted to Agile Program Manager.

🧸 Fun Examples for Children

• Video game achievement: Getting certified is like earning a “gold trophy” in a game – it shows you’re an expert!
• School: Finishing this course is like graduating to the next grade – you’re ready for more.

🏠 Everyday Examples

• Planning a family event: Use your action plan to organise it.
• Learning a new skill: Apply the same study strategies.

👪 Parent Tips

• Help your child set a learning goal and create a study plan.
• Encourage them to join clubs or groups related to their interests.
• Celebrate milestones – passing a practice test or completing a module.

💡 Interesting Facts

• PMI-ACP is one of the fastest-growing certifications in the world.
• There are over 40,000 PMI-ACP holders globally.
• Agile professionals earn on average 15-20% more than non-Agile project managers.

❓ Did You Know?

• You can take the PMI-ACP exam online from home.
• PMI offers a “Study Hall” with practice questions.
• Many Nigerian companies pay for their employees’ certification.

🔔 Remember This

• You are ready for the exam – trust your preparation.
• Your career is in your hands – take action.
• Agile is a community – you are not alone.

⚠️ Common Mistakes

• “I’ll study a week before the exam.” – Start early – give yourself at least 4-6 weeks.
• “I don’t need practice tests.” – Mock exams are essential for time management.
• “I’ll skip the application process.” – Apply well in advance.
• “I’ll wait for a perfect time.” – The perfect time is now – start your journey.

✅ Best Practices

• Use multiple study resources – books, videos, practice tests.
• Join a study group for motivation and support.
• Take breaks and rest – your brain needs time to absorb.
• Stay positive and believe in yourself.

📊 Diagrams

    Your Journey to Certification
    ┌────────────────────────────────────────────────────────────────────┐
    │  1. Learn (5 modules) → 2. Practice (mock exams) → 3. Apply       │
    │       ↓                       ↓                        ↓           │
    │  4. Study (review) → 5. Take Exam → 6. Celebrate! 🎉              │
    └────────────────────────────────────────────────────────────────────┘
    

📊 Comparison: Self-Study vs. Bootcamp

Method	Pros	Cons
Self-Study	Flexible, low cost	Need self-discipline
Bootcamp	Structured, immersive, group support	Costly, fixed schedule
Combination	Best of both	Requires more effort

📝 End-of-Module Summary

❓ Frequently Asked Questions

• Q1: How long should I study for the PMI-ACP?
  Most people study 2-3 months, 1-2 hours per day.
• Q2: Can I take the exam online?
  Yes, PMI offers online proctored exams.
• Q3: What if I fail the exam?
  You can retake it – wait 30 days for the first retake.
• Q4: How much does the exam cost?
  ~$435 for PMI members, ~$495 for non-members.
• Q5: Do I need a degree to get certified?
  No, but you need the experience requirements.
• Q6: Can I use this course as the 21 contact hours?
  Yes, this course provides the required 21 hours.
• Q7: How do I maintain my certification?
  Earn 30 PDUs every 3 years.
• Q8: Is the PMI-ACP recognised in Nigeria?
  Yes, it is highly recognised by multinationals and local companies.
• Q9: Can I become an Agile Coach without PMI-ACP?
  Yes, but the certification adds credibility.
• Q10: What is the pass rate for PMI-ACP?
  PMI does not publish pass rates, but it is generally around 60-70%.

🔗 Matching Exercise

Match the career role with its primary responsibility.

Role	Responsibility
1. Scrum Master	A. Prioritises and manages the backlog
2. Product Owner	B. Helps teams follow Agile
3. Agile Coach	C. Guides Agile adoption at scale
4. Release Train Engineer	D. Coordinates multiple teams in SAFe

(Answers: 1-B, 2-A, 3-C, 4-D)

🎭 Scenario-based Exercise

Scenario: You have just passed the PMI-ACP exam. You want to find a job as a Scrum Master. Your CV is ready, but you don’t have much experience.

Question: What steps would you take to improve your chances of getting hired? (Think about networking, internships, volunteering, and continuous learning.)

👥 Group Activity

In groups of 4, create a “Study Plan” for the PMI-ACP. Decide how many weeks you need, what resources to use, and how you will track progress. Share your plan with the class.

✍️ Individual Activity

Create your personal action plan using the template from Lesson 11. Write down your exam date, study schedule, and resources. Commit to it.

🛠️ Mini Project

Design a “Practice Exam” with 20 questions covering all 7 domains. Write the questions and the correct answers with explanations. Swap with a classmate and take each other’s exams.

📋 Practical Assignment

Visit the PMI website and review the PMI-ACP application process. Gather your project experience details and start filling out the application. Submit it within the next 2 weeks.

🔑 Key Takeaways

• The PMI-ACP is a globally recognised Agile certification.
• The exam covers 7 domains – all covered in this course.
• Preparation is key – study, practice, and plan.
• Agile offers diverse career opportunities.
• Your action plan is your roadmap to success.
• Remember: you are capable, and we believe in you!

💬 Classroom Discussion Questions

• What part of the PMI-ACP exam do you think will be most challenging for you? Why?
• Which career path in Agile excites you the most, and why?
• How can you continue learning Agile after you get certified?
• What is one thing you will do differently after this course?

🏁 You’ve Reached the Finish Line!

You have now completed all six modules of the Certified Agile Practitioner course. You’ve learned:

• Module 1: Agile Mindset & Principles
• Module 2: Agile Frameworks – Scrum & Kanban
• Module 3: Agile Planning & Estimation
• Module 4: Agile Metrics & Continuous Improvement
• Module 5: Agile in the Real World – Scaling & Leadership
• Module 6: Agile Exam Prep & Career Pathways

You are now fully prepared to take the PMI-ACP exam and start your Agile career. Remember:

• Keep learning – Agile is a journey.
• Practice – apply what you’ve learned.
• Network – connect with other Agile professionals.
• Believe in yourself – you have what it takes!

🎉 You are an Agile Champion! 🎉

---

Thank you for your dedication. Go out there and make a difference!