Management fundamentals scrum 101

download Management fundamentals scrum 101

If you can't read please download the document

Embed Size (px)

Transcript of Management fundamentals scrum 101

Management Fundamental

Management Fundamentals:Scrum 101

ManagersGuideProject Management ConsultingYossi BarezerAug 2016Reality Check!


IntroductionThis presentation describes the basic elements of the Scrum FrameworkMy goal is to provide an organized view that will help a novice understand and implement the Scrum foundation quicklyFor enhanced details, you should read the Guide, receive official training and consult a coachHow would I describe Scrum?The Scrum methodology provides a way to continuously, consistently, and constantly improve product value using reality checks

Note, I use the Scrum Guide as my reference as well.2

AGENDACertificationsDefinition of ScrumScrum TheoryThe Scrum FrameworkThe 3 Pillars/PrinciplesThe Scrum TeamThe Scrum Team and EventScrum ArtifactsProduct BacklogSprint Planning and BacklogThe Scrum Process - IncrementScrum Event/CeremonyEvents Goals and DeliverablesThe Sprint FrameworkTime BoxSprint PlanningDaily ScrumScrum BoardBurn-Down ChartSprint ReviewSprint RetrospectiveDefinition of DoneScrum Summary

3 CertificationPSM I, II - Professional Scrum Master Level I&II (CSM Equivalent)PSPO I, II - Professional Scrum Product Owner Level I&II (CSPO Equivalent)PSD I - Professional Scrum Developer Level I (CSD Equivalent)SPS - Scaled Professional Scrum (Scrum of Scrum)PSP - Professional Scrum PractitionerPSF - Professional Scrum FoundationsPSE - Professional Scrum ExpertPST - Professional Scrum Trainer


Definition of ScrumScrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

Scrum is a process framework that has been used to manage complex product development.

The rules of Scrum bind together the events, roles, and artifacts





Scrum Theory Scrum is founded on empirical process control theory, or empiricismThe 3 Pillars/PrinciplesThree pillars uphold every implementation of empirical process control:TransparencyInspectionAdaptationThe Scrum Team /RolesThe Scrum Team consists of a:Product OwnerThe Development TeamScrum MasterScrum Teams are self-organizing and cross-functionalScrum ArtifactsScrum artifacts represent the work or value to provide transparency and opportunities for inspection and adaptationProduct Backlog Sprint BacklogIncrement Scrum EventsScrum prescribes five formal events for inspection and adaptation, as described in the Scrum Events section of this document: The SprintSprint PlanningDaily ScrumSprint ReviewSprint Retrospective

Note: Scrum MasterA Scrum Master is a servant-leader for the Development Team. He is facilitating and removing impedimentsServes a team in achieving the best productivity possible


The Principles/PillarsThe Scrum FrameworkRoles/Team Product Owner Scrum Master DeveloperArtifact Product Backlog Sprint Backlog Sprint Increment Burn-Down/Up ChartEvents/Ceremonies The Sprint Sprint Planning Meeting Daily Meeting The Sprint Review Sprint Retrospective Product RefiningTransparency Inspection AdaptationDONE

*Burn-Down/Up Chart is considered as an internal artifact for the Development team**Product Refining is considered as an external event to the ceremonies7

The 3 Pillars/Principles


The 3 Pillars/PrinciplesTransparency Significant aspects of the process must be visible to those responsible for the outcome

InspectionScrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances

AdaptationIf an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted


The 3 Pillars/PrinciplesTransparencyInspectedAdaptedArtifactThe SprintProduct BacklogProduct BacklogYesSprint PlanningProduct BacklogSprint BacklogYesDaily MeetingSprint ReviewSprint BacklogYesSprint ReviewSprint IncrementProduct BacklogYesSprint RetrospectiveThe Team & ProcessThe Team & ProcessNoProduct RefiningProduct BacklogProduct Backlog & Sprint BacklogYes1 Sprint Backlog Sub-taskSprint BacklogSprint BacklogYes

*Artifacts are part of the outcome of the meeting**The Sprint Retrospective should have a meeting minutes only if the team will agree and only on the process improvement10

The Scrum Team


The Scrum TeamThe Product OwnerThe Product Owner is responsible for maximizing the value of the product and the work of the Development TeamThe Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes

The Development TeamThe Development Team consists of professionals who do the work of delivering a potentially releasable Increment of Done product at the end of each SprintOnly members of the Development Team create the Increment

The Scrum MasterThe Scrum Master is responsible for ensuring Scrum is understood and enactedScrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules


The Scrum Team and EventsEventEventOwnerProduct OwnerScrum MasterDeveloperOtherSprint Planning Part IProduct Owner YYYNSprint Planning Part IIDevOptionalYYNDaily MeetingDevNOptionalYNSprint ReviewProduct OwnerYYYYSprint RetrospectiveScrum MasterYYYNProduct RefiningProduct OwnerYYYN1 Sprint Backlog Sub-taskDevNOptionalYN


Scrum Artifacts

Product Backlog marketing wish listThe sprint Backlog developer plans how to executeIncrement the actual deliverable14

Scrum ArtifactsProduct BacklogThe Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the productThe Product Owner is responsible for the Product Backlog, including its content, availability, and ordering

Sprint BacklogThe Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint GoalThe Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a Done Increment

IncrementThe Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.

Users Acceptance Test can be added to the Product Backlog.Product Backlog items that selected to move to the Sprint Backlog named ReadySprint Backlog also called Sub-Tasks. Sub-Task belong to a Story. Tasks are independed. i.e. Done Checklist.


Product Backlog

The product attributes are:- Description: will answer the question What should I do? (detailed enough to understand) Order: The Product Backlog is ordered by the Product Owner Estimate workload effort: Small, Medium, Large, Extra Large Value: to marketplace

Product Backlog items also called Issues.Issue types can be Story, Bug, Task16

Sprint Planning and Backlog

The Development Team selects items to develop. This will be the Product Increment.Each selected Item will have the following details: Description: will answer the question How will we make this change? Duration 1-2 days Assign

Sprint Backlog items also called Sub-Tasks.17

The Scrum Process - Increment

By Lakeworks - Own work, GFDL, the end of a Sprint, the new Increment must be Done, which means it must be in useable condition and meet the Scrum Teams definition of Done. It must be in useable condition regardless of whether the Product Owner decides to actually release it


Scrum Events


Scrum EventsThe SprintThe heart of Scrum is a Sprint, a time-box of one month or less during which a Done, useable, and potentially releasable product Increment is created

Sprint PlanningThe work to be performed in the Sprint plans at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team

Daily ScrumThe Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one

Sprint ReviewA Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint

Sprint RetrospectiveThe Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.


Events Goals and DeliverablesEventGoalDeliverablesThe SprintA time-box duration which a Done, usable, and Increment is created potentially releasable product A working IncrementSprint PlanningPart I: What can be done this sprint?Part II: How will the chosen work get done?Product Backlog, Sprint Goal, list of selected Product BacklogDefine Done, Check List, Sprint Backlog (Sprint Plan: Tasks & Owner)Daily MeetingInspect and adapt the progress toward the Sprint GoalWhat did I do yesterday?What will I do today?Do I see any impediment?Updated Scrum Board, Updated Sprint Backlog Burn-Down/Up


Events Goals and DeliverablesEventGoalDeliverablesSprint ReviewInspect the Increment and Adapt the Product BacklogP.O. explain what is done and what is not DoneDev. Team explain ove