| Source Code: Do you use source control? |
Build: Can you build in a single step? |
Daily Build: Do you make daily builds? |
Bug DB: Do you have a bug database? |
Fixing: Do you fix bugs before writing new code? |
Sched: Do you have an up-to-date schedule? |
Spec: Do you have a spec? |
Quiet: Do programmers have quiet working conditions? |
Tools: Do you use the best tools money can buy? |
Testers: Do you have testers? |
Intervew: Do new candidates write code during their interview? |
Hallway: Do you do hallway usability testing? |
Wiki: Do you use a Wiki? |
Continuous: Do you do continuous build / test / deploy? |
TDDev: Do your tests drive your development? |
Pair: Do your developers pair and support each other? |
Talk: Does everyone talk to each other, constantly? |
Hiring: Does the team select its new members? |
Colocated: Is the team colocated? |
Testing: Can you test in a single step? |
Releases: Have you delivered running, tested, usable functionality to users at least twice in the last six months? |
Deploy: Can you deploy in a single step? |
Integration: Do you integrate the system at least twice per week` |
News: Can you give your boss bad news? |
Access: Does it take less than three days from when you have a question to when an expert answers it? |
Improvement: Did you get together within the last three months to discuss and improve your group’s working habits? |
Retrospective: Does you team conduct a retrospective after every iteration? |
User Stories: Do you define the product in terms of user stories? |
Acceptence: Do you define acceptence tests before you write code? |
| Source Code: Do you use source control? |
Build: Can you build in a single step? |
Daily Build: Do you make daily builds? |
Bug DB: Do you have a bug database? |
Fixing: Do you fix bugs before writing new code? |
Sched: Do you have an up-to-date schedule? |
Spec: Do you have a spec? |
Quiet: Do programmers have quiet working conditions? |
Tools: Do you use the best tools money can buy? |
Testers: Do you have testers? |
Intervew: Do new candidates write code during their interview? |
Hallway: Do you do hallway usability testing? |
Wiki: Do you use a Wiki? |
Continuous: Do you do continuous build / test / deploy? |
TDDev: Do your tests drive your development? |
Pair: Do your developers pair and support each other? |
Talk: Does everyone talk to each other, constantly? |
Hiring: Does the team select its new members? |
Colocated: Is the team colocated? |
Testing: Can you test in a single step? |
Releases: Have you delivered running, tested, usable functionality to users at least twice in the last six months? |
Deploy: Can you deploy in a single step? |
Integration: Do you integrate the system at least twice per week` |
News: Can you give your boss bad news? |
Access: Does it take less than three days from when you have a question to when an expert answers it? |
Improvement: Did you get together within the last three months to discuss and improve your group’s working habits? |
Retrospective: Does you team conduct a retrospective after every iteration? |
User Stories: Do you define the product in terms of user stories? |
Acceptence: Do you define acceptence tests before you write code? |
