Introduction to Scrum How to use Scrum in corporate environments: - distributed teams - multiprojects

1. Introduction to Scrum

2. Scrum Benefits Where it comes from What it is How it works Scrum in corporate environments content

4. Progress is made, even when requirements are not stable.

5. Early delivery of tested and working software

7. Increased customer commitment through involvement in the development process

8. Problems are immediately detected

9. Tackle or escalate risks without delay

11. Stakeholders are involved in scrum & review meetings

12. The daily scrums allow you to give advance warnings of potential issues & deviation

14. Where it comes fromfailing traditonal approach Functional Analysis Business Business IT Technical Analysis Develop-ment Integration Test UAT

15. Where it comes fromfailing traditonal approach Functional Analysis Business Business IT Technical Analysis Develop-ment Integration Test UAT

17. Long start-up fase

18. Product available in the end

19. Responding to change difficult & costly

20. Team Accountability lowIssues!

21. Where it comes from Reactions Nonaka and Tackeuchi (Harvard 1986) Paper ”The New New Product Development Game” Rugby Scrum Jeff Sutherland Easel Company Ken Schwaber White paper “SCRUM Development Process”

22. Where it comes from Agile Manifesto

24. Short time to functionality

25. High visibility of progress

26. Customer centricity

27. Efficient operational control: planning, progress, cost

29. Where it comes fromtraditonal approach Functional Analysis Business Business IT Technical Analysis Develop-ment Integration Test UAT

30. Where it comes from agile approach Business Business IT Working Software

31. Where it comes from agile approach Business Business IT ... Working Software Working Software Working Software

33. Immediate feedback from customers

34. Stakeholders invited at 2-weekly demo

35. More control on cost/performance

36. Tighter control on development through daily evaluation

37. Immediate progress & risk tracking

40. How it works characteristics Roles Artifacts Ceremonies Positions 3 Tools 4 Meetings

41. How it works characteristics Product Owner The Team ScrumMaster Sprint Planning Meeting Daily Stand-up Sprint Review Sprint Retrospective Ceremonies/ Meetings Roles Product Backlog Sprint Backlog Burndown charts Bug/Impediment List Artifacts/Tools

42. How it works roles The “How” and “How Much” The “Process” The “What”

45. Commits to the Sprint

46. Delivers what is promised

47. Self-Organizing

48. Owns the vision of what should be produced to achieve business success

50. Coaches and facilitates

51. Takes away impediments

52. Plans the Sprint during sprint planning meeting

53. Commits to the Sprint

54. Delivers what is promised

55. Self-Organizing

56. Owns the vision of what should be produced to achieve business success

59. Estimated in relative weights (story points)

61. Estimated in relative weights (story points)

62. PO is owner

63. List of user stories & its tasks to deliver the stories

64. Filled with stories to be developed in the sprint

66. Per Sprint/Project

67. Prioritized list of user stories

68. Estimated in relative weights (story points)

69. PO is owner

70. List of user stories & its tasks to deliver the stories

71. Filled with stories to be developed in the sprint

73. Sprint Backlog is created

74. PO, SM & Team

75. Daily follow up

76. SM & Team

78. End of each sprint

81. Sprint Backlog is created

82. PO, SM & Team

83. Daily follow up

84. SM & Team

86. End of each sprint

89. Sprint Backlog is created

90. PO, SM & Team

91. Daily follow up

92. SM & Team

94. End of each sprint

97. Sprint Backlog is created

98. PO, SM & Team

99. Daily follow up

100. SM & Team

102. End of each sprint

105. Scrum in corporate environments issues

106. Scrum in corporate environments issues Time consuming to manage Hard to create reports Disparate sources of information No real-time status information Hard to audit Not scaleable

107. Scrum in corporate environments solution

108. Scrum in corporate environments solution pmScrum is a pragmatic scrum tool that supports project teams endorsing the scrum framework - over multiple projects - in distributed teams

109. Scrum in corporate environments Solution – Electronic taskboard

110. Scrum in corporate environments Solution – Backlog Management

111. Scrum in corporate environments Solution – On-line metrics # Story Points Planned Actual Trend Timeline Burndowns

112. Scrum in corporate environments Solution – On-line metrics Bug Lists

113. Scrum in corporate environments Solution – On-line metrics Reporting over multiple projects

114. Scrum in corporate environments Solution – Integrated Timesheets

115. Scrum in corporate environments solution pmScrum is a pragmatic scrum tool that supports project teams endorsing the scrum framework - over multiple projects - in distributed teams Reduces risks Reduces costs Increases benefits Increases transparency

116. Frans Vanhaelewijck Product Manager frans.vanhaelewijck@pmscrum.com Mobile: +32 (0) 495 24 66 11 www.pmscrum.com sales@pmscrum.com