Theses are the slides from the scrum Workshop at Accenture's PMO in Amsterdam, January the 5th 2011.

1. Introduction to Project Management with Scrum 1 Scrum@ AccentureTechnology Solutions | PCS

2. Who am I? Scrum@ Accenture Technology Solutions | PCS PMO │ Scrum Coach @ coPROcess S.A. www.coprocess.lu http://managingagile.blogspot.com/ http://paper.li/elPedroMajor 2

3. About this Workshop Scrum@ Accenture Technology Solutions | PCS 3

5. Explain the basic principles

6. Introducing Scrum Training possibilitiesScrum@ Accenture Technology Solutions | PCS 4

7. The Process !!! Scrum@ Accenture Technology Solutions | PCS 5

8. Inspect & Adapt 3 questions: Whoam I? What’smy job? Whataimstoday? Scrum@ Accenture Technology Solutions | PCS 6

9. Introduction to Scrum Scrum@ Accenture Technology Solutions | PCS 7

10. 8 Scrum@ Accenture Technology Solutions | PCS Why “Scrum” ?

11. We’re losing the relay race “The… ‘relay race’ approach to product development…may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‘rugby’ approach—where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today’s competitive requirements.” Hirotaka Takeuchi and Ikujiro Nonaka, “The New New Product Development Game”, Harvard Business Review, January 1986 9 Scrum@ Accenture Technology Solutions | PCS

12. Origins Scrum@ Accenture Technology Solutions | PCS 10

13. The Manifesto for Agile Software Development 2001 Scrum@ Accenture Technology Solutions | PCS 11

15. Scrum is a framework within which the game of product development is played.

16. Your team plays and how good or not-good it is becomes highly visible.

17. Your team gets to continuously improves itself.Scrum@ Accenture Technology Solutions | PCS 12

18. 13 Scrum@ Accenture Technology Solutions | PCS How?

20. Originally Scrum has been formalized for software development. But it also works well for complex and innovative projects.

21. The Scrum framework is deceptively simple.14 Scrum@ Accenture Technology Solutions | PCS

22. The Theory Scrum@ Accenture Technology Solutions | PCS 15

24. During the Sprint Planning, the Team “pulls” a piece of the top of that list: the Sprint Backlog; and decide how to implement it.

25. The Team has a time-box to reach this goal: the Sprint❶ 16 Scrum@ Accenture Technology Solutions | PCS

27. During the whole project, the ScrumMaster ensuresthat the Team is still focused on its objective.

28. At the end of the Sprint, the work has to be potentialy shipable. This work is considered as done.❷ 17 Scrum@ Accenture Technology Solutions | PCS

30. When the next Sprint starts, the Team selects a newpieceoftheProductBacklogandrestartstheprocess.

31. The processisdonewhen all Features areimplemented, orthebudgetisconsummed, orwhenthe time isover.❸ 18 Scrum@ Accenture Technology Solutions | PCS

32. Objective Maximize Value 19 Scrum@ Accenture Technology Solutions | PCS

33. Scrum Roles 20 Scrum@ Accenture Technology Solutions | PCS

34. Pigs & Chicken 21 Scrum@ Accenture Technology Solutions | PCS

35. ❶ The Scrum Team 22 Scrum@ Accenture Technology Solutions | PCS

36. 23 Scrum@ Accenture Technology Solutions | PCS ❷ The Team

37. Self-Managed-Team vs. Traditional Organisation 24 Scrum@ Accenture Technology Solutions | PCS

39. Helps

40. Coaches

41. Protects

42. Removes

43. Responsible

44. Workwith25 Scrum@ Accenture Technology Solutions | PCS

46. Ensures

47. Accepts

48. Rejects

49. Maintains

50. Work with26 Scrum@ Accenture Technology Solutions | PCS

51. Cycle of Ceremonies 27 Scrum@ Accenture Technology Solutions | PCS

