Velocity in Agile: What It Means and How to Track It

Velocity in Agile: A Plain Guide for Nigerian Teams

Velocity is one of the most useful Agile metrics. However, many Nigerian teams misuse or misunderstand it. Lagos Data School helps Nigerian teams track velocity correctly. Therefore, this guide explains what velocity is and how to use it.

This may contain: the agile cycle is shown in this graphic

Also, it covers how to calculate, track, and improve velocity over time. By the end, your team will use velocity to plan sprints with confidence.

 

What Is Velocity in Agile?

Velocity is the amount of work a team completes in one sprint. Furthermore, it is measured in story points. Story points represent the size and complexity of a backlog item.

Also, they are not the same as hours or days of work. Consequently, velocity shows how much a team can deliver reliably. In short, velocity is your team’s delivery power per sprint.

 

What Are Story Points?

Story points are a relative measure of effort. Furthermore, teams assign points using a scale like Fibonacci: 1, 2, 3, 5, 8, 13. A simple task gets 1 or 2 points.

Also, a complex task may get 8 or 13 points. Consequently, points capture complexity, risk, and effort together. Therefore, they are more accurate than estimating in hours alone.

 

Simple Nigerian Example

A Lagos fintech team completes the following in Sprint 1. Furthermore, each item has a story point value assigned.

Backlog Item Story Points Status
User registration form 3 Done
Email verification flow 5 Done
Password reset feature 3 Done
Paystack payment integration 8 Done
Profile update screen 5 Done

 

The team completed all five items. Also, the total story points completed equal 24. Therefore, this team’s velocity for Sprint 1 is 24 story points.

 

How to Calculate Your Team’s Velocity

Velocity is calculated at the end of every sprint. Furthermore, only fully completed items count toward velocity. Items that are started but not finished are not counted.

Also, partially completed items carry zero points. Consequently, the team has a strong incentive to finish work fully. Therefore, avoid half-done items at the end of every sprint.

 

How to Calculate Average Velocity

Use the last three to five sprints to calculate average velocity. Furthermore, add the story points from each sprint together. Then, divide the total by the number of sprints.

Also, use the average, not the highest sprint, for planning. Consequently, sprint commitments stay realistic and achievable.

 

Nigerian Example: Average Velocity Calculation

Sprint Story Points Completed Notes
Sprint 1 24 First sprint — team still learning
Sprint 2 28 Team improved after retrospective
Sprint 3 30 Strong sprint, no blockers
Sprint 4 27 One team member was on leave
Sprint 5 31 New tools adopted this sprint
Average 28 Use 28 points for future sprint planning

 

How to Use Velocity for Sprint Planning

Use your average velocity to set your sprint commitment. Furthermore, do not commit to more points than your average.

Also, reduce the commitment when team members are on leave. Consequently, sprint goals are met consistently rather than missed. However, do not use velocity to push the team to go faster. Therefore, treat velocity as a planning tool — not a performance target.

 

How to Track Velocity Over Time

 

Use a Velocity Chart

A velocity chart shows story points completed for each sprint. Furthermore, it reveals trends over time at a glance.

Also, rising velocity shows a team that is improving. However, a sudden drop signals a problem that needs investigation. Consequently, review the velocity chart at every sprint planning session.

 

Use a Sprint Burndown Chart

A burndown chart tracks work remaining during the sprint. Furthermore, it shows whether the team is on track day by day.

Also, Jira and ClickUp generate burndown charts automatically. Consequently, problems are spotted mid-sprint rather than at the end. Therefore, use both the velocity chart and the burndown chart together.

 

Common Velocity Mistakes Nigerian Teams Make

Mistake What Happens Fix
Comparing teams Team A feels inferior to Team B Never compare velocity across teams
Counting incomplete items Velocity looks higher than it is Count only fully done items
Ignoring leave days Team overcommits every sprint Subtract leave from capacity first
Using velocity as a target Team rushes and cuts quality Use velocity for planning only
Changing story point scale Historical data becomes useless Keep the same scale for all sprints

 

How to Improve Velocity Over Time

Improve velocity by removing blockers faster each sprint. Furthermore, better backlog grooming reduces rework mid-sprint.

Also, consistent retrospectives fix process problems that slow the team. Consequently, velocity rises naturally when teamwork improves. However, never force velocity up by reducing quality standards. Therefore, sustainable improvement always beats short-term speed.

 

Free Resource: Atlassian Velocity Guide

Lagos Data School recommends the Atlassian Agile Velocity Guide as a free reference. Furthermore, it explains velocity charts with clear visual examples.

