This document provides an introduction to agile planning and project management. It defines key concepts like projects, project managers, and project management. It discusses the agile manifesto and values like individuals and interactions, working software, customer collaboration, and responding to change. It also covers agile processes like product vision, product backlog, iteration backlog, and feedback loops. The document discusses when agile is a good fit and compares predictive and empirical processes. It outlines fundamentals of team-based agile like roles, estimating techniques like story points, and managing the delivery process.

1. Introduction to Agile Planning and Project Management By Mike Cottmeyer, Agile Coach LeadingAgile, LLC

2. Mike CottmeyerLeadingAgilemike@leadingagile.com 1.404.312.1471www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyer

3. A Project is a temporary endeavor, having a defined beginning and end, undertaken to meet unique goals and objectives http://en.wikipedia.org/wiki/Project_management

4. A Project Manager is a professional in the field of project management. Project Managers have the responsibility of planning, execution, and closing of any project. http://en.wikipedia.org/wiki/Project_manager

5. Project Management is the discipline of planning, organizing, securing and managing resources to bring about the successful completion of specific project goals and objectives. http://en.wikipedia.org/wiki/Project_management

6. Agile Values & Principles

7. The Agile Manifesto (2001) Individuals and Interactions Processes and Tools

8. The Agile Manifesto (2001) Individuals and Interactions Working software Processes and Tools Comprehensive documentation

9. The Agile Manifesto (2001) Individuals and Interactions Working software Customer collaboration Processes and Tools Comprehensive documentation Contract negotiation

10. The Agile Manifesto (2001) Individuals and Interactions Working software Customer collaboration Responding to change Processes and Tools Comprehensive documentation Contract negotiation Following a plan

11. The Agile Manifesto (2001) Individuals and Interactions Working software Customer collaboration Responding to change Processes and Tools Comprehensive documentation Contract negotiation Following a plan

12. The Agile Manifesto (2001) Individuals and Interactions Working software Customer collaboration Responding to change Processes and Tools Comprehensive documentation Contract negotiation Following a plan

13. Challenging the Project Management Paradigm

14. The BIG Paradigm Shift Scope Cost Time

15. The BIG Paradigm Shift Cost Time Scope

16. The BIG Paradigm Shift Cost Time Reduce Risk Scope

17. The BIG Paradigm Shift Cost Time IncreaseValue Scope

18. Is Your Project a Good Candidate for Agile?

19. Where to Use Agile? Sweet spot in software product development Domains where market requirements change often Initiatives where requirements are unknown or unknowable Complex knowledge work

20. Process Control Predictive – Processes well defined and predictable. Process yields acceptable outcomes Empirical – Frequently measure outcomes and adapt the process to accommodate variation

21. Emergence or Convergence

22. Fundamentals of Team Based Agile

23. Team

24. Developers

25. Testers Developers

26. Analyst Testers Developers

27. Analyst CSM Testers Developers

28. Product Owner Analyst CSM Testers Developers

29. Agile Process Flow…

30. Product Vision Understanding why we are doing what we are doing, who it is for, and the overall market opportunity

31. Product Backlog The master list of things that we want to build into the product

32. Iteration Backlog The highest priority items that we intend to build in the next 2-4 weeks

33. Feedback Loops Inspect and adapt on regular cadences to mitigate delivery risk

34. Working Product Is the primary measure of progress, at the end of each time-box we have a deliverable

35. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

36. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

37. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

38. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

39. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

40. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

41. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

42. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

43. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

44. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

45. User Story Screen User Story Team User Story Report User Story User Story Database User Story User Story

46. User Story Screen User Story Team User Story Report User Story User Story Database User Story User Story

47. Agile Non-Negotiables Teams Backlog Cadence Done

48. My Customer Doesn’t Give a Crap About User Stories!

49. Epics collections of features, typically 1-3 months in duration. Epics span releases. Epics can span more than one team. These are the things the market cares about. Epic

50. Epics collections of features, typically 1-3 months in duration. Epics span releases. Epics can span more than one team. These are the things the market cares about. Epic Features are smaller than epics, typically 2-4 weeks in duration. Features are contained within releases. Ideally, features are contained within a team. These are what the Product Owner Cares about. Feature

