Agile and Scrum Fundamentals
What Does "Agile" Actually Mean?
Agile is a way of building products in small, fast cycles instead of one long, rigid plan. Rather than spending a year designing the "perfect" product and hoping customers like it, agile teams build a small piece, ship it, watch how customers respond, and adjust. It trades certainty up front for speed and the ability to change direction.
Agile started in 2001 when a group of software developers wrote the Agile Manifesto, which values:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
None of the items on the right are worthless — documentation, tools, and plans all matter. The manifesto simply says that when they conflict with the items on the left, the left wins.
Why Fintechs and Banks Both Care
A company like Paystack or Moniepoint ships small, frequent updates to their dashboards and APIs because merchants notice friction immediately and switch to a competitor like Flutterwave within days. A traditional bank like Access Bank, on the other hand, historically ran big annual release cycles for its mobile app — and has been moving toward agile squads precisely because customers now expect the same fast iteration they get from fintech apps. Agile is not just a "startup" thing; it is how any team competing for the same customer attention has to operate.
Scrum vs Kanban
Agile is a philosophy; Scrum and Kanban are two popular frameworks that put it into practice.
| Scrum | Kanban | |
|---|---|---|
| Rhythm | Fixed-length sprints (usually 1-2 weeks) | Continuous flow, no fixed cycle |
| Planning | Plan a batch of work at the start of each sprint | Pull the next item whenever capacity frees up |
| Best for | Teams shipping planned features (e.g. a new savings product at a bank) | Teams handling unpredictable work (e.g. support engineering, incident response) |
| Key limit | Sprint length and sprint backlog | Work-in-progress (WIP) limits per column |
| Roles | Product Owner, Scrum Master, Development Team | No mandated roles |
Many teams — including product squads at companies like Konga and Spotify — blend the two: sprint cadence for planning and reporting, kanban-style boards for visualizing where each ticket sits.
The Scrum Ceremonies
Scrum organizes work around a small set of recurring meetings, all designed to keep the team aligned without excessive overhead:
- Sprint Planning — the team agrees what will be built in the upcoming sprint.
- Daily Standup — a 10-15 minute check-in on progress and blockers.
- Sprint Review (Demo) — the team shows finished work to stakeholders.
- Sprint Retrospective — the team reflects on how the sprint went and what to improve.
Amazon's product teams, for example, run rapid two-week sprints paired with a strict "working backwards" document process before a project even starts — proof that even a company famous for long-range planning still relies on short, iterative execution cycles underneath.
The PM's Job in an Agile Team
The PM (often called the Product Owner in Scrum) owns the what and why: maintaining the backlog, setting priorities, and making sure the team is building the highest-value thing next. The Scrum Master owns the how the team works: removing blockers and protecting the team's focus. Confusing these two roles is one of the most common reasons agile teams stall.
Try it yourself
Key Takeaways
- Agile favors small, fast iterations over long, rigid plans, prioritizing working software and responding to change.
- Scrum uses fixed-length sprints for planned, batchable work; Kanban uses continuous flow for unpredictable work.
- Scrum's core ceremonies are Sprint Planning, Daily Standup, Sprint Review, and Sprint Retrospective.
- Fintechs like Paystack and Moniepoint, and banks like Access Bank, both rely on agile cycles to keep pace with customer expectations.
- The Product Owner (often the PM) owns backlog priorities; the Scrum Master owns how the team works.
Quick Quiz
1.According to the Agile Manifesto, which of these is valued MORE than its counterpart (though the counterpart still matters)?
2.A support engineering team receives unpredictable tickets throughout the day and needs to pull the next item as soon as capacity frees up. Which framework fits best?
3.In Scrum, who is primarily responsible for maintaining the backlog and deciding what gets built next?
Ready to go further?
CareerEx gives you structured 12-week training, live classes every Saturday and Sunday, real tutor feedback, and a certificate. Join the next cohort.
Join CareerEx