Chapter 10. Measuring your team against the agile principles

 

This chapter covers

  • Breaking down the agile principles into measurable pieces
  • Applying the techniques in this book to the agile principles
  • Associating metrics with the agile principles
  • Measuring your team’s adherence to the agile principles

If you ask the CIOs of most Fortune 500 companies if their teams are practicing agile development, they’ll probably all say yes. If you sit on any of the development teams in those companies, you’ll notice that they operate differently to varying degrees. That’s okay; in fact, one of the great things about agile development frameworks is that they allow development teams to move quickly in their own context.

Often as teams evolve their agile development processes they’ll start to question their agility. One way to combat this is to measure your team against the agile principles themselves.

Because we’re talking about continuous improvement in the scope of agile software projects, it seems fitting to complete this book by talking about measuring your project and team against the agile principles. Using the concepts we’ve talked about in this book, we’ll break down the agile principles and show you what to use to measure your team against each one.

10.1. Breaking the agile principles into measurable components

 
 

10.2. Three principles for effective software

 
 
 

10.3. Four principles for effective process

 
 

10.4. Four principles for an effective team

 
 
 
 

10.5. One principle for effective requirements

 
 
 
 

10.6. Case study: a new agile team

 
 

10.7. Summary

 
sitemap

Unable to load book!

The book could not be loaded.

(try again in a couple of minutes)

manning.com homepage