Also, it covers how to use Jira to track velocity automatically.

 

How Lagos Data School Teaches Agile Velocity

Lagos Data School teaches sprint velocity in its live Agile project management course. Students calculate velocity, build sprint plans, and read velocity charts. Furthermore, every exercise uses real Nigerian team sprint data. Consequently, graduates track and apply velocity correctly from day one.

Visit the Lagos Data School training page to enrol. Also, see our graduates’ Agile work in the Lagos Data School student portfolio.

 

Frequently Asked Questions

Q1: Is a higher velocity always better?

No. Higher velocity only matters if quality stays the same. Furthermore, rushing to increase velocity often leads to more bugs. Therefore, a stable, predictable velocity is more valuable than a fast one.

 

Q2: What is a good velocity for a Nigerian team?

There is no universal good velocity. Also, velocity depends on team size, complexity, and story point scale. Therefore, compare your team’s velocity only to its own past sprints.

 

Q3: Can non-tech Nigerian teams use velocity?

Yes. Any team that uses story points or task counts can track velocity. Furthermore, Lagos marketing and HR teams use task-count velocity effectively. Therefore, velocity is useful for any Nigerian team that delivers work in cycles.

 

Track Velocity Confidently with Lagos Data School

Velocity turns sprint data into reliable delivery forecasts. Furthermore, it helps Nigerian teams plan better and commit honestly. Lagos Data School teaches you to track and use velocity on any Agile team.

Visit Lagos Data School and enrol in the Agile course today.

What Is Scrum? A Plain-English Guide for Beginners

What Is Scrum? Everything Nigerian Beginners Need to Know

Scrum is the most popular Agile framework in the world. However, many Nigerian professionals still find it confusing. Lagos Data School explains Scrum in plain, simple English. Therefore, this guide covers everything a beginner needs to know.

This may contain: the word scrum is surrounded by gears and cogwheels, which are connected to

Also, it uses Nigerian examples to make every concept clear. By the end, you will understand Scrum well enough to use it.

 

The One-Sentence Definition of Scrum

Scrum is a framework for delivering work in short, focused cycles. Furthermore, each cycle is called a sprint and lasts one to four weeks. Also, the team reviews progress at the end of every sprint. Consequently, the product improves with every single cycle. In short, Scrum replaces guesswork with a clear, repeating rhythm.

 

Where Did Scrum Come From?

Scrum was created by Ken Schwaber and Jeff Sutherland in 1995. Furthermore, its official rules are documented in the free Scrum Guide. Also, it is used by millions of teams across every industry. Consequently, Nigerian tech companies, banks, and NGOs all use Scrum today. Therefore, learning Scrum opens doors across every Nigerian career sector.

 

The Three Scrum Roles

Scrum defines three roles and three roles only. Furthermore, each role has a clear and distinct responsibility.

 

Role 1: Product Owner

The Product Owner decides what the team builds and in what order. Furthermore, they manage the product backlog every day.

Also, they represent the voice of the customer inside the team. Consequently, the team always works on the most valuable items first. In Nigeria, the Product Owner is often the founder, PM, or client lead.

 

Role 2: Scrum Master

The Scrum Master is the servant-leader of the Scrum team. Furthermore, they remove blockers that slow the team down. Also, they facilitate all four Scrum ceremonies every sprint. Consequently, the team follows the Scrum process correctly and consistently. In short, the Scrum Master protects the team and the process.

 

Role 3: Developers

Developers are all the people who build the product. Furthermore, this includes designers, testers, and engineers. Also, developers self-organise and plan their own sprint tasks. Consequently, the team takes ownership of its commitments fully. Therefore, Scrum developers are accountable to the sprint goal — not to a manager.

 

The Three Scrum Artefacts

Scrum uses three artefacts to manage and track work. Furthermore, each artefact serves a specific purpose in the framework.

 

Artefact 1: Product Backlog

The product backlog is a prioritised list of all work to be done. Furthermore, the Product Owner owns and updates it continuously. Also, every new feature, fix, or improvement goes into the backlog. Consequently, the team always has a clear list of what to build next.

 

Artefact 2: Sprint Backlog

The sprint backlog contains the items selected for the current sprint. Furthermore, it is created during sprint planning. Also, it shows every task the team has committed to this sprint. Consequently, the sprint backlog is the team’s daily to-do list.

 

Artefact 3: Product Increment

The increment is the working product delivered at the end of each sprint. Furthermore, it must meet the team’s Definition of Done. Also, the increment is potentially shippable — ready for users. Therefore, every sprint adds real, tested value to the product.

 

