This document provides an introduction to project management using Scrum. It explains the basic Scrum framework, including roles like the Product Owner, Scrum Master, and self-managed team. The Scrum process is described as a series of time-boxed ceremonies like Sprint Planning, Daily Scrums, Sprint Review and Retrospective. The goal of Scrum is to maximize value through principles of transparency, inspection and adaptation within a flexible, holistic framework. An exercise demonstrates planning a marketing campaign using Scrum techniques.

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

2. Who am I?Scrum@ Accenture Technology Solutions | PCSPMO │ Scrum Coach @ coPROcess S.A.www.coprocess.luhttp://managingagile.blogspot.com/http://paper.li/elPedroMajor2

3. About this WorkshopScrum@ Accenture Technology Solutions | PCS3

4. ObjectiveIntroduce you to Scrum

5. Explain the basic principles

6. Introducing Scrum Training possibilitiesScrum@ Accenture Technology Solutions | PCS4

7. The Process !!!Scrum@ Accenture Technology Solutions | PCS5

8. Inspect & Adapt3 questions:Whoam I?What’smy job?Whataimstoday?Scrum@ Accenture Technology Solutions | PCS6

9. Introduction to ScrumScrum@ Accenture Technology Solutions | PCS7

10. 8Scrum@ Accenture Technology Solutions | PCSWhy “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 19869Scrum@ Accenture Technology Solutions | PCS

12. OriginsScrum@ Accenture Technology Solutions | PCS10

13. The Manifesto for Agile Software Development2001Scrum@ Accenture Technology Solutions | PCS11

14. Introduction by Ken SchwaberScrum is not a methodology. Scrum does not provide the answers to how to build quality software faster.

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 | PCS12

18. 13Scrum@ Accenture Technology Solutions | PCSHow?

19. Scrum is an innovative approach to complete your workScrum is a flexible framework for complex projects.

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.14Scrum@ Accenture Technology Solutions | PCS

22. The TheoryScrum@ Accenture Technology Solutions | PCS15

23. Scrum FrameworkThe Product Owner sets a List of Features called Product Backlog

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❶16Scrum@ Accenture Technology Solutions | PCS

26. Scrum FrameworkEach day, the Team measures its progress during a 15’ meeting: the Daily Scrum

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.❷17Scrum@ Accenture Technology Solutions | PCS

29. Scrum FrameworkThe Sprint ends with the Sprint Review and the Retrospective.

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

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

32. ObjectiveMaximize Value19Scrum@ Accenture Technology Solutions | PCS

33. Scrum Roles20Scrum@ Accenture Technology Solutions | PCS

34. Pigs & Chicken21Scrum@ Accenture Technology Solutions | PCS

35. ❶ The Scrum Team22Scrum@ Accenture Technology Solutions | PCS

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

37. Self-Managed-Team vs. Traditional Organisation24Scrum@ Accenture Technology Solutions | PCS

38. ❸ ScrumMasterEnsures

39. Helps

40. Coaches

41. Protects

42. Removes

43. Responsible

44. Workwith25Scrum@ Accenture Technology Solutions | PCS

45. ❹ Product OwnerResponsible

46. Ensures

47. Accepts

48. Rejects

49. Maintains

50. Work with26Scrum@ Accenture Technology Solutions | PCS

51. Cycle of Ceremonies27Scrum@ Accenture Technology Solutions | PCS

52. Ceremonies are time-boxed.Sprint PlanningSprint ReviewRetrospectiveSprint PlanningDaily MeetingsSPRINT28Scrum@ Accenture Technology Solutions | PCS

53. ❶ Sprint Planning Meeting29Scrum@ Accenture Technology Solutions | PCS

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

55. ❶ Sprint Planning Meeting2 Parts:

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 Sprint31Scrum@ Accenture Technology Solutions | PCS

72. ❷Sprint32Scrum@ Accenture Technology Solutions | PCS

73. ❷SprintDevelopment of the applications from the Sprint Backlog in which the team is involved.