Government Projects the Agile Way Can It Be Done

1
Government Projects the Agile WayCan It Be Done?

• Welcome!
• Mark Leicester
• Senior Technical AnalystState Services
  Commission

This presentation has been adapted from Agile
Overviewby Balachander Swaminathan and Naresh
Jain (licensed under CC by-nc-sa)
2
Government Projects the Agile WayCan It Be Done?

• Introducing our panel
• Mike Lowery
• Andy Neale
• Mark Pascall
• Liesle Venter-Wagner

3
Government Projects the Agile WayCan It Be Done?

• Part One
• An Overview of Agile
• Governance
• Vendor/Agency Relationships
• Getting Started
• Tea / Coffee Break

4
Software Engineering

• the application of a systematic, disciplined,
  quantifiable approach to development, operation
  and maintenance of software that is, the
  application of engineering to software.
• IEEE Standard Computer Dictionary

5
Safeguard Ballistic MissileDefence System

• Late 1960's project to protect US missile sites
  from missile attack
• Close relationship between hardware and software
• Late requirements changesnot an option

6
Safeguard Ballistic MissileDefence System

• Late 1960's project to protect US missile sites
  from missile attack
• Close relationship between hardware and software
• Late requirements changesnot an option
• Did it work?

7
Safeguard Ballistic MissileDefence System

• Delivered to specification

8
Safeguard Ballistic MissileDefence System

• Delivered to specification
• 6 years / 5407 person years

9
Safeguard Ballistic MissileDefence System

• Delivered to specification
• 6 years / 5407 person years
• 25 billion (unadjusted)
• But...

10
Safeguard Ballistic MissileDefence System

• Delivered to specification
• 6 years / 5407 person years
• 25 billion (unadjusted)
• But...
• Operational forjust 133 days!

PROJECTCANCELLED
11
Safeguard Ballistic MissileDefence System

• due to concerns over cost, effectiveness, and
  achanging political climate.
• Wikipedia

12
Software Engineering Revisited

• IEEE Software Engineering is a good fit when
• Requirements are stable
• Technology is well known and mature
• The problem has been solved before
• Everything goes to plan

13
Software Engineering Revisited

• IEEE Software Engineering is a good fit when
• Requirements are stable
• Technology is well known and mature
• The problem has been solved before
• Everything goes to plan
• And how often is this true?

14
The Traditional Process
Analysis
Time
Design
Coding
Testing
15
The Traditional Process
Analysis
Time
Time
Design
Coding
Testing
(The costof changeincreases)
16
The Traditional Process
Analysis
Time
Design
Coding
Do we have halfa solution yet?
Testing
(The costof changeincreases)
17
The Agile Process
Analysis
Design
Coding
Testing
Time
18
The Agile Process
Analysis
Design
Coding
Testing
Time
19
The Agile Process
20 done(100 usable!)
Analysis
Design
Coding
Testing
Time
20
Agile Methodologies

• XP (Extreme Programming)
• SCRUM
• FDD (Feature Driven Development)
• DSDM (Dynamic System Development Method)
• Adaptive Software Development
• Crystal
• Lean Software Development

21
The Agile Manifesto (2001)

• We are uncovering better ways of developing
  software by doing it and helping others do it.
  Through this work we have come to value

22
The Agile Manifesto (2001)

• We are uncovering better ways of developing
  software by doing it and helping others do it.
  Through this work we have come to value
• Individuals and interactions over processes and
  tools

23
The Agile Manifesto (2001)

• We are uncovering better ways of developing
  software by doing it and helping others do it.
  Through this work we have come to value
• Individuals and interactions over processes and
  tools
• Working software over comprehensive documentation

24
The Agile Manifesto (2001)

• We are uncovering better ways of developing
  software by doing it and helping others do it.
  Through this work we have come to value
• Individuals and interactions over processes and
  tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation

25
The Agile Manifesto (2001)

• We are uncovering better ways of developing
  software by doing it and helping others do it.
  Through this work we have come to value
• Individuals and interactions over processes and
  tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

26
The Agile Manifesto (2001)

• We are uncovering better ways of developing
  software by doing it and helping others do it.
  Through this work we have come to value
• Individuals and interactions over processes and
  tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
• That is, while there is value in the items on the
  right, we value the items on the left more.

27
Government Projects the Agile WayCan It Be Done?
28
Choose your preferred topic

• Myths Legends Exploring the myths and legends
  of Agile.
• Budgeting for Agile Do you save money with
  Agile?
• Procurement Are you an agency into agile, but
  have no in-house capability? Can vendors lead
  projects?
• Being Agile What is it actually like to build
  things the Agile way?
• Education How do I find, or become, an
  accredited Agile practitioner?

29
Government Projects the Agile WayCan It Be Done?

• Part Two
• The winning topics
• Questions / Discussion
• How can GOVIS help?
• Drinks