The Four Scrum Ceremonies

Scrum uses four ceremonies to create its delivery rhythm. Furthermore, each ceremony has a fixed time box and a clear purpose.

Ceremony When Time Box Purpose
Sprint Planning Start of sprint 2 hrs per week of sprint Set sprint goal and select backlog items
Daily Scrum Every day 15 minutes Sync the team and surface blockers
Sprint Review End of sprint 1 hr per week of sprint Demo the increment to stakeholders
Retrospective End of sprint 45 mins per week Improve the team process next sprint

 

How a Scrum Sprint Works: Day by Day

 

Day 1: Sprint Planning

The team meets to set the sprint goal and select backlog items. Furthermore, each item is broken into tasks for the week ahead. Also, the team confirms it has enough capacity to meet the goal. Consequently, the sprint starts with full clarity and team alignment.

 

Days 2–13: Daily Scrum and Sprint Work

Every morning, the team holds a fifteen-minute stand-up. Furthermore, each member answers three simple questions.

First: what did I finish yesterday?

Second: what will I do today?

Third: what is blocking me?

Also, the Scrum Master resolves blockers as soon as they surface. Consequently, the team stays on track toward the sprint goal daily.

 

Day 14: Sprint Review and Retrospective

The team demos the working increment to stakeholders. Furthermore, feedback is gathered and added to the product backlog. Also, the retrospective follows immediately after the review. Consequently, the next sprint is planned with both fresh feedback and process improvements.

 

Nigerian Teams Using Scrum Right Now

  • Lagos fintech teams: Run two-week sprints to release payment features continuously.
  • Abuja government IT teams: Use Scrum to deliver digital service portals in phases.
  • Port Harcourt software agencies: Manage client projects with sprint reviews every two weeks.
  • Nigerian edtech startups: Update course content and platform features every sprint.

 

Scrum vs Agile: Are They the Same Thing?

No. Agile is a mindset and a set of values. Furthermore, Scrum is one specific framework for applying Agile. Also, other Agile frameworks like Kanban and XP exist alongside Scrum.

Consequently, all Scrum teams are Agile, but not all Agile teams use Scrum. In short, Scrum is the most popular way to practise Agile in Nigeria.

 

Free Resource: The Official Scrum Guide

Lagos Data School recommends the free Scrum Guide as the first thing every beginner should read. Furthermore, it is short, clear, and written by Scrum’s two founders.

Also, it is available in over thirty languages for free download. Therefore, every Nigerian Scrum beginner should read it this week.

 

How Lagos Data School Teaches Scrum

Lagos Data School delivers live Scrum training for Nigerian professionals. Students run full sprint simulations using real Nigerian project scenarios.

Furthermore, they practise all four Scrum ceremonies in every course module. Consequently, graduates step into Scrum roles with practical confidence.

Visit the Lagos Data School training page to enrol today. Also, explore our graduates’ Scrum projects at the Lagos Data School student portfolio.

 

Frequently Asked Questions

Q1: Do I need a certification to use Scrum in Nigeria?

No. Any team can start using Scrum without a certification. However, a CSM or PSM I certification proves your knowledge to employers. Also, Lagos Data School prepares students for both certifications. Therefore, certification is strongly recommended for career growth.

 

Q2: How long does it take to learn Scrum?

You can learn Scrum basics in one to two days of structured training. Furthermore, practical sprint experience builds real confidence quickly. Also, most Nigerian professionals feel comfortable with Scrum after two sprints. Therefore, start practising immediately after your first training session.

 

Q3: Can Scrum work for teams outside tech in Nigeria?

Yes. Nigerian marketing, HR, operations, and events teams all use Scrum. Furthermore, the ceremonies and artefacts apply to any work delivered in cycles. Also, Lagos Data School trains non-tech Nigerian professionals in Scrum regularly. Consequently, Scrum is a universal tool — not just a developer framework.

 

Q4: What is the biggest benefit of Scrum for Nigerian teams?

The biggest benefit is early and frequent delivery of real results. Furthermore, Nigerian clients see working products every two weeks. Also, problems are caught in sprint one rather than at the final deadline. Consequently, Nigerian Scrum teams earn client trust much faster than waterfall teams.

 

Start Your Scrum Journey with Lagos Data School

Scrum is the most practical Agile framework for Nigerian teams. Furthermore, it works across tech, banking, NGOs, and beyond. Lagos Data School gives you the live training and practice to master Scrum.

Visit Lagos Data School and enrol in the Scrum course today.

