As software architecture catches up to other
engineering architecture, it will be a wild ride for us
for some time.
%
Apps get to market late
Source: CA / Coleman Parkes Research 2012
%
Apps go to market
missing functionality
Source: CA / Coleman Parkes Research 2012
Number of releases expected to be delivered/managed per year

Average
4.6
6.4

average months
to release

28% <3 months
So...
Agile
Requirements

How Did We Get
Here?

Enterprise Agile
Manage Demand
and Define Requirements

Minimal Planning

Minimum Viable Product
Minimal Risk

Most
Value

Continuous caden...
Impediments

http://tinyurl.com/STLVS2013
The Problem
A

B

C

http://tinyurl.com/STLVS2013
The Problem
A

Stakeholders

B

C

http://tinyurl.com/STLVS2013

D

E

F
The Portfolio Backlog

A

http://tinyurl.com/STLVS2013

B

C

D

E

F
The Portfolio Backlog

A

http://tinyurl.com/STLVS2013

B

C

D

E

F
Kanban Columns

A

http://tinyurl.com/STLVS2013

B

C

D

E

F
Work Item Tags

A

http://tinyurl.com/STLVS2013

B

C

D

E

F
N-Levels

A

http://tinyurl.com/STLVS2013

B

C

D

E

F
Agile Planning  - Scaling Agile Development
Agile Planning  - Scaling Agile Development
Agile Planning  - Scaling Agile Development
Agile Planning  - Scaling Agile Development
Agile Planning  - Scaling Agile Development
Agile Planning  - Scaling Agile Development
Agile Planning  - Scaling Agile Development
Agile Planning  - Scaling Agile Development
Upcoming SlideShare
Loading in …5
×

Agile Planning - Scaling Agile Development

582
-1

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
582
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
49
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Agile Planning - Scaling Agile Development

  1. 1. As software architecture catches up to other engineering architecture, it will be a wild ride for us for some time.
  2. 2. % Apps get to market late Source: CA / Coleman Parkes Research 2012
  3. 3. % Apps go to market missing functionality Source: CA / Coleman Parkes Research 2012
  4. 4. Number of releases expected to be delivered/managed per year Average 4.6 6.4 average months to release 28% <3 months Source: CA / Coleman Parkes Research 2012
  5. 5. Agile Requirements How Did We Get Here? Enterprise Agile
  6. 6. Manage Demand and Define Requirements Minimal Planning Minimum Viable Product Minimal Risk Most Value Continuous cadence of value delivery Highest Value Features
  7. 7. Impediments http://tinyurl.com/STLVS2013
  8. 8. The Problem A B C http://tinyurl.com/STLVS2013
  9. 9. The Problem A Stakeholders B C http://tinyurl.com/STLVS2013 D E F
  10. 10. The Portfolio Backlog A http://tinyurl.com/STLVS2013 B C D E F
  11. 11. The Portfolio Backlog A http://tinyurl.com/STLVS2013 B C D E F
  12. 12. Kanban Columns A http://tinyurl.com/STLVS2013 B C D E F
  13. 13. Work Item Tags A http://tinyurl.com/STLVS2013 B C D E F
  14. 14. N-Levels A http://tinyurl.com/STLVS2013 B C D E F
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×