Lean Principle “See the whole”

The remaining work report showed a clear buildup in items that were “Ready to Test” indicating a bottleneck somewhere in the process. I was wondering what was going on… I was under the assumption that the tester did not have any time to test these items (he had some work with existing customers who had to generate some kind of annual reports, so I was waiting for this surge to end). But after asking the tester what was going on he was quite surprised and responded that he only had 12 items that were ready to test instead of the more than 40 shown in the report. After some asking around the root cause of the problem was that the development team did not release a version to the test environment yet so the tester was not able to test the other items.

This example clearly shows that the reporting help you in making bottlenecks visible. However they don’t show you exactly what the root cause is. You always have to keep in mind to See the Whole.

Product Backlog Pareto

Pareto analysis on Product Backlog Items and Bugs

This report helps you analyze the “health” of your backlog for more information:Implementing Lean Software Development: From Concept to Cash (page 170).

Average Cycle Time of Workitems

Find below a query that shows the average Cycle Time per state, you can store the results in a temporary table and join it to provide averages to help in value stream mapping.

 

Cycle Time Per Sprint

The bulk of the work is done by the query below

   1:  WITH cteStateChange(rowId, tpId, wiId, [State], PrevState, UpdTime) AS(

   2:      SELECT Row_Number() OVER(Order by wi.TeamProjectSK, wi.System_id, wi.System_Rev) 

   3:          , wi.TeamProjectSK

   4:          , wi.System_Id

   5:          , wi.System_State

   6:          , wi.PreviousState 

   7:          , wi.System_ChangedDate

   8:      FROM dbo.DimWorkItem wi

   9:      INNER JOIN dbo.FactWorkItemHistory wih

  10:          ON wih.WorkItemSK = wi.WorkItemSK

  11:          AND wih.TeamProjectSK = wi.TeamProjectSK

  12:      WHERE 1=1

  13:      AND (wih.StateChangeCount = 1)

  14:  )