Scrum Roles Explained: Complete 2026 Guide

Scrum Roles Explained for Nigerian Professionals

Scrum defines exactly three roles, no more, no less. Furthermore, each role has a clear and distinct purpose. Lagos Data School teaches every Scrum role in its live Agile course. Therefore, this guide explains all three roles in plain English.

This may contain: three men holding signs with the words three main scrum roles

Also, Nigerian examples are used throughout to make each role practical. By the end, you will know exactly which role fits your career.

 

Why Scrum Defines Only Three Roles

Traditional project teams have many job titles and layers. However, Scrum keeps things simple on purpose. Fewer roles mean fewer silos and faster decisions.

Also, every person on the team knows their responsibility clearly. Consequently, Nigerian Scrum teams move faster than traditional teams. Therefore, Scrum’s three-role structure is a deliberate design choice.

 

Role 1: The Product Owner

The Product Owner decides what the team builds. Furthermore, they decide the order in which items are built.

Also, they manage the product backlog every single day. Consequently, the team always works on the most valuable item first. In short, the Product Owner is the voice of the customer inside the team.

 

What the Product Owner Does Every Sprint

  • Writes user stories: Each backlog item is described from the user’s point of view.
  • Sets priorities: High-value items sit at the top of the backlog always.
  • Defines acceptance criteria: Each item has a clear pass or fail condition.
  • Attends sprint review: Feedback from stakeholders is gathered every sprint.
  • Updates the backlog: New ideas and feedback are added after every sprint review.

 

The Product Owner in Nigerian Teams

In Nigerian startups, the Product Owner is often the founder. Furthermore, in Nigerian banks, this role is often a digital product manager.

Also, NGOs in Nigeria assign this role to the programme lead. Consequently, the Product Owner role exists in every Nigerian industry. Therefore, learning this role opens doors across every Nigerian sector.

 

What Makes a Great Nigerian Product Owner?

A great Product Owner understands both the business and the users. Also, they make fast, clear decisions under pressure. Furthermore, they say no to low-value requests without hesitation. Consequently, the team builds fewer features but each one matters more.

 

Role 2: The Scrum Master

The Scrum Master is the team’s servant-leader and coach. Furthermore, they protect the team from outside distractions.

Also, they remove blockers that slow the team down. Consequently, the team focuses on sprint work rather than internal politics. In short, the Scrum Master serves the team — not the other way around.

 

What the Scrum Master Does Every Sprint

  • Facilitates ceremonies: Planning, stand-ups, reviews, and retrospectives are all run by the Scrum Master.
  • Removes blockers: Any obstacle slowing the team is escalated and resolved fast.
  • Coaches the team: Agile principles and Scrum practices are taught continuously.
  • Shields the team: Unplanned work and stakeholder interference are blocked during the sprint.
  • Tracks progress: Burndown charts and velocity data are monitored every day.

 

The Scrum Master in Nigerian Teams

Many Nigerian companies promote a developer into the Scrum Master role. However, the Scrum Master is a coaching role — not a technical one. Furthermore, the best Nigerian Scrum Masters are patient and process-focused.

Also, they coach managers and executives on how to support Agile teams. Consequently, the Scrum Master role is one of the most impactful in Nigeria.

 

Scrum Master vs Project Manager: Key Difference

Area Scrum Master Project Manager
Authority No formal authority over the team Authority to assign tasks
Focus Team process and Agile principles Scope, budget, and timeline
Style Servant-leader and coach Planner and director
Planning Guides sprint planning only Owns the full project plan
Nigerian salary ₦3m – ₦8m per year ₦4m – ₦12m per year

 

Role 3: The Developers (Development Team)

Developers are all the people who build the product. Furthermore, this includes designers, testers, writers, and engineers.

Also, the term ‘developer’ in Scrum means anyone who creates the product. Consequently, non-programmers are also called developers in Scrum. Therefore, the word ‘developer’ is broader than most Nigerians assume.

 

What Makes the Scrum Development Team Unique?

Scrum teams self-organise without a manager assigning tasks. Furthermore, each developer decides their own daily work.

Also, the team takes shared ownership of the sprint goal. Consequently, accountability sits with the whole team — not just one person. In addition, Scrum teams are cross-functional — each member brings a different skill.

 

The Right Size for a Nigerian Scrum Team

A Scrum team works best with three to nine developers. Furthermore, smaller teams move faster but carry more risk.

Also, larger teams need more coordination and can slow down. Therefore, five to seven developers is the sweet spot for most Nigerian teams.

 

