1. Lean Software Management: BBC Worldwide Case Study Dr Peter Middleton MBA PeterJonMiddleton@gmail.com 13 th June 2014 IASA Ireland, Dublin Irish Computer Society

2. IASA 1.Business Technology Strategy 2.IT Environment 3.Quality Attributes 4.Design 5.Human Dynamics

3. Volume + Constant change Requirements / Budgets / Business Sponsors Users Hardware / Networks Database Software Staff skills and availability Culture / Privacy / Legal / Learning

4. UK Government advice PRINCE2: ‘Ensuring that the information required for the project team is available.’

5. BBC Worldwide Digital Hub Software Team Waterfall Agile Lean London 9 staff: Analyst, Architect, QA, Developers Operating cost: £1.5m p.a. C#,.NET, MS SQL Server RISK

7. Lean Software – key ideas Reduce Work in Process: –Minimum Marketable Feature –Analysis / Specifications –Design –Untested code Reduce total end to end time –Visible management & less risk –Flexibility

9. BBC

10. Lead time to customers -37% Variance -47%

11. Throughput: smaller, incremental deliveries

12. Fewer Bugs: -24%; Variance: -33%

13. Possible problems 1.Space needed for Kanban & info boards 2.Plan driven, document centric process 3.Poor fit with standardised reporting 4.Remit of IT – upstream & downstream 5.Command & control compliance model 6.Staff initiative and multi skilling Lean handles risk by low WIP, transparency, small units & frequent deliverables

14. Conclusion Lean provides discipline and agility Software under quantitative control Frequent, small, high value deliverables Experiments to demonstrate: –End to end time measure –Work in Progress – white board & post notes Lean Software Management: BBC Worldwide Case Study, P. Middleton & D. Joyce, IEEE Trans. on Engineering Management

15. Continual Improvement Days lost: -81% 26 to 5 days

16. Development Time -73%; Variation -78%

17. Differences Agile and Lean Batch / Push versus Pull –Time-boxed iterations Reliance on Data –Focus on people Continual Improvement – ‘impediment list’ / ‘improvement backlog’‘ Multi skilling –Velocity’, features, story points

18. Engineering Practices Decoupling – improve legacy code Test Driven Development (unit tests) Automated Acceptance Testing Source Control Software Bug tracking software Daily Stand Up (15 minutes)

19. Follow up to the IEEE article http://leanandkanban.wordpress.com/2011 /04/09/lean-software-management-bbc- worldwide-case-study/ http://leanandkanban.wordpress.com/2011 /04/09/lean-software-management-bbc- worldwide-case-study/ http://leankitkanban.com/ (lean tool)http://leankitkanban.com/ peterjonmiddleton@gmail.com dpjoyce@googlemail.com Twitter: @dpjoyce