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 ManagementBy Mike Cottmeyer, Agile CoachLeadingAgile, 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 objectiveshttp://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 InteractionsProcesses and Tools

8. The Agile Manifesto (2001)Individuals and InteractionsWorking software Processes and ToolsComprehensive documentation

9. The Agile Manifesto (2001)Individuals and InteractionsWorking software Customer collaborationProcesses and ToolsComprehensive documentationContract negotiation

10. The Agile Manifesto (2001)Individuals and InteractionsWorking software Customer collaborationResponding to changeProcesses and ToolsComprehensive documentationContract negotiationFollowing a plan

11. The Agile Manifesto (2001)Individuals and InteractionsWorking software Customer collaborationResponding to changeProcesses and ToolsComprehensive documentationContract negotiationFollowing a plan

12. The Agile Manifesto (2001)Individuals and InteractionsWorking software Customer collaborationResponding to changeProcesses and ToolsComprehensive documentationContract negotiationFollowing a plan

13. Challenging the Project Management Paradigm

14. The BIG Paradigm ShiftScopeCostTime

15. The BIG Paradigm ShiftCostTimeScope

16. The BIG Paradigm ShiftCostTimeReduceRiskScope

17. The BIG Paradigm ShiftCostTimeIncreaseValueScope

18. Is Your Project a Good Candidate for Agile?

19. Where to Use Agile?Sweet spot in software product developmentDomains where market requirements change oftenInitiatives where requirements are unknown or unknowableComplex knowledge work

20. Process ControlPredictive – Processes well defined and predictable. Process yields acceptable outcomesEmpirical – 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. TestersDevelopers

26. AnalystTestersDevelopers

27. AnalystCSMTestersDevelopers

28. Product OwnerAnalystCSMTestersDevelopers

29. Agile Process Flow…

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

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

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

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

34. Working ProductIs 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)I1I2I3I4I5I6I7I8I9

36. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

37. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

38. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

39. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

40. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

41. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

42. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

43. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

44. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

45. User StoryScreenUser StoryTeamUser StoryReportUser StoryUser StoryDatabaseUser StoryUser Story

46. User StoryScreenUser StoryTeamUser StoryReportUser StoryUser StoryDatabaseUser StoryUser Story

47. Agile Non-NegotiablesTeamsBacklogCadenceDone

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. EpicFeatures 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. EpicFeatures 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. FeatureUser 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 ValueEpicFeatureFeatureFeatureFeatureUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

53. INVESTIndependentNegotiableValuableEstimateableSmall… Sized AppropriatelyTestable

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

55. Epicsare decomposed into Features that describe the value added into the productEpicFeature

56. Epicsare decomposed into Features that describe the value added into the productEpicFeatureFeature

57. Epicsare decomposed into Features that describe the value added into the productEpicFeatureFeatureFeature

58. Epicsare decomposed into Features that describe the value added into the productEpicFeatureFeatureFeatureFeature

59. Featuresare decomposed into User Stories that are thin slices of value added into the systemEpicFeatureFeatureFeatureFeatureUser StoryUser StoryUser StoryUser Story

60. Featuresare decomposed into User Stories that are thin slices of value added into the systemEpicFeatureFeatureFeatureFeatureUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

61. Featuresare decomposed into User Stories that are thin slices of value added into the systemEpicFeatureFeatureFeatureFeatureUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

62. Featuresare decomposed into User Stories that are thin slices of value added into the systemEpicFeatureFeatureFeatureFeatureUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

63. Relative EstimationStart with something small and knowableGive it an arbitrary value of oneEstimate everything else relative to the original storyPlanning poker encourages communication and leads to shared understandingOver time becomes incredibly accurate

64. User Stories are estimated in relative units of measure called Story PointsEpic11FeatureFeatureFeatureFeature11User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

65. User Stories are estimated in relative units of measure called Story PointsEpic11FeatureFeatureFeatureFeature11User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

66. User Stories are estimated in relative units of measure called Story PointsEpic3121FeatureFeatureFeatureFeature323552321122User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

