Traditionally, we decompose tasks and measure completion This is the cost accounting tradition Alternatively, we account for customer value incrementally delivered This is the Lean Manufacturing and Theory of Constraints model Work Down Remaining Work Plan Task 1 Task 2 Task 3 Task 4 Value Value Up
Test rates (pass, inconclusive, fail) shown in bars Against code coverage, … code churn, … and active bugs
Happy families are all alike; every unhappy family is unhappy in its own way. Tolstoy, Anna Karenina Все счастливые семьи похожи друг на друга, каждая несчастливая семья несчастлива по-своему.
Underestimating Uneven Task Decomposition Solution Stuck in Testing Development Practices Too Loose Inadequate Unit Testing Tests Passing; Solution Doesn’t Work Too Little Testing Build Failures Scope Creep Resource Leaks
Steady rates of progress, but slope too shallow Slow progress leading to cuts in planned work, but not enough cuts
Bulge in resolved → Insufficient resources or inadequate quality from dev Bulge in resolved → Insufficient resources or inadequate quality from dev
TFS 2008 SP1 25 instances in Production 15,761 Active Users in last 7 days 3,004 Team Projects TFS 2008 SP1 Usage Statistics 3,253,657 Work Items(1.3M 2/08) 54,212,547 Source Files(29.3M 2/08) 706,957 Team Builds (95K 2/08) TFS 2010 Internal Release 3 instances in Production running early Rosario bits 1,175 Active Users in last 7 days 15 Team Projects Microsoft Developer Division, Office, & Windows dogfooding Rosario since April 2007 Rosario Usage Statistics 216,899 Work Items(114K 2/08)