How All Three Roles Work Together

Situation Product Owner Does Scrum Master Does Dev Team Does
Sprint Planning Presents top backlog items Facilitates the meeting Estimates and commits
Daily Stand-up Listens and notes blockers Runs the 15-min meeting Updates progress daily
Sprint Review Accepts or rejects the demo Organises the event Demos the increment
Retrospective Participates as a team member Facilitates improvement actions Raises honest feedback

 

Free Resource: The Official Scrum Guide

Lagos Data School recommends the free Scrum Guide as the first reference for all three roles. Furthermore, it defines every role, event, and artefact in detail.

Also, it is written by Scrum’s founders and available in many languages.

 

How Lagos Data School Teaches Scrum Roles

Lagos Data School covers all three Scrum roles in its live Agile course. Students practise each role in sprint simulations using Nigerian scenarios. Furthermore, role-play exercises build real confidence before the workplace. Consequently, graduates step into any Scrum role from day one of their new job.

Visit the Lagos Data School training page to enrol today. Also, see our graduates’ Scrum work at the Lagos Data School student portfolio.

 

Frequently Asked Questions

Q1: Can one person hold two Scrum roles?

The Product Owner and Scrum Master roles must always be separate people. However, a developer can also serve as Scrum Master on very small teams. Also, the Scrum Guide discourages this for teams larger than five people. Therefore, keep the three roles separate as the team grows.

 

Q2: Which Scrum role pays most in Nigeria?

Senior Product Owners typically earn the most in Nigerian tech. Furthermore, Scrum Masters at senior level earn competitively in banks and fintechs. Also, experienced developers with Scrum skills earn premium salaries in Lagos. Therefore, all three roles offer strong earning potential in Nigeria.

 

Q3: Do I need certification for a Scrum role in Nigeria?

No certification is required to start in a Scrum role. However, a CSPO, CSM, or PSM I certification improves your job prospects. Also, Lagos Data School prepares students for all three certifications. Therefore, certification accelerates your entry into Nigerian Scrum roles.

 

Start Your Scrum Role Journey with Lagos Data School

Every great Scrum team needs a strong Product Owner, Scrum Master, and Dev Team. Furthermore, Nigerian companies are hiring for all three roles right now. Lagos Data School gives you the training to fill any Scrum role with confidence.

Visit Lagos Data School and enrol in the Scrum course today.

Scrum Events Explained: Your Complete 2026 Guide

Scrum Events Explained for Nigerian Teams

Scrum uses five events to create its delivery rhythm. Furthermore, each event has a strict time box and a clear purpose. Lagos Data School teaches every Scrum event in its live Agile training.

This may contain: a diagram with the words sprint, scrum, and other related items in it

Therefore, this guide explains all five events in plain English. Also, Nigerian work examples are used throughout to make each one practical. By the end, you will know what happens in every Scrum event.

 

Why Scrum Events Matter for Nigerian Teams

Many Nigerian teams adopt Scrum but skip some of the events. However, skipping even one event breaks the Scrum rhythm. Also, each event feeds directly into the next one. Consequently, the whole delivery cycle breaks down when events are missed. Therefore, run all five events every sprint without exception.

 

Event 1: The Sprint

The Sprint is the container for all other Scrum events. Furthermore, it is a fixed time box of one to four weeks. Also, a new sprint starts immediately after the previous one ends. Consequently, the team delivers value in a continuous, unbroken rhythm. In short, the Sprint is the heartbeat of every Scrum team.

 

The Sprint Rules Every Nigerian Team Must Follow

  • Sprint goal is fixed: The sprint goal cannot be changed once the sprint starts.
  • Sprint length is fixed: Two weeks is the most common sprint length in Nigeria.
  • No external interruptions: Unplanned work from outside cannot enter a sprint in progress.
  • Cancel only in extreme cases: Only the Product Owner can cancel a sprint if the goal becomes obsolete.

 

Choosing a Sprint Length for Nigerian Teams

Sprint Length Best For Nigeria Trade-off
1 week Startups and rapidly changing projects Very fast pace, less time to build
2 weeks Most Nigerian tech and fintech teams Balanced pace — the most common choice
3 weeks Mid-size product teams with complex work More time to build, slower feedback
4 weeks Large enterprise projects in Nigeria Slowest feedback loop — use with caution

 

Event 2: Sprint Planning

Sprint Planning opens every new sprint. Furthermore, the whole Scrum team attends this meeting together.

