Agile is on great advance, more and more organisations and teams adopting it. But what is it exactly? And how do you become agile?
In this book I want to show how is possible to introduce gradually a series of changes so that at the end your organisation will be agile (i.e., it has understood the Agile values and principles and know how to apply them), not only does some kind of Agile practices.
Through examples you can see how to introduce and tailor the Agile principles, week after week: in 8 weeks we took a team with no prior experience of Agile into changing its mentality and attitude.
I hope this journey can help your team (and further: the entire organisation) to do a similar one toward the same goal: being Agile.
The examples show which are the general principles and why / when they make sense, so you will be able to inspect your situation, adapt these principles (as needed) and adopt them, finally repeating this cycle continuously.
Build your method up, don’t tailor it down.
Finally, this book is about agility as values system, culture, mind-set, and not about a specific process or methodology. All the currently most used methodologies – Scrum, Lean and Kanban – will be described, each one with its advantages and disadvantages.
The book contains revised versions of the posts published here (see below the list) in the past plus several brand new chapters (about Kanban, how to scale Agile and many examples of retrospectives for each topic introduced every week).
Here are my posts about agile project management:
- The problem with the waterfall model
- The agile manifesto and a brief history
- When agile and when waterfall?
- Benefits of an iterative development
- An introduction to Scrum
- An introduction to Lean
- Week1: the frequent meeting
- Week1: the Product Owner
- Week2: the requirements list aka the backlog
- Week2: an example of backlog
- Week3: iterations
- Retrospective of the daily meetings
- Example of retrospective format
- The agile team and its roles
- The agile team as cross-disciplinary
- The agile team as self organising
- The team collocated
- The iteration kick-off and the planning meeting
- The iteration backlog and the Definition of Done
- More about acceptance tests
- Estimating the tasks
- Velocity and burn-down chart