67. Story Points can be added up to size FeaturesEpic1178123121FeatureFeatureFeatureFeature323552321122User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

68. Feature Points can be added up to size Epics38Epic1178123121FeatureFeatureFeatureFeature323552321122User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser 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 Epic38Epic1178123121FeatureFeatureFeatureFeature323552321122User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

71. We continuously evaluate the Story Map to determine the Minimally Marketable Feature38Epic1178123121FeatureFeatureFeatureFeature323552321122User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

72. We continuously evaluate the Story Map to determine the Minimally Marketable Feature38Epic1178123121User StoryUser StoryUser StoryFeatureFeatureFeatureFeature3235User StoryUser StoryUser Story5232User StoryUser StoryUser Story1122User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

73. When we focus on Minimally Marketable Features, we deliver Business Value early26Epic104753121User StoryUser StoryUser StoryFeatureFeatureFeatureFeature3235User StoryUser StoryUser Story5232User StoryUser StoryUser Story1122User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser Story

74. Managing & Controlling Agile the Delivery Process

75. Minimally Marketable Featuresfeed the prioritization of our Sprint PlanningStory BacklogIn ProcessTask DoneTask BacklogStory Backlog

76. Identify the User Story most likely to contribute to the MMF and build that one firstStory BacklogIn ProcessTask DoneTask BacklogStory Backlog

77. Identify the User Story most likely to contribute to the MMF and build that one firstStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3User Story

78. Pull User Stories in priority order focusing on delivering complete MMFsStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3User Story

79. Pull User Stories in priority order focusing on delivering complete MMFsStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3User Story2User Story

80. It’s okay to work User Stories across MMFs if that is what the Product Owner needsStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3User Story2User Story

81. It’s okay to work User Stories across MMFs if that is what the Product Owner needsStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3User Story2User Story1User Story

82. The team uses its past velocity to determine how many stories go in the SprintPlanned Team Velocity = 6 pointsStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3User Story2User Story1User Story

83. The Team breaks each User Story down into TasksPlanned Team Velocity = 6 pointsStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3TaskTaskUser StoryTask2User Story1User Story

84. The Team breaks each User Story down into TasksPlanned Team Velocity = 6 pointsStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3TaskTaskUser StoryTask2TaskTaskUser StoryTaskTask1User Story

85. The Team breaks each User Story down into TasksPlanned Team Velocity = 6 pointsStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3TaskTaskUser StoryTask2TaskTaskUser StoryTaskTaskTaskTask1User StoryTaskTask

86. And estimates each Task in Real Hours so they can assess if they can make a solid Commitment to DeliverPlanned Team Velocity = 6 pointsStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3168TaskTaskUser Story8Task2TaskTaskUser StoryTaskTaskTaskTask1User StoryTaskTask

87. And estimates each Task in Real Hours so they can assess if they can make a solid Commitment to DeliverPlanned Team Velocity = 6 pointsStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3168TaskTaskUser Story8Task2216TaskTaskUser Story8Task4TaskTaskTask1User StoryTaskTask

88. And estimates each Task in Real Hours so they can assess if they can make a solid Commitment to DeliverPlanned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hoursStory BacklogIn ProcessTask DoneTask BacklogStory Backlog3168TaskTaskUser Story8Task2216TaskTaskUser Story8Task4Task84TaskTask1User Story168TaskTask

89. At the beginning of the Sprint, The Team pulls Tasks from the top of the Task BacklogPlanned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hoursStory BacklogIn ProcessTask DoneTask BacklogStory Backlog38TaskUser Story16Task8Task2216TaskTaskUser Story8Task4Task84TaskTask1User Story168TaskTask

90. Tasks move across the Story Board until there is a completed User Story. Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hoursStory BacklogIn ProcessTask DoneTask BacklogStory Backlog38TaskUser Story16Task8Task2216TaskTaskUser Story8Task4Task84TaskTask1User Story168TaskTask

