TDD : Most Suitable Scenarios

Having said in the previous blog on TDD : Test Driven Development  now we know the recipe and it’s time understand when to cook this food.

 Points are bulleted as below: 

• When the product is complex 
• Product having lot of dependencies
• When you want to sell your product
• Frequent releases
• Very short development cycle
• Winning the trust from Client
• Agile development
• Enhancing or migrating your legacy code
• When the development is happening on a matured product
• When the emphasis is more on quality than delivering much functionality
• Deadlines are not very much aggressive .
•  Availability of sufficient number of resources
• When you want reduced risk in the Production environment
• Requirements are clear
• When we want more attention to Design  
• Relying more on Continues Integration
• Parallel distributed development
• Large Teams 
• Designing robust software components
• More clarity from the Product management 
•  Suffiicient Test coverage
• Automated regression

I hope things are very much clear now and many of the points above are self explanatory. TDD is followed in most of the big companies like Google, Facebook, Yahoo.
 With this we should be fairly confident in taking decisions in going with TDD which says  'SPECIFY FIRST'.