52. Ceremonies are time-boxed. Sprint Planning Sprint Review Retrospective Sprint Planning Daily Meetings SPRINT 28 Scrum@ Accenture Technology Solutions | PCS

53. ❶ Sprint Planning Meeting 29 Scrum@ Accenture Technology Solutions | PCS

54. 30 Scrum@ Accenture Technology Solutions | PCS The “Pull” Principle

56. Sprint Planning 1: the WHAT?

57. Sprint Planning 2: the HOW?

58. Product Owner:

59. Provides the customer ‘s/ user’s prioritized product backlog

60. Presents the Release Plan.

61. Explain theVision

62. Team:

63. Estimates the Product Backlog in terms of feasibility (functional estimation)

64. Slice the Product Backlog to Sprint Backlogs with Product Owner

65. Slice Sprint Backlog in Tasks

66. Team and Product Owner:

67. Define the Sprint objective

68. Establish “Definition of Done” for the Sprint.

69. Moderator: Product Owner

70. Participators: Team (active), ScrumMaster (passive)

71. Duration: 8 Hours for a 4 week Sprint31 Scrum@ Accenture Technology Solutions | PCS

72. ❷Sprint 32 Scrum@ Accenture Technology Solutions | PCS

74. Maintenance of the Level of Done:

75. Developement

76. Unit test

77. Acceptance

78. Integrations test

79. System tests

80. Performance

81. Co-management of impediments with the ScrumMaster.

82. Co-maintenance of the Sprint Backlog with Product Owner.

83. Moderator: Team

84. Participators : Team, ScrumMaster, Product Owner

85. Duration: 2-4 Weeks33 Scrum@ Accenture Technology Solutions | PCS

86. ❸ Daily Scrum 34 Scrum@ Accenture Technology Solutions | PCS

89. Participators : Team (active), ScrumMaster (passive), Product Owner (passive)

90. Duration: 15 min35 Scrum@ Accenture Technology Solutions | PCS

91. ❹Sprint Review 36 Scrum@ Accenture Technology Solutions | PCS

93. The team presents the results of the Sprint.

94. Users/Customer/ Management express their comments and find a compromise with the team.

95. The ProductOwneracceptsorrejects Sprint Backlog Items accordingto Definition ofDone.

96. The Product Owner has the last word here.

97. Moderator: Product Owner

98. Participators: Team (active), ScrumMaster (passive), Management (active), Customer (active), Users (active)

99. Duration: 4 Hours for a 4 week Sprint.37 Scrum@ Accenture Technology Solutions | PCS

100. ❺Retrospective 38 Scrum@ Accenture Technology Solutions | PCS

102. How

103. How can we improve ourselves?

104. Inspection priorities :

105. Team communication

106. Relationshipbetweenteammembers

107. Processes and Tools

108. Training issues

109. etc

110. Moderator: ScrumMaster

111. Participators: Team (active), ScrumMaster (active), Product Owner (active als Scrum Team Member)

112. Duration: 3 Hours for a 4 week Sprint.39 Scrum@ Accenture Technology Solutions | PCS

113. Artifacts 40 Scrum@ Accenture Technology Solutions | PCS

115. Release Burndown 42 Scrum@ Accenture Technology Solutions | PCS

116. Sprint Backlog 43 Scrum@ Accenture Technology Solutions | PCS

117. Sprint Burndown Scrum@ Accenture Technology Solutions | PCS 44

118. Definition of Done 45 Scrum@ Accenture Technology Solutions | PCS

120. Code is

121. proper

122. Re-factored

123. Unit tested

124. checked in

125. built

126. Has a number of applied unit tests.

127. To achieve this, the development environment is constituted by :

128. A Source-Code Library

129. Codes Standards

130. Automatic Build

131. A Unit-tests Environment46 Scrum@ Accenture Technology Solutions | PCS

133. Sprint/Iteration is “done” when

134. All items are “done”

135. When the Sprint reaches its goal.

136. And when Acceptance criteria are met.

137. Release is “done”

138. “done” for Integration

