Chapter 1
The Agile mindset
Agile is a way of delivering work in short cycles, learning from feedback and adapting. The Agile Manifesto (2001) prefers individuals and interactions over processes and tools, working products over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
- Deliver value early and often
- Welcome changing requirements, even late
- Work at a sustainable pace
- Reflect regularly and improve
Key takeaway: Agile is about value, feedback and adaptation — not about skipping planning.
Chapter 2
Scrum roles
Scrum is the most widely used Agile framework. A Scrum Team has three accountabilities working together as one cross-functional, self-managing unit.
- Product Owner — maximises value and orders the Product Backlog
- Scrum Master — servant-leader who coaches the team and removes impediments
- Developers — build a usable Increment every Sprint and own the Sprint Backlog
Key takeaway: No one in Scrum is a traditional boss assigning tasks; the team decides how to do the work.
Chapter 3
Scrum events and artifacts
Work happens in Sprints: fixed timeboxes of one month or less. Each Sprint contains Sprint Planning (agree the Sprint Goal and plan), the Daily Scrum (15 minutes to inspect progress toward the goal), the Sprint Review (inspect the result with stakeholders) and the Sprint Retrospective (improve how the team works).
- Product Backlog — the ordered list of everything the product may need
- Sprint Backlog — the Sprint Goal plus the plan to reach it
- Increment — the usable result that meets the Definition of Done
Key takeaway: The Definition of Done is the shared quality bar; work that does not meet it is not part of the Increment.
Chapter 4
Kanban and flow
Kanban visualises work on a board and limits work in progress (WIP). When a column reaches its WIP limit, the team stops starting and starts finishing, which exposes bottlenecks.
- Visualise every stage of the workflow
- Limit WIP to improve flow
- Measure cycle time (start to finish) and throughput
- Improve the process step by step
Key takeaway: Stop starting, start finishing.
Chapter 5
User stories, estimation and prioritisation
A user story describes value from the user’s point of view: “As a <user>, I want <goal> so that <benefit>.” Good stories follow INVEST: Independent, Negotiable, Valuable, Estimable, Small and Testable. Large stories should be split into thin slices that each deliver value.
- Story points estimate relative effort, not hours
- Planning Poker avoids anchoring by revealing estimates together
- Velocity helps one team forecast — never compare teams with it
- MoSCoW: Must, Should, Could, Won’t have this time
Key takeaway: Small, valuable stories are easier to estimate, test and deliver.
Chapter 6
Delivery, metrics and scaling
Agile teams deliver small working increments frequently, often starting with a Minimum Viable Product (MVP) to learn from real users. Burndown charts show remaining work; retrospectives turn lessons into improvements. When many teams work on one product, frameworks such as SAFe, LeSS or Scrum@Scale coordinate them.
- Release early to reduce risk
- Keep retrospectives safe and blame-free
- Use metrics to learn, not to punish
- Scale only after single teams work well
Key takeaway: Frequent delivery plus honest reflection is the engine of Agile improvement.