-
CH1 LEARNING AGILE
- What is Agile?
- Who should read this book?
- Our goals for this book
- Getting Agile into your brain by any means necessary
- how this book is structured?
-
CH2 UNDERSTANDING AGILE VALUES
- A team lead, architect, and project manager walk into a bar...
- No silver bullet
-
Agile to the rescue! (Right?)
- Adding Agile makes a difference
- "Better-Than-Not-Doing-It" Results
-
A fractured perspective
- How a fractured perspective causes project problems?
- Why does a fractured perspective lead to just Better-Than-Not-Doing -It results?
-
The Agile Manifesto helps teams see the purpose behind each practice
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
- Principle over practices
-
Understanding the Elephant
- Methodologies help you get it all in place at once
- Where to start with a new methodology
-
CH3 THE AGILE PRINCIPLES
- The 12 principles of Agile software
- The Customer is always right...right?
- Delivering the project
- communicating and working together
- Project Execution - Moving the project along
- Constantly improving the project and the team
- The Agile project : Bringing all the principles together
-
CH4 SCRUM and SELF-ORGANIZING TEAMS
- THe rules of Scrum
- Act I : I can Haz Scrum?
- Everyone on a Scrum team owns the project
- Act II : Status updates are for social networks!
- The whole team uses the Daily Scrum
- Act III : Sprinting into a wall
- Sprints, Planning, and Retrospectives
- Act IV : Dog catches Car
- CH5 SCRUM PLANNING and COLLECTIVE COMMITMENT
- CH6 XP and EMBRACING CHANGE
- CH7 XP, SIMPLICITY, and INCREMENTAL DESIGN
- CH8 LEAN, ELIMINATING WASTE, and SEEING THE WHOLE
- CH9 KANBAN, FLOW, and CONSTANTLY IMPROVING
- CH10 THE AGILE COACH