I know that a team is on the right track when they:

• deliver on the majority of their commitments each iteration, and at most a portion of one story is incomplete at the end of an iteration
• deliver stories every 1-3 days, on average, throughout an iteration
• can tell you relevant statistics about the code base, for example, how many unit tests are there and how long they take to run
• commit to improvement, and deliver on that commitment, without having to be told--they just do it
• don't fear open conflict
• can be seen talking about the code

What other indicators do you have?

posted by Jeff L.  # 9/09/2008 12:19:00 PM Database TDD Blogs