51. Epics collections of features, typically 1-3 months in duration. Epics span releases. Epics can span more than one team. These are the things the market cares about. Epic Features are smaller than epics, typically 2-4 weeks in duration. Features are contained within releases. Ideally, features are contained within a team. These are what the Product Owner Cares about. Feature User Stories are the smallest increment of value, typically less than a week. User Stories are contained within sprint. These are the things Engineering Management Cares about. User Story

52. Story Maps visually show the relationship between User Stories and Business Value 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

53. INVEST Independent Negotiable Valuable Estimateable Small… Sized Appropriately Testable

54. Story Maps start with the identification of larger, more strategic organizational goals Epic

55. Epicsare decomposed into Features that describe the value added into the product Epic Feature

56. Epicsare decomposed into Features that describe the value added into the product Epic Feature Feature

57. Epicsare decomposed into Features that describe the value added into the product Epic Feature Feature Feature

58. Epicsare decomposed into Features that describe the value added into the product Epic Feature Feature Feature Feature

59. Featuresare decomposed into User Stories that are thin slices of value added into the system Epic Feature Feature Feature Feature User Story User Story User Story User Story

60. Featuresare decomposed into User Stories that are thin slices of value added into the system Epic Feature Feature Feature Feature User Story User Story User Story User Story User Story User Story User Story User Story

61. Featuresare decomposed into User Stories that are thin slices of value added into the system 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

62. Featuresare decomposed into User Stories that are thin slices of value added into the system 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

63. Relative Estimation Start with something small and knowable Give it an arbitrary value of one Estimate everything else relative to the original story Planning poker encourages communication and leads to shared understanding Over time becomes incredibly accurate

64. User Stories are estimated in relative units of measure called Story Points Epic 1 1 Feature Feature Feature Feature 1 1 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

65. User Stories are estimated in relative units of measure called Story Points Epic 1 1 Feature Feature Feature Feature 1 1 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

66. User Stories are estimated in relative units of measure called Story Points Epic 3 1 2 1 Feature Feature Feature Feature 3 2 3 5 5 2 3 2 1 1 2 2 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

67. Story Points can be added up to size Features Epic 11 7 8 12 3 1 2 1 Feature Feature Feature Feature 3 2 3 5 5 2 3 2 1 1 2 2 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

68. Feature Points can be added up to size Epics 38 Epic 11 7 8 12 3 1 2 1 Feature Feature Feature Feature 3 2 3 5 5 2 3 2 1 1 2 2 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

69. Varying Scope Using the Minimally Marketable Feature

70. Our Goal is to build the smallest system possible to deliver the value in the Epic 38 Epic 11 7 8 12 3 1 2 1 Feature Feature Feature Feature 3 2 3 5 5 2 3 2 1 1 2 2 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

71. We continuously evaluate the Story Map to determine the Minimally Marketable Feature 38 Epic 11 7 8 12 3 1 2 1 Feature Feature Feature Feature 3 2 3 5 5 2 3 2 1 1 2 2 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

72. We continuously evaluate the Story Map to determine the Minimally Marketable Feature 38 Epic 11 7 8 12 3 1 2 1 User Story User Story User Story Feature Feature Feature Feature 3 2 3 5 User Story User Story User Story 5 2 3 2 User Story User Story User Story 1 1 2 2 User Story User Story User Story User Story User Story User Story User Story

73. When we focus on Minimally Marketable Features, we deliver Business Value early 26 Epic 10 4 7 5 3 1 2 1 User Story User Story User Story Feature Feature Feature Feature 3 2 3 5 User Story User Story User Story 5 2 3 2 User Story User Story User Story 1 1 2 2 User Story User Story User Story User Story User Story User Story User Story

74. Managing & Controlling Agile the Delivery Process

75. Minimally Marketable Featuresfeed the prioritization of our Sprint Planning Story Backlog In Process Task Done Task Backlog Story Backlog

76. Identify the User Story most likely to contribute to the MMF and build that one first Story Backlog In Process Task Done Task Backlog Story Backlog

77. Identify the User Story most likely to contribute to the MMF and build that one first Story Backlog In Process Task Done Task Backlog Story Backlog 3 User Story

78. Pull User Stories in priority order focusing on delivering complete MMFs Story Backlog In Process Task Done Task Backlog Story Backlog 3 User Story

