This document discusses how adopting Scrum and Agile methodologies can improve IT project success rates within the military. Traditional "waterfall" project approaches have a high failure rate of 62% due to budget overruns and features not providing value. However, using Agile approaches like Scrum increases success rates to 82% by having daily customer interactions, focusing delivery in short sprints, and emphasizing automated testing and continuous integration. The Scrum framework utilizes product owners, a self-organizing delivery team, and a Scrum master to collaborate closely with customers and adapt quickly to changes.

1. Improving
your
service
offering
to
the
military
with
Scrum
and
Agile
Paul
Williams
SOA
Cer(fied
Architect
Cer(fied
Scrum
Master
METOC
Systems

2. Problems
with
IT
Projects
• 62%
Failure
Rate
IT
Projects
• 49%
budget
related
• 47%
higher
than
an(cipated
costs
Success
38%
Success
• 41%
failed
to
provide
Failed
Failed
62%
value
Data
from
www.cio.com

3. Shiny
Toys
Actual
usage
of
Successfully
delivered
features
7%
13%
Never
45%
Rarely
16%
19%
Some(mes
OQen
Always
Adapted
from
Rally’s
ScrumMaster
training.
One
of
our
smart
techies
trying
out
his
new
iPhone
4.

4. Another
way
• 82%
success
rate
Agile
Success
Rates
• 44%
difference
Success
Failure
Success
Rates
100
80
60
40
Success
Rates
20
0
Waterfall
Agile

5. What
is
Scrum
&
Agile?
• Scrum/Agile
• Backlog/User
Stories
• Sprints/Standup
• Chickens,
Pigs,
Product
Owners,
Delivery
Team
• Poker
Planning
• Quality
First

6. Pigs
• Product
Owner
• Delivery
Team
• Scrum
Master

7. Chickens
• Stakeholders

8. Lifecycle

9. Ability
to
change
direc(on

10. Only
concentra(ng
on
the
sprint

11. Transparent

12. Customer
Partnership
• Daily
interac(ons
with
the
customer
• Customer
sets
the
priori(es
• The
customer
sees
results
every
sprint
(2-­‐4
weeks)
Visit
to
the
USS
Makin
Island
with
our
customers
for
a
week
of
finding
out
what
mission
our
end
users
are
trying
to
accomplish.

13. Scrum
Thermometer

14. Status

15. Quality
Deliveries
Done!

16. Automated
Tes(ng

17. Con(nuous
Integra(on

18. Team
Centric
• Every
member
is
“Responsible”
• Storm
on
big
problems,
parallel
tasking
on
easy
ones
• self-­‐organizing
The
USA
team
line
up.
Photograph:
Nicholas
Kamm/AFP/Gejy
Images

19. Addi(onal
Informa(on
Web
Resources
www.scrumalliance.org
www.scrum.org
Required
Reading

20. Contact
Informa(on
Paul
Williams
228.688.1269
paul.williams@geocent.com
www.geocent.com
SOA
CerCfied
Architect
CerCfied
Scrum
Master
METOC
Systems
Specialist