Also, it is time-boxed to two hours for every week of sprint length. Consequently, a two-week sprint gets a four-hour planning session. Therefore, a two-week sprint gets exactly four hours of planning time.

 

What Happens During Sprint Planning?

First, the Product Owner presents the top backlog items. Also, the sprint goal is defined and agreed by the whole team. Furthermore, developers estimate effort using story points.

Next, selected items are broken into daily tasks. Finally, the team confirms it can meet the sprint goal with current capacity.

 

Nigerian Sprint Planning Example

A Lagos healthtech team runs two-week sprints. Furthermore, their Sprint 8 goal is: ‘Patients can book appointments online.’ Also, the team selects five backlog items totalling 26 story points.

Consequently, the planning meeting finishes in exactly four hours. Therefore, every developer leaves with a clear first task for the next morning.

 

Event 3: The Daily Scrum (Daily Standup)

The Daily Scrum is a fifteen-minute meeting held every morning. Furthermore, the whole development team attends — but only developers speak.

Also, the Scrum Master facilitates and keeps it strictly to time. Consequently, the team syncs and surfaces blockers before the day starts. In short, the Daily Scrum is the team’s daily heartbeat check.

 

The Three Daily Scrum Questions

  • What did I complete since the last Daily Scrum?
  • What will I complete before the next Daily Scrum?
  • Is anything blocking my progress right now?

 

Daily Scrum Tips for Nigerian Teams

Hold the standup standing up — it keeps the meeting short. Also, start at the same time every day without exception. Furthermore, move detailed problem-solving conversations outside the standup. Consequently, the fifteen-minute limit is respected every day. In addition, the Scrum Master removes any blocker raised before the next day.

 

Event 4: The Sprint Review

The Sprint Review is held at the end of every sprint. Furthermore, the team demos the working increment to stakeholders. Also, the Product Owner formally accepts or rejects each completed item. Consequently, stakeholders see real working software, not just slide decks. Therefore, trust between the team and the client grows every sprint.

 

What Happens During the Sprint Review?

  • Demo the increment: The team shows what was built this sprint.
  • Gather feedback: Stakeholders ask questions and suggest improvements.
  • Update the backlog: The Product Owner adds feedback as new backlog items.
  • Review the roadmap: The product direction is adjusted based on real sprint outcomes.

 

Sprint Review in a Nigerian Bank Setting

A Lagos bank’s digital team holds a sprint review every two weeks. Furthermore, the Head of Digital attends every review session. Also, customers are sometimes invited to give direct feedback on new features. Consequently, the team builds exactly what users need rather than what managers assume.

 

Event 5: The Sprint Retrospective

The Retrospective is the final event of every sprint. Furthermore, it focuses on how the team works — not what they built. Also, it is time-boxed to 45 minutes for every week of sprint length. Consequently, the team improves its process with every single sprint. In short, the Retrospective is Scrum’s most powerful improvement engine.

 

The Three Retrospective Questions

  • What went well? Celebrate wins so the team repeats what worked.
  • What did not go well? Name problems honestly without blame.
  • What will we improve? Commit to one or two specific actions for the next sprint.

 

Why Nigerian Teams Skip Retrospectives and Why They Shouldn’t

Many Nigerian teams skip retrospectives when sprints are stressful. However, that is exactly when a retrospective is most needed.

Also, teams that skip retrospectives repeat the same mistakes forever. Consequently, sprint quality never improves without the retrospective. Therefore, protect the retrospective — even if you shorten everything else.

 

All Five Scrum Events at a Glance

Event When Time Box Who Attends Key Output
Sprint Ongoing 1–4 weeks Whole team Delivered increment
Sprint Planning Start of sprint 2h/sprint week Whole team Sprint goal + backlog
Daily Scrum Every morning 15 minutes Developers Daily sync + blockers
Sprint Review End of sprint 1h/sprint week Team + stakeholders Accepted increment
Retrospective End of sprint 45min/sprint wk Whole team 1–2 improvement actions

 

Free Resource: The Official Scrum Guide

Lagos Data School recommends the Scrum Guide as the definitive free reference for all Scrum events. Furthermore, it explains the purpose, time box, and outputs of every event. Also, it is available free in over thirty languages online.

 

How Lagos Data School Teaches Scrum Events

Lagos Data School runs live Scrum event simulations for Nigerian professionals. Students practise all five events in sprint role-play exercises. Furthermore, every exercise uses real Nigerian project scenarios.

Consequently, graduates run Scrum events confidently from their very first sprint. Visit the Lagos Data School training page to enrol.  Also, see our graduates’ Agile work in the Lagos Data School student portfolio.

 