79. Pull User Stories in priority order focusing on delivering complete MMFs Story Backlog In Process Task Done Task Backlog Story Backlog 3 User Story 2 User Story

80. It’s okay to work User Stories across MMFs if that is what the Product Owner needs Story Backlog In Process Task Done Task Backlog Story Backlog 3 User Story 2 User Story

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

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

83. The Team breaks each User Story down into Tasks Planned Team Velocity = 6 points Story Backlog In Process Task Done Task Backlog Story Backlog 3 Task Task User Story Task 2 User Story 1 User Story

84. The Team breaks each User Story down into Tasks Planned Team Velocity = 6 points Story Backlog In Process Task Done Task Backlog Story Backlog 3 Task Task User Story Task 2 Task Task User Story Task Task 1 User Story

85. The Team breaks each User Story down into Tasks Planned Team Velocity = 6 points Story Backlog In Process Task Done Task Backlog Story Backlog 3 Task Task User Story Task 2 Task Task User Story Task Task Task Task 1 User Story Task Task

86. And estimates 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 In Process Task Done Task Backlog Story Backlog 3 16 8 Task Task User Story 8 Task 2 Task Task User Story Task Task Task Task 1 User Story Task Task

87. And estimates 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 In Process Task Done Task Backlog Story Backlog 3 16 8 Task Task User Story 8 Task 2 2 16 Task Task User Story 8 Task 4 Task Task Task 1 User Story Task Task

88. And estimates each Task in Real Hours so they can assess if they can make a solid Commitment to Deliver Planned Team Velocity = 6 points Planned Estimated Hours = 98 hours Story Backlog In Process Task Done Task Backlog Story Backlog 3 16 8 Task Task User Story 8 Task 2 2 16 Task Task User Story 8 Task 4 Task 8 4 Task Task 1 User Story 16 8 Task Task

89. At the beginning of the Sprint, The Team pulls Tasks from the top of the Task Backlog Planned Team Velocity = 6 points Planned Estimated Hours = 98 hours Story Backlog In Process Task Done Task Backlog Story Backlog 3 8 Task User Story 16 Task 8 Task 2 2 16 Task Task User Story 8 Task 4 Task 8 4 Task Task 1 User Story 16 8 Task Task

90. Tasks move across the Story Board until there is a completed User Story. Planned Team Velocity = 6 points Planned Estimated Hours = 98 hours Story Backlog In Process Task Done Task Backlog Story Backlog 3 8 Task User Story 16 Task 8 Task 2 2 16 Task Task User Story 8 Task 4 Task 8 4 Task Task 1 User Story 16 8 Task Task

91. Tasks move across the Story Board until there is a completed User Story. Planned Team Velocity = 6 points Planned Estimated Hours = 98 hours Story Backlog In Process Task Done Task Backlog Story Backlog 3 8 Task User Story 16 Task 8 Task 2 2 16 Task Task User Story 8 Task 4 Task 8 4 Task Task 1 User Story 8 Task 16 Task

92. Tasks move across the Story Board until there is a completed User Story. Planned Team Velocity = 6 points Planned Estimated Hours = 98 hours Story Backlog In Process Task Done Task Backlog Story Backlog 3 8 Task User Story 16 Task 8 Task 2 2 16 Task Task User Story 8 Task 4 Task 8 4 Task Task 1 User Story 8 Task 16 Task

93. 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 Estimated Hours = 98 hours Story Backlog In Process Task Done Task Backlog Story Backlog 3 8 Task User Story 16 Task 8 Task 2 2 16 Task Task User Story 8 Task 4 Task 8 4 Task Task 1 User Story 8 Task 16 Task

94. 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 Estimated Hours = 98 hours Story Backlog In Process Task Done Task Backlog Story Backlog 3 8 Task User Story 16 Task 8 Task 2 2 16 Task Task User Story 8 Task 4 Task 8 4 Task Task 1 User Story 8 Task 16 Task

95. 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 Estimated Hours = 98 hours Story Backlog In Process Task Done Task Backlog Story Backlog 3 8 Task User Story 16 Task 8 Task 2 2 16 Task Task User Story 8 Task 4 Task 8 4 Task Task 1 User Story 8 Task 16 Task

