Transcription
Scrum Guidelinesv.22011WWW.SCRUMDESK.COM
WHYAgile CeremoniesAgile project is developed in repeatableProduct StrategyRelease PlanningSprint PlanningDaily standupReview &RetrospectiveWWW.SCRUMDESK.COMceremonies that give rhythm to delivery.Once per yearEvery quarterEvery three weeksEvery dayEvery three weeks
WHYAgile RoadmapRoadmap is our planRelase 1of intent that allows us to be ready for changes.Release 2Objective AObjective C Epic A.1 Epic A.2 Epic C.1 Epic C.2 Epic B.1 Epic B.2 Epic B.3WWW.SCRUMDESK.COMObjective FObjective GObjective DObjective BRelease 3 EpicsObjective E Epics
Week 1WWW.SCRUMDESK.COMWeek 2Pre-planning sessionPre-planning sessionSprint planningWeek 3Sprint planningReviewRetrospectiveSprint ceremoniesSprint XSprint X 1
Sprint scheduleThis SprintDaySprint PlanningMeeting½ ayDailyWednesdayBuild, e1 hour½ hourWWW.SCRUMDESK.COM, All Rights ReservedFridayThe Next SprintPre-planning session1 hourPre-planning session1 hourThe next sprint backlogfinalized
Product StrategyWHYWe need to understand WHAT, for WHOM and WHY product is developed.We need to understand vision, strategy and goals for better planning,management, development and demonstration our product.WHOWHENAll team participatesHappens beforedevelopment isofficially started1-5 daysVision, strategy and goals reviewedStakeholdersidentifiedKey dates agreedElevator statementDependencies identifiedTeams & rolesRisks identifiedRoadmap agreedObjectives agreedHOWOutWHATInDriven by Product OwnerTeam onsiteTeam commitmentRequirements discussedProduct owner prepares a visionbefore the meeting. Vision andstrategy are updated in the meetingWWW.SCRUMDESK.COM, All Rights Reserved
WHYElevator StatementElevator statement helps us to focus on product goals with anunderstanding what our product is, what is not for who is developed andhow is different comparing to our competition.FOR our customers WHO needs something THE product is THAT product key benefit, why is necessary UNLIKE competition alternative OUR PRODUCT is different WWW.SCRUMDESK.COM, All Rights Reserved
WHYRelease PlanningWe would like to identify what next release means,published and agree on preliminary plan.when it should beRelease plan is an increment to our vision according our strategy.We will create estimated release backlog to drive our effort.WHOWHENAll team participatesHappens beforethe release1-5 daysDriven by Product OwnerVision, strategy and goalsOutWHATInFeatures broken into epicsPreliminary estimation ofcomplexity, risk and businessvalueEpics orderedMilestones agreedHOWRisks updatedTeam onsiteTeam commitmentRequirements discussedSubject matter experts invited ifnecessaryAgile project planWWW.SCRUMDESK.COM, All Rights Reserved
WHYDaily StandupSynchronize our progress and plans.We share our status, plans and problems.Happens everysprint dayFacilitated by Scrum MasterWHENWHOAll team participatesProduct Owner is welcome toanswer questions1 minute perteam member 15 minutesManagers as chickenUpdatedimpedimentsWhat do you plan to do today?OutWHATInWhat have you done yesterday?Meetings agreedHOWWhat problems are youencountering?Use WebEx/Skype (optional)Use chatTask board updated beforemeeting. It is checked in themeetingDetailsdiscussed aftermeetingBurn Down chart updated beforemeeting.It is checked in the meetingKeepcommunicationchannel openWWW.SCRUMDESK.COM, All Rights Reserved
WHYRetrospectiveWe examine how to improve our team and the way we work together.We are ready to provide our ideaswhat is good and what can be better.WHOWHENAll team participatesFacilitated by Scrum MasterLast day in asprint½ hourProduct Owner is welcomePrioritized list ofideasIdeas from previous retrospectivesImplementation status reported byScrum Masterimplementation status of ideasreported previouslyOutWHATInManagers, please, stay awayAssigned ideas(optional)Apply different retrospectivepractices based on books &blogsHOWWhat was good?What can be better?Any other ideas?DiscussionVote for ideas , prioritize them and pickup few to be implemented inthe next sprintWWW.SCRUMDESK.COM, All Rights Reserved
WHYReviewWe would like to demonstratereal increment to our customersand stakeholders. We expect our stakeholders will eitheraccept or not accept our achievements.Last day of sprintWHENAll team participatesWHOArranged by Scrum Master1 hourLead by Product OwnerCustomers & stakeholders invitedWorking, potentially shippable,incrementPresentation is optionalHOWLive showSprint backlog items presentedDiscussionWWW.SCRUMDESK.COM, All Rights ReservedOutWHATInWorld is welcomeIteration backlogclosed at the endAcceptance ofsprint outcome
Scrum RolesProduct OwnerFather of the productRepresents the voiceof customersCommunicates with clients, customersand stakeholdersAccountable for ensuring the teamdelivers valueResponsible for product vision androadmapResponsible for product planningManages a product backlogSetting up priorities based on businessvalue and riskAligns product plans with otherdependent productsAccepts outcome of developmentprocessStays in contact with marketing & salesTeamResponsible for delivering the productSmall team, 5-9 peopleMulti-discipline, cross-functionalSelf-organizedApplying pull principleEstimates complexityReflecting problemsIdentify risksDemonstrate the product incrementWWW.SCRUMDESK.COM, All Rights ReservedScrum MasterTeam protectorFacilitatorCoach of scrum processAccountable for removingimpediments with help of othersHelps team to deliver the sprint goalsNot a team leader, but buffer betweenteam and distractionEnforces rulesCollaborates with other scrummasters to align development withothersHelps to team members to focus ontasks
Scrum Master Daily ChecklistTask boardoooooooDoes the team know what has been committed?Is task board visible?Is board updated since the last stand-up?Is time remaining updated since the last stand-up?Are all stories and tasks estimated (maybe except spikes)?Are stories broken to tasks?Are all tasks which are in progress or done assigned?Impedimentso Are impediments visible to everyone?o Is the status of impediments updated?o Are impediments assigned to concrete persons?Burn Down chartooooIs burn down chart current?Do you understand the current status and progress?Does anyone add new work into sprint backlog?Are you taking an action in case you are late as soon as possible?WWW.SCRUMDESK.COM, All Rights Reserved
ExamplesAgile Product Backlog break-downProduct planTheme XTheme YEpic AStory A.1Epic BStory A.2Story B.1Epic CEpic DStory B.2Agile project planProduct planRelease 1Sprint 1Story A.1Story A.22 weeksRelease 2Sprint 2Sprint 3Story B.1Story B.22 weeks2 weeksEpic CRelease 3Epic DEpic‘We want a system to be able to help us with management our client base’‘Product portfolio management’‘Reports and analyses’Story‘As an account manager I would like to add details of a new client into our CRM system so weknow how to contact him’‘As a user I would like to configure my printer before document is printed so I get documentprinted correctly.’WWW.SCRUMDESK.COM, All Rights Reserved
Stakeholders matrixA tool that helps team to understand who customer and their potential clients are and whatthe team should expect or fulfill while communicating the current status and gettingrequirements fluenceHighJohn DoeStakeholderHighLowMary Ewans SponsorLowHighJeffreyHerrisonLowLowSubject Matter ExpertWWW.SCRUMDESK.COM, All Rights atisfiedMonitor
GlossaryReleaseA milestone in which potentially shippable increment is developed and delivered.In release are more (completed only) stories delivered based on value and priorities sorelease adds a product value important for users.SprintAn iteration in which potentially shippable increment is developed by a team. It typicallystarts with sprint planning session, continues every day with daily meeting and is finished byreview and retrospective. Suggested length of the iteration is 1 to 3 weeks.EpicA big functionality that requires huge effort for completion. Epic is a container of otherstories defining big functionality. Epics are slotted into releases typically. An epic should bebroken into smaller parts aka stories.Example: ‘We want a system to be able to help us with management our client base’StoryUser story is one or more sentences written in the language of end user to capture what userwant to achieve including a benefit that might be gained if story is completed. It is efficientway to handle customers’ requests without formalized documents.User story is typically written on an index card. It should also have acceptance criteriadefined.Example: ‘As an account manager I would like to add details of a new client into our CRMsystem so we know how to contact him’Planning pokerA game developed by Mike Cohn used for an estimation of stories complexity based onrelative comparison to a reference story of size 1. Different scales are used, but typically theWWW.SCRUMDESK.COM, All Rights Reserved
scale is 0, ½, 1,2,3,5,8,13,20,40,100. Game is facilitated by Scum Master. Team estimatescomplexity and product owner should be available to explain and answer questions.Stakeholders matrixStakeholders matrix helps identify important stakeholders who are available to product teamto help them with strategy and goals. The outcome of this matrix is an understanding aboutcommunication necessities.CreditsIllustrations of scrum master, product owner, pig and chicken are ownership of MichaelVizdos, www.implementingscrum.comAbout ScrumDeskScrumDesk company shares the knowledge about agile and scrum in Central Europe regionsince 2008.Our Scrum project management solution called ScrumDesk helps agile teams with all Scrumpractices to self-organize and manage development process through intuitive tools availableon Windows, iOS and soon on Android and web.Together with experienced agile coaches we bring agile knowledge in unique AgileKnowledge Hub initiative.Join our community on our pages www.scrumdesk.com.WWW.SCRUMDESK.COM, All Rights Reserved
Our Scrum project management solution called ScrumDesk helps agile teams with all Scrum practices to self-organize and manage development process through intuitive tools available on Windows, iOS and soon on Android and web. Together with experienced agile coaches we bring agile knowledge i