139. “done” for Production47 Scrum@ Accenture Technology Solutions | PCS

141. Scrum Values Scrum@ Accenture Technology Solutions | PCS 49

142. Tranparence Transparence Inspection Adaptation 50 Scrum@ Accenture Technology Solutions | PCS

143. Scrum@ Accenture Technology Solutions | PCS Inspection 51

144. Scrum@ Accenture Technology Solutions | PCS Adaptation 52

145. In fact, how does it work? 53 Scrum@ Accenture Technology Solutions | PCS

146. First an idea 54 Scrum@ Accenture Technology Solutions | PCS

147. Then a Vision 55 Scrum@ Accenture Technology Solutions | PCS

148. The Vision 56 Scrum@ Accenture Technology Solutions | PCS

149. Then a Product Backlog 57 Scrum@ Accenture Technology Solutions | PCS

150. Product Backlog High priority Sprint Medium Priority Release Future Releases Scrum@ Accenture Technology Solutions | PCS 58

151. Product Backlog - Examples Scrum@ Accenture Technology Solutions | PCS 59

152. Then build the Team Scrum@ Accenture Technology Solutions | PCS 60

153. Team Building Product Owner Product Manager Business Business Analyst Functional Project Manager Scrum Master Architect Anyone (not an authority role) Not necessarily a developer. The Team Developer DBA Analyst Tester 61 Scrum@ Accenture Technology Solutions | PCS

154. Scrum Cycle 62 Scrum@ Accenture Technology Solutions | PCS

155. Scrum Principles Summary Scrum@ Accenture Technology Solutions | PCS 63

156. Planning Game Scrum@ Accenture Technology Solutions | PCS 64 45’ immersion in Scrum

157. Exercise: Deliver a brochure for the Earth Tourist Board located on Mars Create cover art, brand, and/or logo Define major topics for Martian Tourism Describean “Art Interestsin Europe” tour Describe a tour based on Photosynthesis Outline a “7 wonders of the world” Expedition Set prices for the tours Outlinewarning messages (gravity, oxygen, fungi, etc.) Suggestclothing options Explain travel options to/from Mars Describe a “Human Sports” tour Outlinerefundpolicy Suggestrelated services Defineadvertisers Definea 12-monthcampaign Set-up how to get more information Scrum@ Accenture Technology Solutions | PCS 65 You have 45’

159. 15’  estimate & prioritize

161. Certified ScrumMaster

162. Certified Product Owner

163. Certified Scrum Developer

164. Certified Scrum Professional

165. Certified Scrum Trainer

166. Certified Scrum Coach

167. Scrum.org http://www.scrum.org/

168. Professional Scrum Master

169. Professional Scrum Master 1

170. Professional Scrum Master 2

171. Professional Scrum Developer

172. PSD .Net

173. PSD Javahttp://www.scrumalliance.org/ 67 Scrum@ Accenture Technology Solutions | PCS

175. Introduction to Scrum

176. ScrumMaster in depth Training

177. Product Owner in depth Training

178. Coaching Scrum Teams

179. Hyper Productivity & Rapid Scrum

180. ScrumBan

181. Scrum Certification on-demand

182. “Short Tracks”:

183. Format: 4 Hours, 4 Trainees, 1 Problem, 1 Solution, 1 Example, 1 Counterexample, 1 Tool, 1 Template

184. Themes: PID, ROI, Scaling Teams, Visual Management, Visioning, Scrum Tools, Magic Estimation. 68 Scrum@ Accenture Technology Solutions | PCS

185. Scrum Resources 69 Scrum@ Accenture Technology Solutions | PCS

186. Companies using SCRUM 70 Scrum@ Accenture Technology Solutions | PCS

187. That was my introduction to Project Management with Scrum 71 Scrum@ Accenture Technology Solutions | PCS

188. Thanks 72 Scrum@ Accenture Technology Solutions | PCS

189. pneis@coprocess.lu 73 Scrum@ Accenture Technology Solutions | PCS