91. Tasks move across the Story Board until there is a completed User Story. Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hoursStory BacklogIn ProcessTask DoneTask BacklogStory Backlog38TaskUser Story16Task8Task2216TaskTaskUser Story8Task4Task84TaskTask1User Story8Task16Task

92. Tasks move across the Story Board until there is a completed User Story. Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hoursStory BacklogIn ProcessTask DoneTask BacklogStory Backlog38TaskUser Story16Task8Task2216TaskTaskUser Story8Task4Task84TaskTask1User Story8Task16Task

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 pointsPlanned Estimated Hours = 98 hoursStory BacklogIn ProcessTask DoneTask BacklogStory Backlog38TaskUser Story16Task8Task2216TaskTaskUser Story8Task4Task84TaskTask1User Story8Task16Task

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 pointsPlanned Estimated Hours = 98 hoursStory BacklogIn ProcessTask DoneTask BacklogStory Backlog38TaskUser Story16Task8Task2216TaskTaskUser Story8Task4Task84TaskTask1User Story8Task16Task

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 pointsPlanned Estimated Hours = 98 hoursStory BacklogIn ProcessTask DoneTask BacklogStory Backlog38TaskUser Story16Task8Task2216TaskTaskUser Story8Task4Task84TaskTask1User Story8Task16Task

96. Until the entire Sprint has been delivered to the Product Owner. Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hoursStory BacklogIn ProcessTask DoneTask BacklogStory Backlog38TaskUser Story16Task8Task2216TaskTaskUser Story8Task4Task184TaskUser StoryTask8Task16Task

97. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38966Release BurndownSprint BurndownVelocity Trend

98. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38966Release BurndownSprint BurndownVelocity Trend

99. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38966Release BurndownSprint BurndownVelocity Trend

100. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38966Release BurndownSprint BurndownVelocity Trend

101. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38966Release BurndownSprint BurndownVelocity Trend

102. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38966Release BurndownSprint BurndownVelocity Trend

103. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38966Release BurndownSprint BurndownVelocity Trend

104. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38966Release BurndownSprint BurndownVelocity Trend

105. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38966Release BurndownSprint BurndownVelocity Trend

106. From a Metrics perspective, we Burn Down points to make sure the Release is on track389666Release BurndownSprint BurndownVelocity Trend

107. From a Metrics perspective, we Burn Down points to make sure the Release is on track3896866Release BurndownSprint BurndownVelocity Trend

108. We track Velocity Trend to make sure the team is delivering in a Predictable manner38968665Release BurndownSprint BurndownVelocity 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. 38968665Release BurndownSprint BurndownVelocity 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!38968665Release BurndownSprint BurndownVelocity Trend

111. Predicting the Future… Agile Fortune Telling

112. Yesterday’s WeatherPast performance is our best indicator of future performanceThe 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 iterationThe same goes for releases

113. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

114. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

115. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

116. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

117. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

118. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

119. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

120. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

121. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

122. Project (years)Release (months)Release (months)Release (months)I1I2I3I4I5I6I7I8I9

123. Team Level Release PlanningUse past velocity to determine roughly how much content can fit into the upcoming releaseVary 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 PlanningUse past velocity to determine roughly how much content can fit into the upcoming releaseVary 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 teamsReduces 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 1Team 2

153. Team 1Team 2Team 3

154. Team 1Team 2Team 3Team 4

155. Team 1Team 2Team 3Team 4Team 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 levelEpic

158. Team predictability is one thing, but organizations need to be able to track value at the Epic levelEpicWe 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 levelEpicWe need a mechanism to make sure features that span multiple Scrum teams are treated with the same sense of awareness as single-product features. FeatureAll of our day-to-day activities need to clearly map to enterprise objectives. We need to build product as one organizationUser Story

160. Story BacklogIn ProcessTask DoneTask BacklogStory BacklogTier 1 - Scrum

161. DeployBuild Test DesignAnalysisTier 2 - KanbanStory BacklogIn ProcessTask DoneTask BacklogStory BacklogTier 1 - Scrum