Frequently Asked Questions

Q1: Can Scrum events be run remotely in Nigeria?

Yes. All five Scrum events work well on Zoom, Google Meet, or Microsoft Teams. Furthermore, tools like Miro and Trello support remote sprint boards and retrospectives. Also, teams in different Nigerian cities run effective remote sprints every day. Therefore, location is never a barrier to running great Scrum events.

 

Q2: What happens if a Daily Scrum is missed?

Missing one daily standup rarely causes a crisis. However, missing standups regularly breaks team alignment quickly. Also, blockers go unreported, and sprint goals are missed more often. Therefore, protect the Daily Scrum even if it is shortened to five minutes.

 

Q3: Who should speak at the Sprint Review?

Every developer demos the work they personally completed. Furthermore, the Product Owner provides context before each demo.

Also, stakeholders are encouraged to ask questions and give live feedback. Consequently, the Sprint Review becomes a real conversation — not a presentation.

 

Master Scrum Events with Lagos Data School

Scrum events create the rhythm that keeps Nigerian teams on track. Furthermore, each event builds on the last to create a full delivery cycle. Lagos Data School trains you to run every Scrum event with skill and confidence.

Visit Lagos Data School and enrol in the Scrum course today.

Scrum Artifacts: Your Complete Guide

Scrum Artifacts Explained for Nigerian Professionals

Scrum defines three artefacts and three artefacts only. Furthermore, each one provides transparency at a different level.

Story pin image

Lagos Data School teaches all three artefacts in its live Scrum course. Therefore, this guide explains every artefact in plain English.

Also, Nigerian project examples are used to make each one real. By the end, you will understand and use all three with confidence.

 

What Is a Scrum Artefact?

A Scrum artefact is a document or output that makes work visible. Furthermore, artefacts reduce guesswork and improve team alignment. Also, they are updated continuously throughout the sprint. Consequently, every team member always sees the current state of work.

According to the Scrum Guide, artefacts create transparency. Therefore, Scrum artefacts are the team’s source of truth.

 

Artefact 1: The Product Backlog

The Product Backlog is an ordered list of all future product work. Furthermore, it contains features, fixes, improvements, and experiments. Also, the Product Owner owns and manages it every day.

Consequently, the backlog always reflects the latest product priorities. In short, the Product Backlog is the single source of all future work.

 

What Goes Into the Product Backlog?

  • User stories: Features written from the user’s point of view.
  • Bug fixes: Known issues that need to be resolved in a future sprint.
  • Technical tasks: Infrastructure, security, or performance improvements.
  • Research spikes: Short investigations needed before a feature can be built.
  • Stakeholder requests: New ideas gathered from sprint reviews or user feedback.

 

How the Product Backlog Is Ordered in Nigerian Teams

The highest-value items always sit at the top of the backlog. Furthermore, the Product Owner uses business value and risk to rank items.

Also, items at the top are detailed and ready to work on.

Consequently, items lower down are less refined and more loosely defined. Therefore, the backlog gets more detailed as items move toward the top.

 

Nigerian Example: Product Backlog for a Lagos Food App

Priority Backlog Item Type Story Points
1 User can search for restaurants by location User Story 5
2 User can add items to a cart User Story 3
3 User can pay with Paystack User Story 8
4 Fix broken image upload on vendor dashboard Bug Fix 2
5 Improve app load time by 30% Tech Task 5
6 Add delivery tracking feature (future sprint) User Story 13

 

Backlog Grooming: Keeping the Backlog Healthy

Backlog grooming is a regular session to keep the backlog clean. Furthermore, it is held one to two days before sprint planning. Also, the Product Owner and team refine, estimate, and re-order items.

Consequently, only clear, ready items enter the sprint planning meeting. Therefore, sprint planning runs faster when the backlog is well-groomed.

 

Artefact 2: The Sprint Backlog

The Sprint Backlog is the team’s plan for the current sprint. Furthermore, it contains three things: the sprint goal, selected backlog items, and tasks.

Also, developers own and update the sprint backlog every day. Consequently, the team always knows what is left to do this sprint. In short, the Sprint Backlog is the team’s daily working plan.

 

How the Sprint Backlog Is Created

First, the Product Owner presents the top backlog items at sprint planning. Also, the team selects items that fit within the sprint’s capacity. Furthermore, each selected item is broken into daily tasks.

Next, each task is assigned to a developer or left for self-selection.

Finally, the sprint backlog is complete and visible on the team’s board.

 

Sprint Backlog vs Product Backlog: Key Differences

