Explosion of Agile Practices
Wow I had not realized that people now name over 50 practices as Agile Practices. (I don’t think they are all at the same level. But itsĀ fascinatingĀ to see this list.)
- Retrospective
- Prioritized product backlog
- Embracing changing requirements
- “Just-in-time” requirements elaboration
- Planning Game
- Kanban
- Small teams (12 people or less)
- Team documentation focuses on decisions rather than planning
- Onsite customer (Daily customer/product manager involvement)
- Short iterations (30 days or less)
- “Potentially shippable” features at the end of each iteration
- Stabilization iterations
- Iteration reviews/demos
- Team velocity
- Time-boxing
- Requirements written as informal User Stories
- Synchronous communication (face-to-face, video conference, conference call, instant messaging)
- “Done” criteria
- “Whole” multidisciplinary team with one goal
- Energized Work
- Sustainable pace
- Sit-together or Co-located team
- Release planning
- Informative Workspace (Information Radiators, Big Visible Charts [Burndown Charts, Pair Stairs])
- Stand up/Scrum meeting
- Features in iteration are customer-visible/customer valued
- Task planning
- Automation
- Emergent design
- System Metaphor
- Simple Design (Do Simple Things, You Aren’t Gonna Need It, Once And Only Once, Simplify Vigorously)
- Unit-Test-driven development
- Acceptance Test-driven development
- Collective code ownership
- Continuous Integration
- Continuous Deployment
- Design inspections
- Ten minute build
- Refactoring
- Configuration management
- Single Click Deploy
- Pair programming
- Coding standard
- Code inspections
- “Complete” feature testing done during iteration
- Exploratory Testing