Accepted Agile Practices

Recently found this list on the web of accepted agile practices.

Just scanning through the items, it amazes me how many I’ve actually used on projects that I’ve worked on.

Which ones are you using?

• Retrospective
• Prioritized product backlog
• Embracing changing requirements
• “Just-in-time” requirements elaboration
• Planning Game/Planning Poker
• 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 meeting (Scrum)
• 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 (YAGNI), Once And Only Once, Simplify Vigorously)
• Unit Test-driven development (TDD)
• 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 standards
• Code inspections
• “Complete” feature testing done during iteration
• Exploratory Testing
• Behavior-driven Development (BDD)