“…For clarification, Table 4 shows a compilation of practices which have been categorised as having only lean origins [5]. Table 4 Lean (only) Software Development Practices Jidoka (build quality in) [6] Poka-Yoke (Defect detection and prevention) [9] Kano analysis to link voice of the customer to requirements [40], [41] Quality Function Deployment [41] Value Stream Mapping [8], [6], [27], [42] Transparency [8] Make project status highly visible Visualise all work items Limit WIP (Work in Process), [43], [31] Workload levelling "Heijunka" [6], [40] Addressing bottlenecks [6], [44,45], [40], [27] Deferring decision making [38], [27] Moving variability downstream [27] Reducing slack [22] Measure and manage [46] Employ Queuing Theory [25], [44,45] but measure the right things [11] Employing Pull systems Kanban, Limitied WIP, CONWIP (Sugimori et al, 1977;Bradley, 2007; Kniberg and Skarin, 2010), [31] Batch control processing [47], [11] Value stream Kaikaku [8] Relentless reflection "Hansei" and continuous improvement "Kaizen" [6], [28],…”