Invite collaborators by email, take a guided tour of our application and look closely at your developers’ commits

Code churn is regarded by many software engineers as the best indicator of a code’s quality and defect density. Most engineers will also agree that code churn is good or bad relative to when and why it is taking place. But it is worth understanding in detail because it is 100x less costly to catch a defect during the design phase than catching it during maintenance.

Reducing cycle time is probably the holy grail of software development. If you’re improving it, reducing it, you’re likely improving everything that feeds into it. Cycle time is so important that it actually is worth obsessing about.