Is your organization struggling to make the right investments at the enterprise level and deliver value as quickly as possible to the end-user? Mike Cottmeyer from LeadingAgile explained what agility means at the portfolio and program level, and how it differs from traditional plan-driven approaches.

1. Agile Program and Portfolio
Management
Mike Cottmeyer, President & Agile Coach
LeadingAgile, LLC
Wednesday, February 6, 13

2. Mike Cottmeyer
mike@leadingagile.com
404.312.1471
www.leadingagile.com
twitter.com/mcottmeyer
facebook.com/leadingagile
linkedin.com/in/cottmeyer
Wednesday, February 6, 13

3. Before We Start...
Wednesday, February 6, 13

4. Before We Start...
This is not a process overlay for
your existing organization...
Wednesday, February 6, 13

5. Before We Start...
Organiza(onal+
Transforma(on+
Personal+ Adopt++
Transforma(on+ Prac(ces+
Wednesday, February 6, 13

6. Before We Start...
Organiza(onal+
Transforma(on+
Personal+ Adopt++
Transforma(on+ Prac(ces+
Wednesday, February 6, 13

7. Before We Start...
Organiza(onal+
Transforma(on+
Strategic
Personal+ Adopt++
Transforma(on+ Prac(ces+ Release
Iteration
Daily
Continuous
Wednesday, February 6, 13

8. Before We Start...
Organiza(onal+
Transforma(on+
Strategic
Personal+ Adopt++
Transforma(on+ Prac(ces+ Release
Iteration
Daily
Continuous
Wednesday, February 6, 13

9. Projects, Programs, Portfolios
Wednesday, February 6, 13

10. Agile Project Management
Scrum Scrum Scrum Scrum
Team Team Team Team
Wednesday, February 6, 13

11. Agile Program Management
Program Program
Team Team
Scrum Scrum Scrum Scrum
Team Team Team Team
Wednesday, February 6, 13

12. Agile Portfolio Management
Portfolio
Team
Program Program
Team Team
Scrum Scrum Scrum Scrum
Team Team Team Team
Wednesday, February 6, 13

13. Enterprise Portfolio Management
Strategy Portfolio
Support
Team Team
Program Program
Team Team
Scrum Scrum Scrum Scrum
Team Team Team Team
Wednesday, February 6, 13

14. How is Agile PPM Different?
Business Agility at the Portfolio Level
• Want our investment portfolio to respond to
the needs of changing market conditions
• We need the ability as an organization to
respond to changing market conditions
Wednesday, February 6, 13

15. How is Agile PPM Different?
Business Agility at the Portfolio Level
• Want our investment portfolio to respond to
the needs of changing market conditions
• We need the ability as an organization to
respond to changing market conditions
• It’s less about team level agility, although that is
an essential component
Wednesday, February 6, 13

16. Foundational Stuff...
The Anatomy of Agile Teams
Wednesday, February 6, 13

17. Agile Teams
• Who’s involved?
• Dependencies
• Backlog
• Velocity
• Accountability
Wednesday, February 6, 13

18. Scrum
Team
Wednesday, February 6, 13

19. Scrum
Team Developers
Wednesday, February 6, 13

20. Scrum
Team Developers
Testers
Wednesday, February 6, 13

21. Analysts
Scrum
Team Developers
Testers
Wednesday, February 6, 13

22. Analysts
Lead Scrum
Team Developers
Testers
Wednesday, February 6, 13

23. Analysts
Lead Scrum
Team Developers
ScrumMaster
Testers
Wednesday, February 6, 13

24. Product Owner
Analysts
Lead Scrum
Team Developers
ScrumMaster
Testers
Wednesday, February 6, 13

25. Foundational Stuff...
Time, Cost, and Scope
Wednesday, February 6, 13

26. Scope
Time Cost
Wednesday, February 6, 13

27. Time Cost
Scope
Wednesday, February 6, 13

28. Time Cost
$$$
Scope
Wednesday, February 6, 13

29. Managing Variable Scope
How to deal with making commitments when scope is
constantly changing
Wednesday, February 6, 13

30. Story Maps
Wednesday, February 6, 13

31. Epics
collec*ons
of
features,
typically
1-­‐3
months
in
dura*on.
Epics
Epic span
releases.
Epics
can
span
more
than
one
team.
These
are
the
things
senior
leadership
cares
about.
Wednesday, February 6, 13

32. Epics
collec*ons
of
features,
typically
1-­‐3
months
in
dura*on.
Epics
Epic span
releases.
Epics
can
span
more
than
one
team.
These
are
the
things
senior
leadership
cares
about.
Features
are
smaller
than
epics,
typically
2-­‐4
weeks
in
dura*on.
Feature Features
are
contained
within
releases.
Features
are
contained
within
a
team.
These
are
what
the
Product
Owner
Cares
about.
Wednesday, February 6, 13

33. Epics
collec*ons
of
features,
typically
1-­‐3
months
in
dura*on.
Epics
Epic span
releases.
Epics
can
span
more
than
one
team.
These
are
the
things
senior
leadership
cares
about.
Features
are
smaller
than
epics,
typically
2-­‐4
weeks
in
dura*on.
Feature Features
are
contained
within
releases.
Features
are
contained
within
a
team.
These
are
what
the
Product
Owner
Cares
about.
User
Stories
are
the
smallest
increment
of
value,
typically
less
than
a
User
week.
User
Stories
are
contained
within
sprint.
These
are
the
things
Story
Engineering
Management
Cares
about.
Wednesday, February 6, 13

34. Story
Maps
visually
show
the
Epic rela*onship
between
User
Stories
and
Business
Value
Feature Feature Feature Feature
User
Story User
Story User
Story User
Story
User
Story User
Story User
Story User
Story
User
Story User
Story User
Story User
Story
User
Story User
Story User
Story User
Story
Wednesday, February 6, 13

35. Story
Maps
start
with
the
Epic iden*fica*on
of
larger,
more
strategic
organiza*onal
goals
Wednesday, February 6, 13

36. Epics
are
decomposed
into
Epic Features
that
describe
the
value
added
into
the
product
Feature
Wednesday, February 6, 13

37. Epics
are
decomposed
into
Epic Features
that
describe
the
value
added
into
the
product
Feature Feature
Wednesday, February 6, 13

38. Epics
are
decomposed
into
Epic Features
that
describe
the
value
added
into
the
product
Feature Feature Feature
Wednesday, February 6, 13

39. Epics
are
decomposed
into
Epic Features
that
describe
the
value
added
into
the
product
Feature Feature Feature Feature
Wednesday, February 6, 13

40. Features
are
decomposed
into
Epic User
Stories
that
are
thin
slices
of
value
added
into
the
system
Feature Feature Feature Feature
User
Story
User
Story
User
Story
User
Story
Wednesday, February 6, 13

41. Features
are
decomposed
into
Epic User
Stories
that
are
thin
slices
of
value
added
into
the
system
Feature Feature Feature Feature
User
Story User
Story
User
Story User
Story
User
Story User
Story
User
Story User
Story
Wednesday, February 6, 13

42. Features
are
decomposed
into
Epic User
Stories
that
are
thin
slices
of
value
added
into
the
system
Feature Feature Feature Feature
User
Story User
Story User
Story
User
Story User
Story User
Story
User
Story User
Story User
Story
User
Story User
Story User
Story
Wednesday, February 6, 13

43. Features
are
decomposed
into
Epic User
Stories
that
are
thin
slices
of
value
added
into
the
system
Feature Feature Feature Feature
User
Story User
Story User
Story User
Story
User
Story User
Story User
Story User
Story
User
Story User
Story User
Story User
Story
User
Story User
Story User
Story User
Story
Wednesday, February 6, 13

44. Minimally Marketable
Features
Wednesday, February 6, 13

45. User
Stories
are
es*mated
in
Epic rela*ve
units
of
measure
called
Story
Points
Feature Feature Feature Feature
User
Story3 1
User
Story User
Story2 User
Story1
2
User
Story User
Story3 5
User
Story User
Story3
5
User
Story User
Story2 User
Story3 User
Story2
1
User
Story User
Story1 User
Story2 2
User
Story
Wednesday, February 6, 13

46. Story
Points
can
be
added
up
to
Epic size
Features
11 7 12 8
Feature Feature Feature Feature
User
Story3 1
User
Story User
Story2 User
Story1
2
User
Story User
Story3 5
User
Story User
Story3
5
User
Story User
Story2 User
Story3 User
Story2
1
User
Story User
Story1 User
Story2 2
User
Story
Wednesday, February 6, 13

47. 38 Feature
Points
can
be
added
up
to
Epic size
Epics
11 7 12 8
Feature Feature Feature Feature
User
Story3 1
User
Story User
Story2 User
Story1
2
User
Story User
Story3 5
User
Story User
Story3
5
User
Story User
Story2 User
Story3 User
Story2
1
User
Story User
Story1 User
Story2 2
User
Story
Wednesday, February 6, 13

48. 38 Our
Goal
is
to
build
the
smallest
Epic system
possible
to
deliver
the
value
in
the
Epic
11 7 12 8
Feature Feature Feature Feature
User
Story3 1
User
Story User
Story2 User
Story1
2
User
Story User
Story3 5
User
Story User
Story3
5
User
Story User
Story2 User
Story3 User
Story2
1
User
Story User
Story1 User
Story2 2
User
Story
Wednesday, February 6, 13

49. 38 We
con*nuously
evaluate
the
Epic Story
Map
to
determine
the
Minimally
Marketable
Feature
11 7 12 8
Feature Feature Feature Feature
User
Story3 1
User
Story User
Story2 User
Story1
2
User
Story User
Story3 5
User
Story User
Story3
5
User
Story User
Story2 User
Story3 User
Story2
1
User
Story User
Story1 User
Story2 2
User
Story
Wednesday, February 6, 13

50. 38 We
con*nuously
evaluate
the
Epic Story
Map
to
determine
the
Minimally
Marketable
Feature
11 7 12 8
Feature Feature Feature Feature
3
User
Story 1
User
Story 2
User
Story User
Story1
2
User
Story 3
User
Story 5
User
Story 3
User
Story
5
User
Story User
Story2 3
User
Story User
Story2
1
User
Story User
Story1 User
Story2 2
User
Story
Wednesday, February 6, 13

51. 26 When
we
focus
on
Minimally
Epic Marketable
Features,
we
deliver
Business
Value
early
10 4 5 7
Feature Feature Feature Feature
3
User
Story 1
User
Story 2
User
Story User
Story1
2
User
Story 3
User
Story 5
User
Story 3
User
Story
5
User
Story User
Story2 3
User
Story User
Story2
1
User
Story User
Story1 User
Story2 2
User
Story
Wednesday, February 6, 13

52. Essential View #1
Velocity & Burndown
Wednesday, February 6, 13

53. Sprinting
Wednesday, February 6, 13

54. Minimally
Marketable
Features
feed
the
priori*za*on
of
our
Sprint
Planning
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
Wednesday, February 6, 13

55. Iden*fy
the
User
Story
most
likely
to
contribute
to
the
MMF
and
build
that
one
first
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
Wednesday, February 6, 13

56. Iden*fy
the
User
Story
most
likely
to
contribute
to
the
MMF
and
build
that
one
first
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3
User
Story
Wednesday, February 6, 13

57. Pull
User
Stories
in
priority
order
focusing
on
delivering
complete
MMFs
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3
User
Story
Wednesday, February 6, 13

58. Pull
User
Stories
in
priority
order
focusing
on
delivering
complete
MMFs
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3
User
Story
2
User
Story
Wednesday, February 6, 13

59. It’s
okay
to
work
User
Stories
across
MMFs
if
that
is
what
the
Product
Owner
needs
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3
User
Story
2
User
Story
Wednesday, February 6, 13

60. It’s
okay
to
work
User
Stories
across
MMFs
if
that
is
what
the
Product
Owner
needs
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3
User
Story
2
User
Story
1
User
Story
Wednesday, February 6, 13

61. The
team
uses
its
past
velocity
to
determine
how
many
stories
go
in
the
Sprint
Planned
Team
Velocity
=
6
points
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3
User
Story
2
User
Story
1
User
Story
Wednesday, February 6, 13

62. The
Team
breaks
each
User
Story
down
into
Tasks
Planned
Team
Velocity
=
6
points
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3 Task Task
User
Story
Task
2
User
Story
1
User
Story
Wednesday, February 6, 13

63. The
Team
breaks
each
User
Story
down
into
Tasks
Planned
Team
Velocity
=
6
points
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3 Task Task
User
Story
Task
2 Task Task
User
Story
Task
Task
1
User
Story
Wednesday, February 6, 13

64. The
Team
breaks
each
User
Story
down
into
Tasks
Planned
Team
Velocity
=
6
points
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3 Task Task
User
Story
Task
2 Task Task
User
Story
Task
Task
Task Task
1
User
Story
Task Task
Wednesday, February 6, 13

65. And
es*mates
each
Task
in
Real
Hours
so
they
can
assess
if
they
can
make
a
solid
Commitment
to
Deliver
Planned
Team
Velocity
=
6
points
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
16
3 Task
8
Task
User
Story
8
Task
2 Task Task
User
Story
Task
Task
Task Task
1
User
Story
Task Task
Wednesday, February 6, 13

66. And
es*mates
each
Task
in
Real
Hours
so
they
can
assess
if
they
can
make
a
solid
Commitment
to
Deliver
Planned
Team
Velocity
=
6
points
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
16
3 Task
8
Task
User
Story
8
Task
2
2 Task 16 Task
User
Story 8
4 Task
Task
Task Task
1
User
Story
Task Task
Wednesday, February 6, 13

67. And
es*mates
each
Task
in
Real
Hours
so
they
can
assess
if
they
can
make
a
solid
Commitment
to
Deliver
Planned
Team
Velocity
=
6
points
Planned
Es*mated
Hours
=
98
hours
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
16
3 Task
8
Task
User
Story
8
Task
2
2 Task 16 Task
User
Story 8
4 Task
Task
8 4
Task Task
1
User
Story
16 8
Task Task
Wednesday, February 6, 13

68. At
the
beginning
of
the
Sprint,
The
Team
pulls
Tasks
from
the
top
of
the
Task
Backlog
Planned
Team
Velocity
=
6
points
Planned
Es*mated
Hours
=
98
hours
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3 Task
8
User
Story
16
8
Task
Task
2
2 Task 16 Task
User
Story 8
4 Task
Task
8 4
Task Task
1
User
Story
16 8
Task Task
Wednesday, February 6, 13

69. Tasks
move
across
the
Story
Board
un*l
there
is
a
completed
User
Story.
Planned
Team
Velocity
=
6
points
Planned
Es*mated
Hours
=
98
hours
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3 Task
8
User
Story
16
8 Task
Task
2
2 Task 16 Task
User
Story 8
4 Task
Task
8 4
Task Task
1
User
Story
16 8
Task Task
Wednesday, February 6, 13

70. Tasks
move
across
the
Story
Board
un*l
there
is
a
completed
User
Story.
Planned
Team
Velocity
=
6
points
Planned
Es*mated
Hours
=
98
hours
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
3 Task
8
User
Story
16
8 Task
Task
2 Task 16 Task
2
User
Story 8
4 Task
Task
8 4
Task Task
1
User
Story 8
16 Task
Task
Wednesday, February 6, 13

71. Tasks
move
across
the
Story
Board
un*l
there
is
a
completed
User
Story.
Planned
Team
Velocity
=
6
points
Planned
Es*mated
Hours
=
98
hours
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
8
Task 3
User
Story
16
8 Task
Task
2 Task 16 Task
2
User
Story 8
4 Task
Task
8 4
Task Task
1
User
Story 8
16 Task
Task
Wednesday, February 6, 13

72. The
Team
works
from
the
top
of
the
Story
Board,
Swarming
to
get
User
Stories
across
the
board
as
fast
as
possible
.
Planned
Team
Velocity
=
6
points
Planned
Es*mated
Hours
=
98
hours
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
8
Task 3
User
Story
16
8 Task
Task
2 Task 16 Task
2
User
Story 8
4 Task
Task
8 4
Task Task
1
User
Story 8
16 Task
Task
Wednesday, February 6, 13

73. The
Team
works
from
the
top
of
the
Story
Board,
Swarming
to
get
User
Stories
across
the
board
as
fast
as
possible
.
Planned
Team
Velocity
=
6
points
Planned
Es*mated
Hours
=
98
hours
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
8
Task 3
User
Story
16
8 Task
Task
2
Task 16 Task 2
8 User
Story
4 Task
Task
8 4
Task Task
1
User
Story 8
16 Task
Task
Wednesday, February 6, 13

74. The
Team
works
from
the
top
of
the
Story
Board,
Swarming
to
get
User
Stories
across
the
board
as
fast
as
possible
.
Planned
Team
Velocity
=
6
points
Planned
Es*mated
Hours
=
98
hours
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
8
Task 3
User
Story
16
8 Task
Task
2
Task 16 Task 2
8 User
Story
4 Task
Task
8 4
Task Task
1
User
Story 16 Task
8
Task
Wednesday, February 6, 13

75. Un*l
the
en*re
Sprint
has
been
delivered
to
the
Product
Owner.
Planned
Team
Velocity
=
6
points
Planned
Es*mated
Hours
=
98
hours
Story
Backlog Task
Backlog In
Process Task
Done Story
Done
8
Task 3
User
Story
16
8 Task
Task
2
Task 16 Task 2
8 User
Story
4 Task
Task
Task
8
Task
4 1
User
Story
8
16 Task
Task
Wednesday, February 6, 13

76. Measuring Progress
Wednesday, February 6, 13

77. From
a
Metrics
perspec*ve,
we
Burn
Down
hours
to
make
sure
the
sprint
is
on
track
38 96
6
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

78. From
a
Metrics
perspec*ve,
we
Burn
Down
hours
to
make
sure
the
sprint
is
on
track
38 96
6
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

79. From
a
Metrics
perspec*ve,
we
Burn
Down
hours
to
make
sure
the
sprint
is
on
track
38 96
6
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

80. From
a
Metrics
perspec*ve,
we
Burn
Down
hours
to
make
sure
the
sprint
is
on
track
38 96
6
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

81. From
a
Metrics
perspec*ve,
we
Burn
Down
hours
to
make
sure
the
sprint
is
on
track
38 96
6
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

82. From
a
Metrics
perspec*ve,
we
Burn
Down
hours
to
make
sure
the
sprint
is
on
track
38 96
6
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

83. From
a
Metrics
perspec*ve,
we
Burn
Down
hours
to
make
sure
the
sprint
is
on
track
38 96
6
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

84. From
a
Metrics
perspec*ve,
we
Burn
Down
hours
to
make
sure
the
sprint
is
on
track
38 96
6
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

85. From
a
Metrics
perspec*ve,
we
Burn
Down
hours
to
make
sure
the
sprint
is
on
track
38 96
6
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

86. From
a
Metrics
perspec*ve,
we
Burn
Down
points
to
make
sure
the
Release
is
on
track
38 96
6
6
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

87. From
a
Metrics
perspec*ve,
we
Burn
Down
points
to
make
sure
the
Release
is
on
track
38 96
8
6
6
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

88. We
track
Velocity
Trend
to
make
sure
the
team
is
delivering
in
a
Predictable
manner
38 96
8
6
6 5
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

89. When
the
Release
is
ready
to
deliver,
The
Team
has
completed
the
highest
priority
User
Stories,
against
the
highest
priority
Features
,against
the
highest
priority
Epics.
38 96
8
6
6 5
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

90. When
the
Release
is
ready
to
deliver,
The
Team
has
completed
the
highest
priority
User
Stories,
against
the
highest
priority
Features
,against
the
highest
priority
Epics.
Everyone
is
focused
on
delivering
value
early
and
oen!
38 96
8
6
6 5
Release
Burndown Sprint
Burndown Velocity
Trend
Wednesday, February 6, 13

91. Essential View #2
Roadmap Over Time
Wednesday, February 6, 13

92. Planning Horizons
Wednesday, February 6, 13

93. Q1 Q2 Q3 Q4
Wednesday, February 6, 13

94. Q1 Q2 Q3 Q4
Epic
Wednesday, February 6, 13

95. Q1 Q2 Q3 Q4
Epic Epic
Wednesday, February 6, 13

96. Q1 Q2 Q3 Q4
Epic Epic Epic
Wednesday, February 6, 13

97. Q1 Q2 Q3 Q4
Epic Epic Epic Epic
Wednesday, February 6, 13

98. Q1 Q2 Q3 Q4
Epic Epic Epic Epic Epic
Wednesday, February 6, 13

99. Q1 Q2 Q3 Q4
Epic Epic Epic Epic Epic Epic
Wednesday, February 6, 13

100. Q1 Q2 Q3 Q4
Epic Epic Epic Epic Epic Epic Epic
Wednesday, February 6, 13

101. Q1 Q2 Q3 Q4
Epic Epic Epic Epic Epic Epic Epic Epic
Wednesday, February 6, 13

102. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Wednesday, February 6, 13

103. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Wednesday, February 6, 13

104. Progressive Elaboration
Wednesday, February 6, 13

105. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature
Wednesday, February 6, 13

106. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature
Wednesday, February 6, 13

107. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature
Wednesday, February 6, 13

108. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature Feature
Wednesday, February 6, 13

109. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature Feature
User
Story User
Story
User
Story User
Story
Wednesday, February 6, 13

110. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature Feature
User
Story User
Story User
Story User
Story
User
Story User
Story User
Story
Wednesday, February 6, 13

111. Dealing with Risk
Wednesday, February 6, 13

112. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature Feature
User
Story User
Story User
Story User
Story
User
Story User
Story User
Story
Risk Risk
Wednesday, February 6, 13

113. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature Feature
User
Story User
Story User
Story User
Story User
Story User
Story
User
Story User
Story User
Story
Risk Risk
Wednesday, February 6, 13

114. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature Feature
User
Story User
Story User
Story User
Story User
Story User
Story
User
Story User
Story User
Story
Risk Risk Risk Risk
Wednesday, February 6, 13

115. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature Feature
User
Story User
Story User
Story User
Story User
Story User
Story User
Story
User
Story User
Story User
Story
Risk Risk Risk Risk
Wednesday, February 6, 13

116. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature Feature
User
Story User
Story User
Story User
Story User
Story User
Story User
Story
User
Story User
Story User
Story
Risk Risk Risk Risk Risk
Wednesday, February 6, 13

117. Release Spikes
Wednesday, February 6, 13

118. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature Feature
User
Story User
Story User
Story User
Story User
Story User
Story User
Story
User
Story User
Story User
Story
Spike Spike
Risk Risk Risk Risk Risk
Wednesday, February 6, 13

119. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature Feature
User
Story User
Story User
Story User
Story User
Story User
Story User
Story
User
Story User
Story User
Story
Spike
Spike Spike
Risk Risk Risk Risk Risk
Wednesday, February 6, 13

120. Budgeting vs. Estimating
Wednesday, February 6, 13

121. Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Epic Epic Epic Epic Epic Epic Epic Epic
Feature Feature Feature Feature Feature Feature Feature
User
Story User
Story User
Story User
Story User
Story User
Story User
Story
User
Story User
Story User
Story
Spike
Spike Spike
Risk Risk Risk Risk Risk
Wednesday, February 6, 13

122. Essential View #3
Flow
Wednesday, February 6, 13

123. Key Concepts
• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13

124. Key Concepts
• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13

125. Key Concepts
• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13

126. Key Concepts
• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13

127. Key Concepts
• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13

128. Key Concepts
• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13

129. n-Tier Model
Wednesday, February 6, 13

130. Enterprise Portfolio Model
Strategy Portfolio
Support
Team Team
Program Program
Team Team
Scrum Scrum Scrum Scrum
Team Team Team Team
Wednesday, February 6, 13

131. Story Backlog Task Backlog In Process Task Done Story Done
Tier 1 - Scrum
Wednesday, February 6, 13

132. Analysis Design Build Test Deploy
Tier 2 - Kanban
Story Backlog Task Backlog In Process Task Done Story Done
Tier 1 - Scrum
Wednesday, February 6, 13

133. Inception Elaboration Construction Transition
Tier 3 - Kanban
Analysis Design Build Test Deploy
Tier 2 - Kanban
Story Backlog Task Backlog In Process Task Done Story Done
Tier 1 - Scrum
Wednesday, February 6, 13

134. Epic
Feature Feature Feature Feature
User
Story User
Story User
Story User
Story
User
Story User
Story User
Story User
Story
User
Story User
Story User
Story User
Story
User
Story User
Story User
Story User
Story
Wednesday, February 6, 13

135. Inception Elaboration Construction Transition
Tier 3 - Kanban
Analysis Design Build Test Deploy
Tier 2 - Kanban
Story Backlog Task Backlog In Process Task Done Story Done
User Story
Tier 1 - Scrum
Wednesday, February 6, 13

136. Inception Elaboration Construction Transition
Tier 3 - Kanban
Analysis Design Build Test Deploy
Feature
Tier 2 - Kanban
Story Backlog Task Backlog In Process Task Done Story Done
User Story
Tier 1 - Scrum
Wednesday, February 6, 13

137. Inception Elaboration Construction Transition
Epic
Tier 3 - Kanban
Analysis Design Build Test Deploy
Feature
Tier 2 - Kanban
Story Backlog Task Backlog In Process Task Done Story Done
User Story
Tier 1 - Scrum
Wednesday, February 6, 13

138. Kanban creates a Pull System
across the entire portfolio that is
limited by your Actual Capacity
Wednesday, February 6, 13

139. Inception Elaboration Construction Transition
Epic
Epic
Analysis Design Build Test Deploy
Story Backlog Task Backlog In Process Task Done Story Backlog
Wednesday, February 6, 13

140. Inception Elaboration Construction Transition
Epic
Epic
Analysis Design Build Test Deploy
Story Backlog Task Backlog In Process Task Done Story Backlog
Wednesday, February 6, 13

141. Inception Elaboration Construction Transition
Epic
Epic
Analysis Design Build Test Deploy
Story Backlog Task Backlog In Process Task Done Story Backlog
Wednesday, February 6, 13

142. Inception Elaboration Construction Transition
Epic
Epic
Analysis Design Build Test Deploy
Feature
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Wednesday, February 6, 13

143. Inception Elaboration Construction Transition
Epic
Epic
Analysis Design Build Test Deploy
Feature
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Wednesday, February 6, 13

144. Inception Elaboration Construction Transition
Epic
Epic
Analysis Design Build Test Deploy
Feature
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Wednesday, February 6, 13

145. Inception Elaboration Construction Transition
Epic
Epic
Analysis Design Build Test Deploy
Feature
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Spike
Wednesday, February 6, 13

146. Inception Elaboration Construction Transition
Epic
Epic
Analysis Design Build Test Deploy
Feature
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Spike
User Story
User Story
Wednesday, February 6, 13

147. Inception Elaboration Construction Transition
Epic
Epic
Analysis Design Build Test Deploy
Feature
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Spike
User Story
User Story
Wednesday, February 6, 13

148. Inception Elaboration Construction Transition
Epic
Epic
Analysis Design Build Test Deploy
Feature
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
8 16
Task Task
Spike
User Story
8
User Story Task
Wednesday, February 6, 13

149. Inception Elaboration Construction Transition
Epic
Epic
Analysis Design Build Test Deploy
Feature Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
8 16
Task Task
Spike
User Story
8
User Story Task
Wednesday, February 6, 13

150. Inception Elaboration Construction Transition
Epic Epic
Analysis Design Build Test Deploy
Feature Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
8 16
Task Task
Spike
User Story
8
User Story Task
Wednesday, February 6, 13

151. Inception Elaboration Construction Transition
Epic Epic
Epic
Analysis Design Build Test Deploy
Feature
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
8 16
Task Task
Spike
User Story
8
User Story Task
Wednesday, February 6, 13

152. Inception Elaboration Construction Transition
Epic Epic
Epic
Analysis Design Build Test Deploy
Feature
Feature Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
8 16
Task Task
Spike
User Story
8
User Story Task
Wednesday, February 6, 13

153. Inception Elaboration Construction Transition
Epic Epic
Epic
Analysis Design Build Test Deploy
Feature
Feature Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
16
8 Task
Task
Spike
User Story
8
User Story Task
Wednesday, February 6, 13