Professional Documents
Culture Documents
8/26/2014
Thinking Workshop
8/26/2014
Planning and
estimating methods
setup the project for
failure
Gov contracts
attempt to fix
everything upfront
and mandate heavy
processes
Slow time to
completion, too long
to deliver
Inherited a tangled
mess of nonintegrated legacy
applications
Missing, incomplete,
changing,
ambiguous
requirements
No value/ ROI
measurement, only
focus on cost
measurement
Lack of clear
direction, no
engaged customer,
wasteful meetings
Heavy engineering
and testing
processes, no
automation
Lack of
empowerment, low
engagement and
morale
Specialized roles,
not my task thinking
Overproduction,
working on wasteful
features
5
Focus
Execution
How do we deliver value
and measure success?
8/26/2014
RE-THINKING PORTFOLIO
MANAGEMENT
What are the 6 levels of Agile planning?
How is Agile Portfolio Management Differ from Traditional
Approaches?
What does the Agile/Lean Portfolio Lifecycle look like?
8/26/2014
10
8/26/2014
11
12
8/26/2014
13
Portfolio Planning 2
Portfolio Planning by Customer Unit
Product/Program Planning 3
Product Planning by Product Managers
Release Planning 4
Release Planning by Product Owner/Team
Iteration Planning 5
Iteration Planning by Team/PO
Daily Planning 6
Daily Task Planning by Team
14
8/26/2014
15
16
8/26/2014
Backlog
orem ipsum dolor sit
amet, co nse ctetur
orem ipsum dolor sit
amet, co nse ctetur
Business Vision
What? Why?
Measurement
orem ipsum dolor sit
amet, co nse ctetur
How
Team
Facilitator
Technical
Vision
17
Program Team
(Scrum of Scrums)
8/26/2014
Portfolio Team
19
20
8/26/2014
http://agileforgovernment.com/real-transformation-videos/
21
The Vision: BCBSNE will have an engaged and collaborative workforce unified
in their pursuit of common goals and efficiently delivering on key initiatives.
Strategic Objectives & Projects
3 Year Roadmap
Stable Teams
22
8/26/2014
23
24
8/26/2014
Value/ROI
Number of releases and number of features per release.
Quality
Escaped defects
Collaboration
Are we more collaborative within IT and between IT and Business partners?
Copyright(c) Agile Transformation Inc.
25
26
8/26/2014
Decision Time!!
How do we structure our teams so
they can deliver value against our
strategic initiatives?
27
28
8/26/2014
www.agileforgovernment.com/download
29
30
8/26/2014
TRANSFORMATION
ROADMAP
Concrete steps for Piloting, Scaling, Enterprise
Concrete learning roadmap
31
Transformation Phases
Copyright(c) Agile
Transformation Inc.
Copyright
Agile
Transformation
Inc
32
8/26/2014
Transformation Roadmap
Copyright(c) Agile
Transformation Inc.
Copyright
Agile
Transformation
Inc
Learning Roadmap
33
8/26/2014
Additional Considerations
Planning for Agile Program teams
Teams working on the same larger initiative will need additional coordination through
a program leadership team.
Distributed Teams
Where the team members are located may impact the design of the team and their
speed towards Agile maturity.
Strong ScrumMasters
Standing up several teams at the same time following an aggressive schedule
requires strong ScrumMasters supporting the coaches.
Management Support
Lack of understanding or support by middle management will potentially kill the
transformation
35
Copyright(c) Agile
Transformation Inc.
Copyright
Agile
Transformation
Inc
36
8/26/2014
37
38
8/26/2014
Source : The Business Value of Agile Software Methods by Dr. F Rico, Dr. H Sayani, Dr. S Sone Page 89
39
Source : The Business Value of Agile Software Methods by Dr. F Rico, Dr. H Sayani, Dr. S Sone
40
8/26/2014
Source : The Business Value of Agile Software Methods by Dr. F Rico, Dr. H Sayani, Dr. S Sone
Picture Souce: www.People10.com
41
Agile
Traditional
Success
14%
Success
42%
Failed
9%
Challenged
49%
Failed
29%
Challenged
57%
42
42
8/26/2014
Rico, D. F. (2008). What is the return-on-investment of agile methods? Retrieved February 3, 2009, from http://davidfrico.com/rico08a.pdf
Rico, D. F. (2008). What is the ROI of agile vs. traditional methods? TickIT International, 10(4), 9-18.
43 43
After Agile
2.25
18
61%
Lower
Cost
Before Agile
13.5
After Agile
15
39%
Less
Staff
Total Staffing
2270
Before Agile
2500
After Agile
1875
10
After Agile
11
10
0.75
20
Before Agile
20
15
1.1
1.50
18
Before Agile
3.00
1250
24%
Faster
381
625
Cumulative Defects
93%
Less
Defects
Mah, Michael. QSM (2008). Measuring agile in the enterprise: Proceedings of the Agile 2008 Conference, Toronto, Canada.
Copyright(c) Agile Transformation Inc.
44 44
8/26/2014
Hoque, F., et al. (2007). Business technology convergence. The role of business technology
convergence in innovation and adaptability and its effect on financial performance. Stamford, CT:
BTM Institute.
45 45
46
8/26/2014
47
48
8/26/2014
Org
Project
Purpose
Electronic
Commerce
Adwords
Advertising
Shrink
Wrapped
Primavera
Primavera
Project
Management
Health
Care
FDA
m2000
Blood
Analysis
Law
Enforcement
FBI
Sentinel
Case File
Workflow
U.S.
DoD
Stratcom
SKIweb
Knowledge
Management
Size
20 teams
140 people
5 countries
15 teams
90 people
Collocated
4 teams
20 people
Collocated
10 teams
50 people
Collocated
3 teams
12 people
Collocated
Metrics
1,838 User Stories
6,250 Function Points
500,000 Lines of Code
26,809 User Stories
91,146 Function Points
7,291,666 Lines of Code
1,659 User Stories
5,640 Function Points
451,235 Lines of Code
3,947 User Stories
13,419 Function Points
1,073,529 Lines of Code
390 User Stories
1,324 Function Points
105,958 Lines of Code
Rico, D. F., Sayani, H. H., & Sone, S. (2009). The business value of agile software methods: Maximizing ROI with just-in-time processes and
Rico, D.Ft.
F. (2010).
Lean and
project
management: For large programs and projects. Proceedings of the First International Conference on Lean
documentation.
Lauderdale,
FL:agile
J. Ross
Publishing.
Enterprise Software and Systems, Helsinki, Finland, 37-43.
49 49
50
8/26/2014
51
statement:
years.
The GAO report profiles agile initiatives from the Department
of Defense, NASA, the US Patent and Trademark Office, the
VA and the IRS.
Source: http://bit.ly/PMPTIa - Jason Bloomberg www.cio.com
Copyright(c) Agile Transformation Inc.
52
8/26/2014
53
54