96. Until the entire Sprint has been delivered to the Product Owner. Planned Team Velocity = 6 points Planned Estimated Hours = 98 hours Story Backlog In Process Task Done Task Backlog Story Backlog 3 8 Task User Story 16 Task 8 Task 2 2 16 Task Task User Story 8 Task 4 Task 1 8 4 Task User Story Task 8 Task 16 Task

97. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track 38 96 6 Release Burndown Sprint Burndown Velocity Trend

98. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track 38 96 6 Release Burndown Sprint Burndown Velocity Trend

99. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track 38 96 6 Release Burndown Sprint Burndown Velocity Trend

100. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track 38 96 6 Release Burndown Sprint Burndown Velocity Trend

101. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track 38 96 6 Release Burndown Sprint Burndown Velocity Trend

102. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track 38 96 6 Release Burndown Sprint Burndown Velocity Trend

103. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track 38 96 6 Release Burndown Sprint Burndown Velocity Trend

104. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track 38 96 6 Release Burndown Sprint Burndown Velocity Trend

105. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track 38 96 6 Release Burndown Sprint Burndown Velocity Trend

106. From a Metrics perspective, we Burn Down points to make sure the Release is on track 38 96 6 6 Release Burndown Sprint Burndown Velocity Trend

107. From a Metrics perspective, we Burn Down points to make sure the Release is on track 38 96 8 6 6 Release Burndown Sprint Burndown Velocity Trend

108. 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

109. 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

110. 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 often! 38 96 8 6 6 5 Release Burndown Sprint Burndown Velocity Trend

111. Predicting the Future… Agile Fortune Telling

112. Yesterday’s Weather Past performance is our best indicator of future performance The amount of product we were able to build during the last iteration, is a pretty good indicator of what we’ll be able to deliver this iteration The same goes for releases

113. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

114. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

115. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

116. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

117. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

118. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

119. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

120. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

121. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

122. Project (years) Release (months) Release (months) Release (months) I1 I2 I3 I4 I5 I6 I7 I8 I9

123. Team Level Release Planning Use past velocity to determine roughly how much content can fit into the upcoming release Vary scope by focusing on the MMF to fine tune the implementation as you build the emerging product

124. Agile Project Management in Larger, More Complex Enterprises

125. Agile in the Enterprise

126. Agile in the Enterprise

127. Enterprise Agile

128. Enterprise Agile... it’s different!

129. Enterprise Agile

130. Enterprise Agile

131. Enterprise Agile

132. Enterprise Agile

133. Enterprise Agile

134. Enterprise Agile

135. Enterprise Agile

136. Multi-Team Release Planning Use past velocity to determine roughly how much content can fit into the upcoming release Vary scope by focusing on the MMF to fine tune the implementation as you build the emerging product Sequence backlogs so deliverables are coordinated across agile teams Reduces business agility

137. Let’s Talk About the Stuff That Breaks Agile

138. External Dependencies

139. External Dependencies

140. External Dependencies

141. Many-to-Many Relationships

142. Many-to-Many Relationships

143. Many-to-Many Relationships

144. Many-to-Many Relationships

145. Many-to-Many Relationships

146. Many-to-Many Relationships

147. Many-to-Many Relationships

148. Many-to-Many Relationships

149. Many-to-Many Relationships

150. Agile Project, Program, and Portfolio Management using Lean, Kanban, and TOC

151. Team 1

152. Team 1 Team 2

153. Team 1 Team 2 Team 3

154. Team 1 Team 2 Team 3 Team 4

155. Team 1 Team 2 Team 3 Team 4 Team 5

156. Establishing the relationship between team level velocity and enterprise level throughput?

157. Team predictability is one thing, but organizations need to be able to track value at the Epic level Epic

158. Team predictability is one thing, but organizations need to be able to track value at the Epic level Epic We need a mechanism to make sure features that span multiple Scrum teams are treated with the same sense of awareness as single-product features. Feature

159. Team predictability is one thing, but organizations need to be able to track value at the Epic level Epic We need a mechanism to make sure features that span multiple Scrum teams are treated with the same sense of awareness as single-product features. Feature All of our day-to-day activities need to clearly map to enterprise objectives. We need to build product as one organization User Story

160. Story Backlog In Process Task Done Task Backlog Story Backlog Tier 1 - Scrum

