The document provides an overview of Scrum, an iterative framework for agile project management that enhances transparency, accountability, and speed in software development. It outlines key benefits, roles, ceremonies, and artifacts associated with Scrum, emphasizing its ability to deliver higher quality results while accommodating changing customer needs. Additionally, it discusses challenges in corporate environments and presents solutions, including the use of a pragmatic tool, PMScrum, to support distributed teams and multiple projects.

1. Introduction to Scrum

2. ScrumBenefitsWhere it comes fromWhat it isHow it worksScrum in corporate environmentscontent

3. benefits of scrumTo deliver faster with higher quality in a more transparent way Faster Scrum forces you to break-up projects into a series of manageable pieces

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

5. Early delivery of tested and working software

6. Easier response to changing needs (of the customer) Higher Quality Frequent feedback & increments delivery guarantees meeting customer expectations

7. Increased customer commitment through involvement in the development process

8. Problems are immediately detected

9. Tackle or escalate risks without delay

10. Tighter control on development through daily evaluation More Transparent At start of sprint, the scope is fixed and everyone knows who is accountable for what and by when

11. Stakeholders are involved in scrum & review meetings

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

13. Clear and accurate view on planned budget vs. actuals and the ability to react swiftly (on sprint frequency) Scrum

14. Where it comes fromfailing traditonal approachFunctional AnalysisBusinessBusinessITTechnicalAnalysisDevelop-mentIntegration TestUAT

15. Where it comes fromfailing traditonal approachFunctional AnalysisBusinessBusinessITTechnicalAnalysisDevelop-mentIntegration TestUAT

16. Where it comes fromfailing traditonal approachFunctional AnalysisBusinessBusinessITTechnicalAnalysisDevelop-mentIntegration TestUATTime to market too long

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 ReactionsNonaka and Tackeuchi (Harvard 1986)Paper ”The New New Product Development Game”RugbyScrumJeff SutherlandEasel CompanyKen SchwaberWhite paper “SCRUM Development Process”

22. Where it comes from Agile Manifesto

23. Where it comes from Agile ValuesFocus on short, iterative development cycles

24. Short time to functionality

25. High visibility of progress

26. Customer centricity

27. Efficient operational control: planning, progress, cost

28. Best practices industry-based frameworksWhere it comes from Agile TechniquesStrategicTactical LeandXScrumExec/PMOMgmt/ProjectDev/Delivery

29. Where it comes fromtraditonal approachFunctional AnalysisBusinessBusinessITTechnicalAnalysisDevelop-mentIntegration TestUAT

30. Where it comes from agile approachBusinessBusinessITWorking Software

31. Where it comes from agile approachBusinessBusinessIT...Working SoftwareWorking SoftwareWorking Software

32. Where it comes from agile approachBusinessBusinessIT...Working SoftwareWorking SoftwareWorking SoftwareEarly delivery of tested and 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

38. High accountability of team membersWhat it is DefinitionsScrum is an iterative, incremental frameworkFor project management &For agile software developmentScrum is nota methodology

39. How it works iterateSplit your work into a list of small, concrete deliverables Sort the list by priority estimate the relative effort of each itemSplit time into short fixed-length iterations (usually 1 – 4 weeks)Split your organization into small, cross-functional, self organizing teamsSlice-up WorkSlice-up TimeSlice-up Teams“Scrum is what we already do when we are with our backs against the wall!” (J. Coplien)

40. How it works characteristicsRolesArtifactsCeremoniesPositions3Tools4Meetings

41. How it works characteristicsProduct OwnerThe TeamScrumMasterSprint Planning MeetingDaily Stand-upSprint ReviewSprint RetrospectiveCeremonies/MeetingsRolesProduct BacklogSprint BacklogBurndown chartsBug/Impediment ListArtifacts/Tools

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

43. How it works rolesThe “How” and “How Much”The “Process”The “What” Owns the vision of what should be produced to achieve business success

44. Turns input from stakeholders into a single list, called Product Backlog Prioritizes list based on business value, ROI or level of riskHow it works rolesThe “How” and “How Much”The “Process”The “What” Plans the Sprint during sprint planning meeting