Feature Product Backlog Sprint Backlog
Scope All future product work This sprint only
Owner Product Owner Development team
Update rate Continuously — every day Every day during the sprint
Detail level Varies — rough to detailed Fully detailed daily tasks
Change rules Can change anytime Cannot change during the sprint
Nigerian use Roadmap for the whole product Daily task board for the sprint

 

The Sprint Burndown Chart

The sprint burndown chart tracks work remaining in the sprint. Furthermore, it is updated every day by the developers.

Also, a falling burndown line means the team is on track. Consequently, a flat or rising line signals a problem that needs attention. Therefore, review the burndown chart at every Daily Scrum.

 

Artefact 3: The Product Increment

The Increment is the sum of all completed sprint work. Furthermore, it includes work from every previous sprint as well.

Also, each new sprint adds more value to the existing increment. Consequently, the product grows and improves with every sprint cycle. In short, the Increment is the growing, working version of the product.

 

What Is the Definition of Done?

The Definition of Done (DoD) is a shared checklist for completed work. Furthermore, every sprint item must pass the DoD before it counts as done. Also, the team defines the DoD together at the start of the project.

Consequently, quality standards are consistent across every sprint. Therefore, partial or untested work is never counted in the sprint increment.

 

Nigerian Example: Definition of Done for a Lagos Fintech Team

  • Code reviewed: A second developer has reviewed and approved the code.
  • Tests passing: All automated unit and integration tests pass without errors.
  • Security check: The feature has passed a basic OWASP security review.
  • Product Owner accepted: The PO has reviewed and accepted the feature against criteria.
  • Deployed to staging: The feature is live on the staging environment for review.

 

Why the Increment Must Be Potentially Shippable

Every increment must be in a releasable state at sprint end. Furthermore, this does not mean it must be released — only that it could be. Also, a potentially shippable increment gives the Product Owner full control. Consequently, the team releases when the business is ready — not just when the sprint ends. Therefore, quality and completeness are non-negotiable in every Nigerian sprint.

 

All Three Artefacts at a Glance

Artefact Owner Updated When Key Commitment
Product Backlog Product Owner Continuously Product Goal
Sprint Backlog Development Team Every day in the sprint Sprint Goal
Product Increment Development Team End of every sprint Definition of Done

 

Free Resource: The Scrum Guide on Artefacts

Lagos Data School recommends the Scrum Guide for the official definition of all three artefacts. Furthermore, it explains each artefact’s commitment in detail. Also, it is free, short, and easy to read in one sitting.

 

How Lagos Data School Teaches Scrum Artefacts

Lagos Data School covers all three Scrum artefacts in its live course. Students build real product backlogs and sprint backlogs from Nigerian project briefs. Furthermore, they define a custom Definition of Done for every sprint exercise. Consequently, graduates manage all three artefacts correctly from day one.

Visit the Lagos Data School training page to enrol. Also, explore our graduates’ work at the Lagos Data School student portfolio.

 

Frequently Asked Questions

Q1: Who can add items to the Product Backlog?

Anyone can suggest items — stakeholders, developers, or users. However, only the Product Owner decides whether to add them. Also, the PO ranks all accepted items by business value. Therefore, the backlog always reflects the Product Owner’s priorities.

 

Q2: Can the Sprint Backlog change during a sprint?

The sprint goal cannot change once the sprint starts. However, developers can add tasks to the sprint backlog during the sprint. Also, they can remove tasks if they discover a better approach. Therefore, the sprint backlog is flexible in execution but fixed in goal.

 

Q3: What happens if an increment is not done by sprint end?

Incomplete items are returned to the product backlog. Furthermore, they are re-prioritised for a future sprint. Also, they are never counted in the sprint’s velocity. Consequently, the team only claims velocity for truly completed work.

 

Q4: How detailed should a product backlog item be?

Items at the top need full detail and acceptance criteria. However, items further down can be rough and loosely defined. Also, the team refines lower items during backlog grooming sessions. Therefore, only refine items when they are close to the top of the backlog.

 

Master Scrum Artefacts with Lagos Data School

Scrum artefacts make work visible, honest, and accountable. Furthermore, they are the backbone of every great Nigerian Scrum team. Lagos Data School trains you to own, update, and use all three artefacts expertly.

Visit Lagos Data School and start your Scrum journey today.

Hi, How Can We Help You?
Welcome To
Lagos Data School

Artificial Intelligence (AI), Machine Learning and Robotics Programmes Are Now Available!!!

Enroll Now!

Thank You
100% secure website.