3/19/2009
Plans change very easily. Worldly affairs do not always go according to a plan and orders have to change rapidly in response to a change in circumstances. If one sticks to the idea that once set, a plan should not be changed, a business cannot exist for long.
-- Taiichi Ohno, Toyota Production System. (the father of lean methods)
3/19/2009
Agenda
1. Orientation and Overview Why the waterfall/milestone governance model of software development doesnt work Perspectives on Agile Portfolio Management: DTE Energy Case Study 3. Rethinking Investment Funding 4. Rethinking Change Management 5. Rethinking Governance and Oversight
3/19/2009
Waterfall/milestone governance doesnt work because the development model doesnt work
Requirements
Application Development
System Integration Operation and Maintenance
Why, When I was your age, sometimes Ive believed in six impossible things before breakfast The Queen to Alice in Wonderland
There is probably no job on earth for which an ability to believe six impossible things before breakfast is more of a requirement than Software Project Management DeMarco and Lister - Waltzing with Bears: Managing Risks in Software Projects
r
Fixed scope (requirements)
r r r r r r r r r r r
rr
r
r r r
r r
r r
Fixed time
1) In order to give a professional estimate, we have to analyze and estimate even this one before time even begins!
3/19/2009
There exists a reasonably well defined set of requirements, if we only took the time to define them
We can limit change or it will be small and manageable System integration is a stage in the lifecycle and we can predict how that will go Software research and development can be done on a predictable schedule and budget
Promote the non-participants Scope triage Create a new plan Reduce testing time Cut back on quality Extend delivery date Repeat failed process
10
3/19/2009
The teams are not on plan bad plan (blame planning) or bad team (blame development team)? They are under enormous pressure to deliver the promised functionality in the box In order to complete the committed work, the teams must actively resist any further change They are about of time and they have only one variable left under their control Solution: Sacrifice QUALITY
11
12
3/19/2009
Wait, it gets worseThe buggy solution we don't quite have is a poor fit to current requirements
100%
75%
Fidelity Gap
50%
25% 0 3 6 9 12 15 18 21 24
13
14
3/19/2009
Yahoo, Google, BTI, BMC, Nokia, DTE Energy, Cisco, Citrix, HP, JP Morgan, AOL Boeing, Comcast, PayPal, EDS, Emerson, Fidelity
16
3/19/2009
17
18
3/19/2009
19
20
10
3/19/2009
Reduces Risk
21
$ in
Waterfall $$$$$ start here if you are lucky and on time
22
11
3/19/2009
23
24
12
3/19/2009
Team Agility
A disciplined set of
enhanced software engineering practices empirical software project management practices modified social behaviors
25
1. The Define/Build/Test Team 2. Mastering the Iteration 3. Smaller, More Frequent Releases
4. Two-level Planning
5. Concurrent Testing 6. Continuous Integration 7. Regular Reflection and Adaptation
26
13
3/19/2009
Enterprise Agility
A set of organizational best practices beliefs core values That harness large numbers of agile teams to build and release quality enterprise enterprise-class software more rapidly than ever before Explicitly driven by intimate and immediate customer feedback
Copyright 2009, Leffingwell, LLC.
27
1. Intentional Architecture 2. Lean Requirements at Scale 3. Systems of Systems and the Agile Release Train
28
14
3/19/2009
30
15
3/19/2009
The following slides are abstracted from a case study Establishing an Agile Portfolio to Align IT Investments with Business Needs -- Thomas and Baker, DTE Energy presented at Agile 2008, by DTE Energy. DTE Energy, a Fortune 300 is a diversified energy company involved in the development and management of energy related businesses and services nationwide with $9 billon in annual revenue and 11,000 employees. DTE Energys Information Technology Services (ITS) organization, now consisting of over 900 people, provides leadership, oversight, delivery, and support on all aspects of information technology (IT) across the enterprise. They have been implementing an extending agile practices since 1998.
Mindset
widget engineering
Manifestation
-Fixed schedule, functionality planning -Big Up Front Design/Analysis (BUFD) -Do what you are told -We are the boss of you
Problems
- Long range plans - Resources committed year in advance - Analysis paralysis -False agreements. No buy in. -Misses innovation contribution from IT -Failure to meet expectations mistrust -No empowerment, lower motivation
32
16
3/19/2009
Manifestation
-Resources committed long range -100% allocation before what if - Key resources assigned to multiple projects
Problems
- No time to think or innovate - Dedicate resources to task or lose resources - Thrashing productivity lost of most valuable resources - Exhaustion, burnout - Deferred recognition of plan vs. actual - Late discovery and renegotiation - Loss of credibility, mistrust
Get it done
33
Manifestation
- Fine grain reporting and overhead - Detailed wbs, earned value metrics ,fully loaded Gantt charts
Problems
- Reporting overhead - Annoying the team - Metrics dont reflect actual progress -Could not assess new agile projects with old metrics - Plans are obsolete, but not treated that way
34
17
3/19/2009
To Agile Portfolio
Dedicated teams stop multiplexing no one works on more than one team Project overhead is replaced by standard iteration and release cadence New initiatives appear as new content and are prioritized at each iteration/release boundary Work in an iteration/release is fixed Team resources are adjusted only at periodic release boundaries
36
18
3/19/2009
Feature:
feature
Substantive user benefit Used for release planning Features sized to fit in release boundaries System-level, common and non-functional requirements often carried here
User value Used for iteration planning Sized to fit in iteration boundaries
38
19
3/19/2009
To Agile Model
1-2 page business case form Not much detail Business cases that make the cut get exploratory iterations funding Easily cancelled if progress not acceptable Fast ROI if it is Updated quarterly changes only
Ipsum lorem
39
At Release Planning
Business case drives vision - which drives features Resources adjusted to address constraints (velocity bottlenecks)
40
20
3/19/2009
4 pts 2 pts
Iteration planning
Reporting
Release/iteration review/retropective
42
21
3/19/2009
Issues: Irrelevant to agile teams Hard to maintain Always obsolete If a team isnt on the plan, is it a bad team or bad plan? Measure paper, not software
Issues: Most agile companies start here Little coordination amongst teams Non-harmonized schedules No visibility beyond the next sprint Little or no system level visibility
43
architects
Teams plan stories for iterations Work out dependencies Architects and PMs, POs circulate
Product managers/ Product Owners
|1 |2 |3 |4 |1 |2 |3 |4
44
22
3/19/2009
Road Rage Ported (part I) Brickyard port started (stretch goal to complete) Distributed platform demo ALL GUIs for both games demonstrable New features (see prioritized list) Demo of Beemer game
Road Rage Completed (single user) Brickyard Ported (single user) Road Rage multiuser demonstrable First multiuser game feature for Road Rage New features (see prioritized list) Beemer game in Alpha
Multiuser Road Rage first release Brickyard Ported multiuser demo New features for both games (see prioritized list) Beemer game to E3 Tradeshow?
45
23
3/19/2009
47
Value time Waiting/waste time Source: Implementing Lean Software Development: From Concept to Cash. Poppendiecks
48
24
3/19/2009
49
Program Approved
2.1 - 2.n
Incremental releases
Commit to Maintenance
Quality/GA Firewall
1.1 - 1.n
Potentially shippable Increments
50
25
3/19/2009
51
52
26
3/19/2009
Agile Portfolio Management -- Jochen Krebs, 2008, Microsoft Press Agile Project Management Leadership Network, http://apln.org/ Establishing an Agile Portfolio to Align IT Investments with Business Needs, -- Thomas and Baker, DTE Energy, Proceedings of Agile 2008 Implementing Lean Software Development: From Concept to Cash -- Poppendieck, 2007. Addison-Wesley Scaling Software Agility: Best Practices for Large Enterprises -- Leffingwell, 2007. Addison-Wesley The Software Project Managers Bridge to Agility -- Sliger and Broderick, 2008. Addison Wesley
53
27