161. Deploy Build Test Design Analysis Tier 2 - Kanban Story Backlog In Process Task Done Task Backlog Story Backlog Tier 1 - Scrum

162. Construction Transition Elaboration Inception Tier 3 - Kanban Deploy Build Test Design Analysis Tier 2 - Kanban Story Backlog In Process Task Done Task Backlog Story Backlog Tier 1 - Scrum

163. Kanban creates a pull system across the entire portfolio that is limited by your actual capacity

164. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Story Backlog In Process Task Done Task Backlog Story Backlog

165. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Story Backlog In Process Task Done Task Backlog Story Backlog

166. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog

167. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog

168. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog Spike

169. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog User Story User Story Spike

170. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 8 Task Task User Story User Story Spike 8 Task

171. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 8 Task Task User Story User Story Spike 8 Task

172. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 8 Task Task User Story User Story Spike 8 Task

173. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 8 Task Task User Story User Story Spike 8 Task

174. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 8 Task Task User Story User Story Spike 8 Task

175. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 8 Task Task User Story User Story Spike 8 Task

176. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 8 Task Task User Story User Story Spike 8 Task

177. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 8 Task Task User Story User Story Spike 8 Task

178. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 8 Task Task User Story User Story Spike 8 Task

179. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 8 Task Task User Story User Story Spike 8 Task

180. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task 8 User Story User Story Task Spike 8 Task

181. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task 8 User Story User Story Task Spike 8 Task

182. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task 8 User Story User Story Task Spike 8 Task

183. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task 8 User Story User Story Task Spike 8 Task

184. Construction Transition Elaboration Inception Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task 8 User Story User Story Task Spike 8 Task

185. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task User Story User Story 8 Task Spike 8 Task

186. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task User Story User Story 8 Task Spike 8 Task

187. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task User Story User Story 8 Task Spike 8 Task

188. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task 8 Task User Story User Story Spike 8 Task

189. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task User Story User Story Spike 8 Task 8 Task

190. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task User Story User Story Spike 8 Task 8 Task

191. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task Task User Story User Story User Story User Story 8 Task Spike Spike 8 Task 8 8 Task Task

192. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 16 Task User Story User Story User Story User Story Spike Spike 8 Task 8 Task

193. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 8 Task User Story User Story 8 Task Spike 8 Task

194. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 8 Task User Story User Story 8 Task Spike 8 Task

195. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 8 Task User Story User Story 8 Task Spike 8 Task

196. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 8 Task User Story User Story 8 Task Spike 8 Task

197. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 8 Task 8 User Story User Story Task Spike 8 Task

198. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 8 Task 8 User Story User Story Task Spike 8 Task

199. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 8 Task 8 User Story User Story Task Spike 8 Task

200. Construction Transition Elaboration Inception Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 8 Task 8 User Story User Story Task Spike 8 Task

201. Construction Transition Elaboration Inception Epic Epic Epic Epic Deploy Build Test Design Analysis Feature Feature Feature Feature Feature Feature Story Backlog In Process Task Done Task Backlog Story Backlog 8 8 Task Task Task 8 User Story User Story User Story User Story 8 Task Task Spike Spike 8 8 8 Task Task Task

202. At the team level, velocity metrics drive predictability 38 96 8 6 6 5 Release Burndown Sprint Burndown Velocity Trend

203. At the program/product level, lean metrics are more meaningful At the team level, velocity metrics drive predictability 38 96 8 6 6 5 Release Burndown Sprint Burndown Velocity Trend

204. At the enterprise level, lean metrics are also the more interesting metric At the program/product level, lean metrics are more meaningful At the team level, velocity metrics drive predictability 38 96 8 6 6 5 Release Burndown Sprint Burndown Velocity Trend

205. Enterprise Release Planning Use Scrum at the team level to drive predictable outcomes Balance the backlogs across team to optimize the flow of value at the Feature and Epic level Use metrics to plan the number of Features and Epics that can be included in a release

206. Agile Project Managers Manage the System, not the People Clear the path, enable the teams and the organization Drive shared understanding of delivery risk Systems thinking, look out for the whole

207. Agile Project Manager Team PM Team Team Team Team Team Team Team APM

208. Mike CottmeyerLeadingAgilemike@leadingagile.com 1.404.312.1471www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyer