Agile Scrum Process Checklist To Be Successful, Agile .

Agile Scrum Process ChecklistTo be successful, agile projects require a consistent management process. This checklist provides the various roles involved in agileprojects (especially those with limited agile experience) with a comprehensive checklist that ensures that they complete theessential tasks from planning to deployment. Add tasks or change terminology to align the Checklist with your organization’sapproach.Agile Scrum ProcessProject InitiationStartSprintConduct DailyScrumsDemo/ReviewPlan the SprintSprintRetrospectiveProductReleaseGrooming SessionsNext SprintEndSprint Pierson Requirements Group, Inc.www.piersonrequirementsgroup.com

Project Initiation- Product Owner and Business Analysts are responsible scope, requirements and priorities are defined before thesprint begins.TaskGather product backlogsDefine the project goalsIdentify team membersIdentify the key teamrolesDefine communicationplan for community ofstakeholdersDefine backlog storiesderived from epicsDescriptionStatusCommentsThe list of processes to be developed for aproject should be in the form of stories orepics, (often derived from use cases orprocess walkthroughs)The overall goals will guide the overall shapeof the solution and guide the priority-settingfor various processesThe members of the project team who willparticipate in all of the sprints in the project.Include stakeholders, quality assurance andimplementation team members.Scrum master (organizes team, removesblockers, executes on scrum process - sprintplanning, retrospectives, daily scrums). Product Owner Developers and Quality Assurance StakeholdersIdentify the expected level of stakeholderparticipation and get commitment for thoseresources and time. Identify the method ofcommunication with stakeholders.Stories include: Title Pierson Requirements Group, Inc.www.piersonrequirementsgroup.com

Description (As a ROLE I want toPrioritize backlog andcommunicate sprintrelease goals withstakeholders ACTION so I can PURPOSE ) Acceptance Test Criteria(Implementation conditions must be truefor the story to be considered complete)Prioritize the stories based on user value ascommunicated by the stakeholders.Sprint Planning- The Scrum Master is responsible for completing the sprint plan before the sprint begins.TaskDefine sprint lengthsPresent stories andacceptance test criteriaDefine “done” for eachstoryEstimate storiesDescriptionStatusCommentsThe Scrum Master must establish the length ofa sprint (usually one or two weeks).The product owner should lead the teamthrough the proposed project.Product Owner, Business Analysts, QAcollaborate with the developer to confirm thescope, expectations (acceptance criteria), andtechnical implementation details for theSprint, and establish how and how much QAwill be carried out, what documentation willbe prepared and by whom.Product owner/developer/businessanalyst/scrum master estimate time forcompletion of each user story and tasks Pierson Requirements Group, Inc.www.piersonrequirementsgroup.com

Develop Scrum BoardBook daily scrumsneeded to complete the user story. Tasks areestimated by man hours.The scrum master should prepare this projecttracking tool.Block off team calendars for the daily scrums,15 minutes every day.Daily Scrums- The Scrum Master is responsible for facilitating the meeting. All team members must attend this 15 minute dailymeeting.TaskSelect story fordevelopment and designeach story solutionUpdate status of storiesIdentify, track, andresolve blockersCalculate time stillrequired for the sprintDescriptionStatusCommentsBefore developers begin working on aselected story, Product Owner, TechnicalArchitect discuss design elements for thatstory.Identify stories that will be worked on or arein progress. Get time spent and timeremaining.Record type of blockers and time spent oneach type to improve future estimates.Burn down "Done" stories using a Burn downchart. Pierson Requirements Group, Inc.www.piersonrequirementsgroup.com

Review Meeting/Demo- The Product Owner is responsible for reviewing the completed work at the end of the sprint.TaskExecute demoGather feedbackDiscuss stories that will becompleted in theupcoming sprintDescriptionStatusCommentsCarry out the demo to relevant stakeholders.Collect detailed comments from allobservers, consolidate findings. Add toproject backlog.Review the stories planned.Sprint Retrospective- The Scrum Master is responsible for leading a lessons learned meeting is conducted at the end of each sprint.TaskReview sprint statusDiscuss what was donewell, areas forimprovement, changesrequired to improveresultsDescriptionStatusCommentsReview stories in the sprint: what wascompleted, what was not, what will bedemoed, what will be released.Encourage open discussion to identify partsof the process that would benefit fromchange. Pierson Requirements Group, Inc.www.piersonrequirementsgroup.com

Agree on how the nextsprint will be runMake adjustments to make the sprintprocess more effective.Product Release- The Product Owner is responsible for ensuring communication and training is completed at the end of the sprint.TaskCommunicate tostakeholder communityProvide trainingDescriptionStatusCommentsWhen the contents of a sprint are ready fordeployment, inform the user population ofthe changes in the systems, include HelpDesk.Provide training for the new functionality tothe stakeholder community, includingHelpdesk. Pierson Requirements Group, Inc.www.piersonrequirementsgroup.com

Sprint Planning- The Scrum Master is responsible for completing the sprint plan before the sprint begins. Task Description Status Comments Define sprint lengths The Scrum Master must establish the length of a sprint (usually one or two weeks). Present stories and accept