162. ConstructionTransitionElaborationInceptionTier 3 - KanbanDeployBuild Test DesignAnalysisTier 2 - KanbanStory BacklogIn ProcessTask DoneTask BacklogStory BacklogTier 1 - Scrum

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

164. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisStory BacklogIn ProcessTask DoneTask BacklogStory Backlog

165. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisStory BacklogIn ProcessTask DoneTask BacklogStory Backlog

166. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog

167. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog

168. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory BacklogSpike

169. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory BacklogUser StoryUser StorySpike

170. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog168TaskTaskUser StoryUser StorySpike8Task

171. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog168TaskTaskUser StoryUser StorySpike8Task

172. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog168TaskTaskUser StoryUser StorySpike8Task

173. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog168TaskTaskUser StoryUser StorySpike8Task

174. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog168TaskTaskUser StoryUser StorySpike8Task

175. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog168TaskTaskUser StoryUser StorySpike8Task

176. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog168TaskTaskUser StoryUser StorySpike8Task

177. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog168TaskTaskUser StoryUser StorySpike8Task

178. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog168TaskTaskUser StoryUser StorySpike8Task

179. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog168TaskTaskUser StoryUser StorySpike8Task

180. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16Task8User StoryUser StoryTaskSpike8Task

181. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16Task8User StoryUser StoryTaskSpike8Task

182. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16Task8User StoryUser StoryTaskSpike8Task

183. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16Task8User StoryUser StoryTaskSpike8Task

184. ConstructionTransitionElaborationInceptionEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16Task8User StoryUser StoryTaskSpike8Task

185. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16TaskUser StoryUser Story8TaskSpike8Task

186. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16TaskUser StoryUser Story8TaskSpike8Task

187. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16TaskUser StoryUser Story8TaskSpike8Task

188. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16Task8TaskUser StoryUser StorySpike8Task

189. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16TaskUser StoryUser StorySpike8Task8Task

190. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16TaskUser StoryUser StorySpike8Task8Task

191. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16TaskTaskUser StoryUser StoryUser StoryUser Story8TaskSpikeSpike8Task88TaskTask

192. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog16TaskUser StoryUser StoryUser StoryUser StorySpikeSpike8Task8Task

193. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog8TaskUser StoryUser Story8TaskSpike8Task

194. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog8TaskUser StoryUser Story8TaskSpike8Task

195. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog8TaskUser StoryUser Story8TaskSpike8Task

196. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog8TaskUser StoryUser Story8TaskSpike8Task

197. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog8Task8User StoryUser StoryTaskSpike8Task

198. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog8Task8User StoryUser StoryTaskSpike8Task

199. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog8Task8User StoryUser StoryTaskSpike8Task

200. ConstructionTransitionElaborationInceptionEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog8Task8User StoryUser StoryTaskSpike8Task

201. ConstructionTransitionElaborationInceptionEpicEpicEpicEpicDeployBuild Test DesignAnalysisFeatureFeatureFeatureFeatureFeatureFeatureStory BacklogIn ProcessTask DoneTask BacklogStory Backlog88TaskTaskTask8User StoryUser StoryUser StoryUser Story8TaskTaskSpikeSpike888TaskTaskTask

202. At the team level, velocity metrics drive predictability38968665Release BurndownSprint BurndownVelocity Trend

203. At the program/product level, lean metrics are more meaningfulAt the team level, velocity metrics drive predictability38968665Release BurndownSprint BurndownVelocity Trend

204. At the enterprise level, lean metrics are also the more interesting metricAt the program/product level, lean metrics are more meaningfulAt the team level, velocity metrics drive predictability38968665Release BurndownSprint BurndownVelocity Trend

205. Enterprise Release PlanningUse Scrum at the team level to drive predictable outcomesBalance the backlogs across team to optimize the flow of value at the Feature and Epic levelUse 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 PeopleClear the path, enable the teams and the organizationDrive shared understanding of delivery riskSystems thinking, look out for the whole

207. Agile Project ManagerTeamPMTeamTeamTeamTeamTeamTeamTeamAPM

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