- A Fable About Trust
  - Trust Driven Development
  - Back to the Mechanic
  - Project Zen
  - Where to?
I Before You Start
- 1. What is a Project?
  - 1.1 What is “Process”
- 2. Who are the Players?
- 3. What do I Need Before I Start?
  - 3.1 Sharing Knowledge
  - 3.2 What to Share?
- 4. What prevents sharing?
- 5. What do First Meetings Look Like?
  - 5.1 Getting the initial feature list
  - 5.2 Workflows
- 6. Initial Estimates
  - 6.1 Let’s talk about #NoEstimates
  - 6.2 Making story lists and estimates
  - 6.3 Converting the list to something resembling an estimate
- 7. What do Clients Need To Know?
  - 7.1 Okay, so what’s the problem…
- 8. Iteration Zero
  - 8.1 Setting up Environments, Continuous Integration, and Continuous Deployment
  - 8.2 Team Agreements
  - 8.3 Spikes and Technology decisions
II Iteration Heartbeat
- 9. Iterations
  - 9.1 What’s an iteration?
  - 9.2 Why Iterations?
  - 9.3 What happens in an iteration?
  - 9.4 How long should an iteration be?
  - 9.5 A Quick Plea About Days of the Week
  - 9.6 The Iteration Planning Meeting
  - 9.7 Iteration process smells
  - 9.8 When don’t I need iterations?
  - 9.9 When should I worry?
- 10. Retrospectives
  - 10.1 When
  - 10.2 Who
  - 10.3 How
- 11. Where Do Stories Come from?
  - 11.1 What makes a story?
  - 11.2 Lifecycle of a story
- 12. Estimation and Velocity
  - 12.1 The Rules
  - 12.2 Why Estimate?
  - 12.3 What are you estimating?
  - 12.4 One Plus One Equals Three, or Point Math
  - 12.5 Validating Estimates
  - 12.6 Estimation in Context, or Estimation in Conflict
  - 12.7 Should You Estimate Bugs?
  - 12.8 Why does this work?
- 13. Responding to Change
  - 13.1 What’s a change?
III Daily Heartbeat
- 14. Daily Stand Up
  - 14.1 Build A Better Standup
  - 14.2 Date and Time
  - 14.3 Who attends?
  - 14.4 The Virtual Standup
- 15. Doing The Work
- 16. Pair Programming vs Code Review
  - 16.1 Effective Pairing
  - 16.2 Code Review
  - 16.3 Code standards and documentation
- 17. Remote Work
  - 17.1 Set up communication early
  - 17.2 Conway’s Law, Remote Teams, and You
  - 17.3 Split Sites
  - 17.4 Remote Meetings
  - 17.5 When Not To Remote
- 18. Release Management
  - 18.1 Code Freeze
  - 18.2 Release cutover
  - 18.3 Staging “plus”
  - 18.4 Feature block
  - 18.5 When to deploy?
- 19. Testing
- 20. When to Deploy to Stage
- 21. When to Deploy to Production
- 22. Bugs
  - 22.1 Building Trust Before Bugs Happen
  - 22.2 Building Trust When Bugs Happen
  - 22.3 Fixing Bugs
  - 22.4 Bug or Feature?
  - 22.5 Flavors of bugs
  - 22.6 When Bugs Get Serious
IV Crunch Time
- 23. Crunch Time
  - 23.1 The End Game
  - 23.2 Attention Must Be Paid
  - 23.3 Deadlines
  - 23.4 End Game Review
  - 23.5 Code Freeze is never a freeze
  - 23.6 One More Thing
  - 23.7 Continuous Crunch
  - 23.8 Plan for the End
- 24. Responding To Problems
- 25. I made a mistake
- 26. Professionalism in a Hostile Environment
  - 26.1 I think what you are doing is a bad idea
  - 26.2 The project keeps changing
  - 26.3 Scope Creep
  - 26.4 The client has unreasonable time and scope expectations
  - 26.5 I way underestimated this feature/project
  - 26.6 People on this project are not executing
  - 26.7 I don’t have agency, the team is too big
  - 26.8 I’m having personal issues with the client
  - 26.9 The client hates what they said they wanted
V End of Life
- 27. End of Life
- Colophon
- Acknowledgements
- Changelog
Notes

About

Authors

Author Support

More

Legal