1. Brian Wernham e-Government and Gateway reviews: Waterfall biased or Agile ready? brian.wernham@gmail.com @BrianUkulele Click here for delegates discount Presented at the Baltic PM Days Conference on May 9, 2014

2. How to bring in an innovative solution On cost On time How to develop battle hardware, not just software How to work collaboratively with suppliers whilst maintaining formal contractual targets http://bit.ly/About-Brian @BrianUkulele 2 Part I – Agile Defence?

3. A story of working together with the US and our closest European allies… http://bit.ly/About-Brian @BrianUkulele 3

4. The French… 4

5. The Italians… 5

6. The Germans… 6

7. Who is who? Blue = friendly Red = enemy White = neutral http://bit.ly/About-Brian @BrianUkulele 7

8. Rising problem from faster, more lethal and more accurate weapons… Blue-on-Blue incidents Friendly Fire Fratricide Collateral damage http://bit.ly/About-Brian @BrianUkulele 8

9. Some instances of friendly fire in Afghanistan… Tarnak Farm 18 April 2002 four Canadian soldiers were killed by U.S. laser-guided bomb. A former professional American football player, was shot and killed by American fire in 22 April 2004. On 6 April 2006, UK forces called in a US airstrike - wounded 13 Afghan police officers and killed one. An RAF Harrier mistakenly strafed British troops on 20 August 2006. 9

10. http://bit.ly/About-Brian The UK Ministry of Defence decided on: Agile approach… Fix timescale/budget Flexible scope Incremental delivery Interdisciplinary teams … within a DSDM project Framework Formal requirements management Formal roles and project governance Controlled architecture … 120 staff to be trained Developers Project Board Auditors Subcontractors Procurement staff 10

11. Comments from the training/ coaching: When you encounter choppy waters will you finger point or collaborate? Collaboration & Control NOT Command and control Requirements trading crucial: Foundations phase re-baselined the contract At start of every Spiral Iteration http://bit.ly/About-Brian @BrianUkulele 11

12. MoSCoW - Prioritised Requirements List Must haves Should haves Could haves Wont haves Allows for crucial Requirements trading: Foundations phase re-baselined the contract Changed at start of every Spiral Iteration http://bit.ly/About-Brian @BrianUkulele 12

13. DSDM Roles on the CIDS = Governance + Delegation 13

14. DSDM inverts the normal project management paradigm… 14

15. The results were proven in battlefield testing… Tech Readiness Level 6: UK Battlespace Laboratory End of each 3–6 months Spiral Final test 50+ battlefield positions Immoveable deadlines ensured use of Battlefield Laboratory on expected dates Tech Readiness Level 7: unscheduled trial in Norway August 2010 Interoperability of UK and US CIDS systems proven Danish aircraft arrived without prep and immediately able to use Link 16 Ground and air 3 second response time/5 metre accuracy Tech Readiness Level 8: Bold Quest 2011 Full coalition interoperability testing http://bit.ly/About-Brian @BrianUkulele 15

16. Lessons learned Clear Priorities BUT: they change as the project progresses Iterate delivery Timebox work Delegate responsibility Have clear roles Trade requirements Ruthlessly sacrifice scope http://bit.ly/About-Brian @BrianUkulele 16

18. Part II – Agile Assurance? What are Gateway reviews? What is Agile? Can a Gated approach be used to assure Agile projects? … and what about complex change programmes? http://bit.ly/About-Brian @BrianUkulele 18

19. Waterfall projects drive a waterfall assurance approach… Design Build Test Deploy White box Assurance P Level Process Assurance

20. Gateway reviews – as interpreted for waterfall projects http://bit.ly/About-Brian @BrianUkulele 20 Acronyms: - Strategic Outline Case (SOC) - Outline Business Case (OBC) - Full Business Case (FBC) Source: Welsh Government 2012

21. What does an Agile project look like: - a governance perspective 21

22. Examples of Agile Methods - A project level method: DSDM 22 Source: DSDM Consortium (DSDM = Driving Strategy, Delivering More)

23. Examples of Agile Methods - A team level method: Scrum 23 Source: Mike Cohn

24. Agile projects invert the iron- triangle: 24 Source: DSDM Consortium

25. Dont be slaves to process! 25

26. Be outcome focussed: 26

27. O for Outcome Assurance… 27 P Level Process Assurance

28. Taking an appropriate assurance approach… 28 Design Build Test Deploy White box Assurance

29. Hybrid Gate Assurance? http://bit.ly/About-Brian @BrianUkulele 29 Project Programme Gateway Reviews Strategic Assessment Initial Gate O Annual O Gates Gates 1-5 repeated for each project Gate 0 repeated annually P level Process Assurance O Level Outcome Assurance Programme Close O Gate Source: Welsh Government 2012 – amended to correctly show iterative Gates O

30. Managing and assuring agile/waterfall hybrid change programmes – my recent article… http://bit.ly/About-Brian @BrianUkulele

31. brian.wernham@gmail.com Blog: brianwernham.wordpress.com @BrianUkulele http://bit.ly/About-Brian Thanks for listening! 31 Click here for delegates discount