brian wernham e-government and gateway reviews: waterfall biased or agile ready?...
TRANSCRIPT
Brian Wernham
e-Government and Gateway reviews: Waterfall biased or Agile ready?
[email protected]@BrianUkulele
Click here for
delegates’ discount
Presented at the Baltic PM Days Conference
on May 9, 2014
2
How to bring in an innovative solutionOn cost On time
How to develop battle hardware, not just software
How towork collaboratively with supplierswhilst maintaining formal contractual targets
http://bit.ly/About-Brian@BrianUkulele
Part I – Agile Defence?
3
A story of working together with the US and our closest European allies…
http://bit.ly/About-Brian@BrianUkulele
4
The French…
5
The Italians…
6
The Germans…
7
Who is who?
Blue = friendly Red = enemy White = neutral
http://bit.ly/About-Brian@BrianUkulele
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
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.
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
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 contractAt start of every Spiral Iteration
http://bit.ly/About-Brian@BrianUkulele
12
MoSCoW - Prioritised Requirements List
Must haves Should haves Could haves Won’t haves
Allows for crucial ‘Requirements trading’: ‘Foundations phase’ re-baselined the contractChanged at start of every Spiral Iteration
http://bit.ly/About-Brian@BrianUkulele
13
DSDM Roles on the CIDS= Governance + Delegation
14
DSDM inverts the normal project management paradigm…
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
16
Lessons learnedClear PrioritiesBUT: they change as the project progresses
Iterate deliveryTimebox workDelegate responsibilityHave clear rolesTrade requirements
Ruthlessly sacrifice scope
http://bit.ly/About-Brian@BrianUkulele
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
Waterfall projects drive a waterfall assurance approach…
TraditionalProject
Design
Build
Test
Deploy
White boxAssurance
‘P’ LevelProcess
Assurance
20
Gateway reviews – as interpreted for waterfall projects
http://bit.ly/About-Brian@BrianUkulele
Acronyms:- Strategic Outline Case (SOC)- Outline Business Case (OBC)- Full Business Case (FBC)
Source: Welsh Government 2012
What does an ‘Agile’ project look like:- a governance perspective
21
Innovationproject
P/type
P/type
P/type
P/type
22
Examples of Agile Methods- A project level method: ‘DSDM’
Source: DSDM Consortium (DSDM = Driving Strategy, Delivering More)
23
Examples of Agile Methods- A team level method: ‘Scrum’
Source: Mike Cohn
‘Agile’ projects invert the ‘iron-triangle’:
24Source: DSDM Consortium
25
Don’t be slaves to process!
26
Be outcome focussed:
27
‘O’ for Outcome Assurance…
‘P’ LevelProcess
Assurance
Taking an appropriate assurance approach…
28
TraditionalProject
Innovationproject
HybridProgramme
Design
Build
Test
Deploy
P/type
P/type
P/type
P/type
White boxAssurance
HybridAssurance
Black boxAssurance
InnovationProject
InnovationProject
TraditionalProject
TraditionalProject
29
Hybrid Gate Assurance?
http://bit.ly/About-Brian @BrianUkulele
Project
Programme Gateway Reviews
Str
ate
gic
Ass
es
sm
en
t
Str
ate
gic
As
ses
sm
ent
Initi
al G
ate
‘O’
Annual ‘O’ Gates
Gates 1-5 repeated for each project
Gate 0 repeated annually
‘P’ levelProcess
Assurance
‘O’ LevelOutcome
Assurance
Pro
gram
me
Clo
se ‘O
’ Gat
e
Source: Welsh Government 2012 – amended to correctly show iterative Gates O
Managing and assuring agile/waterfall hybrid change programmes – my recent article…
http://bit.ly/About-Brian@BrianUkulele
31
[email protected]: brianwernham.wordpress.com
@BrianUkulele http://bit.ly/About-Brian
Thanks for listening!
Click here for
delegates’ discount