The document discusses Scrum, an agile framework for project management. It describes Scrum roles like the Product Owner and Scrum Master, ceremonies like the daily scrum and sprint planning, artifacts like the product and sprint backlogs, and compares Scrum to traditional waterfall project management. The document also provides tips for transitioning to Scrum and links to learn more about agile coaching and Scrum.

1. Traditional Project Management Erin Beierwaltes | agileaction.blogspot.com

2. How did we do? Scaling Software Agility – Dean Leffingwell Erin Beierwaltes | agileaction.blogspot.com

3. Scrum Erin Beierwaltes | agileaction.blogspot.com

4. The Agile Manifesto Process and tools Individuals and interactions Following a plan Responding to change Comprehensive documentation Working software Contract negotiation Customer collaboration over over over over Source: www.agilemanifesto.org Erin Beierwaltes | agileaction.blogspot.com

5. Features Used by Customers Standish Group Study reported at XP2002 by Jim Johnson, Chairman © Poppendieck LLC Erin Beierwaltes | agileaction.blogspot.com

6. Why Scrum? Delivering the highest business value in the shortest time Working software every two to four weeks Business sets priorities, while teams self-organize for delivery of highest priority features Reprioritization every two to four weeks or option to release It’s better to have 80% 100% done, instead of 100% 80% done. Erin Beierwaltes | agileaction.blogspot.com

7. Requirements Game Get into teams of 2 Choose a Product Manager and a Developer Developers leave the room Product Managers write a “design document” for developers Words ONLY Developers come back in and try to follow written instructions Erin Beierwaltes | agileaction.blogspot.com

8. Erin Beierwaltes | agileaction.blogspot.com

9. PMI’s View of Agile “There is no single best way to define an ideal project life cycle.” – PMBOK, p. 20 “The project manager, in collaboration with the project team, is always responsible for determining what processes are appropriate, and the appropriate degree of rigor for each process, for any given project.” – PMBOK, p. 37 www.pmi.org Erin Beierwaltes | agileaction.blogspot.com

10. PMBOKProject Management Process Groups (mapped to) Agile Project ManagementFramework Initiating  Envisioning Planning  Speculation Executing  Exploring Controlling  Adapting Closing  Closing Jim Highsmith www.stickminds.com Erin Beierwaltes | agileaction.blogspot.com

11. Fixed Requirements Resources Time Plan Driven ValueDriven Estimated Resources Time Features www.dsdm.org Triple Constraints Erin Beierwaltes | agileaction.blogspot.com

13. ScrumMaster

14. Cross-functional Team

15. Daily Scrum

16. Sprint Planning

17. Sprint Demo & Retrospective

18. Prioritized Backlog

19. Time-boxed Sprints

21. Prioritized Tasks

23. Planning Game

24. Test-driven Development

25. Whole Team

26. Continuous Integration

27. Refactoring

28. Small Releases

29. Coding Standards

30. Collective Code Ownership

31. Simple Design

32. System Metaphor

33. Sustainable PaceAgile Methods Erin Beierwaltes | agileaction.blogspot.com

34. Scrum Framework Daily Scrum 2-4 weeks Potentially Shippable Product Backlog Sprint Backlog Erin Beierwaltes | agileaction.blogspot.com

36. ScrumMaster

37. Team

38. Sprint planning

39. Sprint review

40. Sprint retrospective

41. Daily scrum meeting

42. Product backlog

43. Sprint backlog

44. Burndown chartswww.mountaingoatsoftware.com Erin Beierwaltes | agileaction.blogspot.com

45. The Sprint (Timeboxing) 2 to 4 weeks Time boxed Product Owner does NOT make changes mid sprint Team can request changes to the sprint based on burndown progress Erin Beierwaltes | agileaction.blogspot.com

47. ScrumMaster

48. Team

49. Sprint planning

50. Sprint review

51. Sprint retrospective

52. Daily scrum meeting

53. Product backlog

54. Sprint backlog

55. Burndown chartswww.mountaingoatsoftware.com Erin Beierwaltes | agileaction.blogspot.com

56. Product Owner Defines the features of the products Decides on the release date and content Prioritizes features Accepts or rejects work results Erin Beierwaltes | agileaction.blogspot.com

57. ScrumMaster Responsible for Scrum values and practices Removes impediments Shields the team from external interferences Facilitates team decisions Erin Beierwaltes | agileaction.blogspot.com

58. Team 5-9 people (typically) Larger projects expand with multiple scrum teams (scrum of scrums) Cross-functional (developers, testers, documentation, ect) Full time membership Self organized Membership only changes between sprints Erin Beierwaltes | agileaction.blogspot.com

60. ScrumMaster

61. Team

62. Sprint planning

63. Sprint review

64. Sprint retrospective

65. Daily scrum meeting

66. Product backlog

67. Sprint backlog

68. Burndown chartswww.mountaingoatsoftware.com Erin Beierwaltes | agileaction.blogspot.com

69. Scrum Ceremonies Daily Scrum Meeting Sprint Planning Sprint Review and Retrospective www.adyax.com Erin Beierwaltes | agileaction.blogspot.com

71. ScrumMaster

72. Team

73. Sprint planning

74. Sprint review

75. Sprint retrospective

76. Daily scrum meeting

77. Product backlog

78. Sprint backlog

79. Burndown chartswww.mountaingoatsoftware.com Erin Beierwaltes | agileaction.blogspot.com

80. Product Backlog User Stories As a ____, I want ____, so that ____. Prioritized list of ALL desired work Owned and kept up to date by Product Owner Used during sprint planning Reviewed Reprioritized before the start of every sprint Sized with Story Points (by the team) Erin Beierwaltes | agileaction.blogspot.com

81. Sprint Backlog List of TASKS that make up the required work for each Backlog item in the CURRENT sprint Created and estimated by the TEAM Updated by the TEAM Data for the burndown chart Erin Beierwaltes | agileaction.blogspot.com

82. Product Backlog www.inspectandadapt.com Erin Beierwaltes | agileaction.blogspot.com

83. Release Burndown What happened here? Based on average velocity Velocity = number of story points COMPLETED during the sprint Erin Beierwaltes | agileaction.blogspot.com

84. Burndown Chart What happened here? Erin Beierwaltes | agileaction.blogspot.com

85. Waterfall vs. Scrum Waterfall Requirements Predictive Individuals Sequential Cost of change Agile/Scrum User Stories Empirical Teams Iterative Encouraged Change Philipjeffs.com Erin Beierwaltes | agileaction.blogspot.com

86. Transitioning to Scrum Waterfall to Agile Erin Beierwaltes | agileaction.blogspot.com

87. Waterfall vs. Scrum Every framework has its place Agile Project Management with Scrum by Ken Schwaber Erin Beierwaltes | agileaction.blogspot.com

88. Acceptance of Change Know where You are Know where They are www.thecouldview.com Erin Beierwaltes | agileaction.blogspot.com

89. Agile Coaching Find or Become an Agile Coach Erin Beierwaltes | agileaction.blogspot.com

90. Learn More http://www.scrumalliance.org/ http://www.mountaingoatsoftware.com/ http://www.coachingagileteams.com/ http://www.infoq.com/minibooks/scrum-xp-from-the-trenches (free downloadable book) http://www.rallydev.com/agileblog/ Erin Beierwaltes | agileaction.blogspot.com