Download to read offline
More Related Content
Similar to Learn scrum in half an hour
Learn scrum in half an hour
- 1. Agile Scrum Learn scrumin half an hour
- 2. Agile Scrum A cross-functionalteam delivers potentially shippable product increments in an iterative time-boxes called sprints. Inspect & adapt is a major theme in scrum which gives opportunities to improve in the current project itself. Sprint Review Sprint Daily Scrum Release Planning Sprint Planning Sprint Retrospective Requirements Product Backlog Sprint Backlog Working Software Product Owner Team Scrum Master Process Recommendations
- 3. Scrum Role –Product Owner Product owner: A product owner represents SPOC of business users & accountable for ROI of the project. There should be a only one product owner for a scrum team. # Process Activity 1 Release Planning • Shares Product vision & project goal to the team. • Shares project requirement in terms of epic & user stories. • Clarify the user stories and prioritized the product backlog. 2 Sprint Planning • Prioritize product backlog & explains priority after each sprint. • Clarify user stories & their acceptance criteria. • Helps team to select backlog items for the sprint. 3 Sprint Review • Participates hands-on of live software. • Understands product development. • Share feedback of live software to finalize ‘done’. Release Planning Sprint Planning Sprint Review Product OwnerRequirements Product Backlog Sprint Backlog Working Software
- 4. Scrum Role –Scrum Master Scrum Master: Scrum Master helps team and product owner with scrum processes and removes impediments reported by the team. # Proces s Activity 1 Release Planning • Assist in clarifying user stories. • Moderate planning poker. • Assist in building product backlog. 2 Sprint Planning • Brings retrospective feedback. • Helps with decomposing. • Assist in creating sprint backlog. 3 Daily Scrum • Ensures daily scrum happens. • Assists in daily scrum if needed. • Watch obstacles are reported. # Process Activity 4 Sprint • Work on impediments. • Ensures team gets timely help. • Ensures burn down charts get updated. 5 Sprint Review • Encourages feedback giving. • Encourages team to speak. • Assist with verifying ‘done’. 6 Sprint Retrospective • Encourage team to speak. • Assist in calculating velocity. • Assist in deriving recommendations. Sprint Burn Down Release Planning Sprint Planning Daily Scrum Scrum Master Sprint Sprint Review Sprint Retrospective Product Backlog Sprint Backlog Release Burn Down Working Software Process Improvement
- 5. Scrum Role –Team Team: A 7+ or – 2 cross functional team, self managing team with high degree of autonomy & accountability works on priority chosen by product owner. # Process Activity 1 Release Planning • Understands requirement. • Estimates user stories, epic • Builds product backlog. 2 Sprint Planning • Understands priority. • Decompose the backlog item. • Commit the sprit. 3 Daily Scrum • What has been accomplished • What will done next • What are obstacle # Process Activity 4 Sprint • Convert committed backlog into working software • Updates sprint burn down. 5 Sprint Review • Assist user hands-on. • Receives feedback. • Update release burn down. 6 Sprint Retrospective • Review process – inspect & adapt. • productive process will continue • unproductive process will not Release Planning Sprint Planning Daily Scrum Team Sprint Sprint Review Sprint Retrospective Product Backlog Sprint Backlog Sprint Burn Down Release Burn Down Working Software Process Improvement
- 6. Scrum Process –Release Planning # Component Activity 1 Product vision/Product roadmap • Produce owner share product vision. • Big picture is created. • Product roadmap is derived. 2 User stories/ Epic • Product owner shares user stories/epic. • Acceptance criteria are discussed and agreed. • Dependencies are discussed. 3 Planning Poker • Scrum master moderates planning poker. • Team estimates user story and epic. • Team allocates story points to user stories/epic. 4 Product backlog • Product owner prioritize user stories/epic. • Other non-user story requirements are also prioritized. • Total story point is used to evaluate high level effort. Release Planning : Release planning converts requirement into product backlog. Release Planning Product Owner Scrum MasterTeam Requirements Product Backlog
- 7. Scrum Process –Sprint Planning # Component Activity 1 Product backlog • Product owner prioritized the product backlog after last sprint. • An addition/deletion of item may also happen. 2 What • Product owner picks up the highest priority for the sprint to work • Sprint goal is devised. • Any pending clarification is resolved. 3 How • Improvements of last retrospective are discussed. • Selected product backlog items are broken into activities • Activities are sequences & assigned among team. 4 Sprint backlog • List of activities constitutes sprint backlog • Task volunteer is assigned to each activity • Sprint backlog is committed by the team and frozen for the sprint. Sprint Planning : Spring planning is a 2 hours/week sprint time-boxed meeting to prepare sprint which delivers a sprint backlog. Sprint Planning What How Product Owner Team Scrum Master Sprint Backlog Product Backlog
- 8. Scrum Process –Sprint # Component Activity 1 Daily Scrum • A 15 minute must have stand up call • What has been accomplished since last meeting? • What will be done before next meeting? • What obstacles are in the way? 2 Obstacles • Scrum master understand obstacles in daily scrum • Scrum master should resolve obstacles 3 Sprint Burn down • Scrum team works on sprint activities in best of their capacity • Scrum updates burn down chart as activity completes • Scrum team get scrum master help to resolve obstacles • Team can choose any new tool & technique Sprint : 2-4 week iterative development cycle deliver sprint goal in the form of working software. Sprint Daily Scrum Team Scrum Master Sprint Backlog Sprint Burn Down
- 9. Scrum Process –Sprint Review # Component Activity 1 Sprint backlog • Sprint backlog & sprint burin is verified to derive how many backlog items has been ‘done’. • Team explains how product was developed. 2 User story • User stories of completed items are reviewed. • Test results are verified against acceptance criteria. 3 Working Software • Product owner uses working software. • Product owner share his/her feedback. • Constructive conversation between team & product owner. 4 Release Burn Down • Team & product owner agrees on what has been ‘done’. • Release burn down char is updated for the sprint. • Product owner share next priority in high level. Sprint Review : Sprint review is a 1 hour/week of sprint to review ‘done’ items of the product backlog in inspect & adapt mode. Sprint Review Product Owner Team Scrum Master Sprint Backlog Working Software Release Burn DownUser Story
- 10. Scrum Process –Sprint Retrospective # Component Activity 1 Process, environment & tool • Team review process, environment & tool used in the sprint. • Team conclude what went good & what went wrong. • Scrum moderate this activity neutrally. 2 Recommendation • Process & practice recommendations are recorded. • These recommendations are discussed in next sprint planning. • Team adapts the recommendations in next sprint. • These are reviewed again in next sprint retrospective which leads to continuous improvement. Sprint Retrospective : A 45 minute/week sprint time-boxed meeting to inspect & adapt process & environment Sprint Retrospective Team Scrum Master Process & Environment Process Improvement
- 11. Scrum Artifacts # ArtifactTemplate 1 Product backlog & release burn down 2 Sprint backlog & sprint burn down 3 User story 4 Planning Poker
- 12.