Scrum is a framework for managing product development that uses short cycles of work called sprints, daily stand-ups to track progress, and iterative planning to adapt to changes. Key aspects of Scrum include self-organizing cross-functional teams, time-boxing work into sprints, and artifacts like product backlogs and sprint backlogs to track work. Scrum roles include the Scrum Master, Product Owner, and Team. Variations like Scrum-ban blend Scrum with Kanban for maintenance work.

1. SCRUMThe Framework

2. SCRUM Theory Three pillars uphold every implementation of empirical process controlTransparencyInspectionAdaptation

3. Inspection and AdaptationThe Daily Scrum meetingThe Sprint Review and Planning MeetingsThe Sprint Retrospective

4. SCRUM ContentTeamsTime-boxesArtifactsRules

5. TeamsScrum MasterProduct OwnerTeam

6. Time-BoxesSprintDaily SCRUMSprint ReviewSprint RetrospectiveSprint Planning MeetingRelease Planning Meeting

7. ArtifactsProduct BacklogSprint BacklogRelease BurndownSprint Burndown

8. Rules Rules bind together Scrum’s time-boxes, roles, and artifacts.

9. SCRUM Roles

10. PIGSScrum MasterProduct OwnerTeamChickenStakeholdersManagers

11. SCRUM-BANespecially suited for maintenance projects with frequent and unexpected user stories or errors.SCRUM practices without time limited sprintVisualization of the work stages and limitations for simultaneous unfinished user stories and defects are familiar from the Kanban model.In their simplest, the work stages areUnstartedOngoingCompleted

12. Final ThoughtsDone (Sashimi)UndoneAbnormal Termination "Working more hours" does not necessarily mean "producing more output""A happy team makes a tough task look simple"

13. After Thoughts