How does work? SCRUM SCRUM MASTER ELEMENTS 1. ROLES 3. TOOLS 2. ACTIVITIES - planning releases - refinement - planning a sprint - sprint - daily meengs - sprint review - scrum retrospecve TEAM SCRUM MASTER PRODUCT OWNER - backlog - burndown charts SCRUM is a set of rules concerning project management. It’s clear It’s flexible Educates It’s effecve Helps coping with unpredicted factors It’s Easy STEADY WORK RHYTHM TIMEFRAMES ::::::::::::::::::::::::::::::::::::: ::::::::::::::::::::::::::::::::::::: ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: PRODUCT OWNER IDEA PRODUCT PROCESS SELF-ORGANIZATION ADAPTATION (CONTINUOUS IMPROVEMENT) INSPECTION (FEEDBACK) CLARITY (COMMUNICATION) TRUST TEAM WHAT IS SCRUM? TWICE AS MUCH, TWICE AS FAST or PRODUCT OWNER PRODUCT REGISTRY SPRINT USER STORY SCRUM BOARD USER STORY TASK 97)6 7836= 83 (3 -2 463+6)77 (32) US1 T5 T5 T6 T4 T4 T4 T3 T3 T3 T2 T2 T2 T1 T1 T1 US2 US3 Scrum’s origins are dated to 1986, but its first formal documentaon was created in 1995. Scrum is named aſter a rugby tacc, and was designed to help manage projects with hard to predict outcomes. Meaning: It helps with Context User experience Priories Plot Understanding main character’s situaon Understanding goals and needs • The team idenfies with the end user. • The team engages in searching for the best soluon. TEMPLATE: As a <user_name> I would like to <acon> to <reason> EXAMPLE: As a system administrator I want to login to the admin panel to manage the site. What’s what in scrum? GLOSSARY Release – pushing a finished fragment of the project. Preceded by sprint. User story – the smallest measurable funconality, generang a business advantage. Sprint (Iteraon) – process which aims to produce a funconing fragment of the product. During the sprint a team completes all the tasks necessary to achieve this goal. To ensure good realizaon of a sprint the team must understand the user stories. Refinement – a reflecon before the next sprint. During refinement we explain the user stories for a next sprint. Welcome, but not necessary. Burndown – shows the work progress during a sprint. Visualized by burndown charts which depict the amount of work leſt. Sprint retrospecve – a meeng at the end of iteraon, dedicated to refining the process. Any conclusions from the retrospecve will be implemented during the next sprint. Definion of done – the quality metric for a delivered peace of code. It defines what (apart from finishing the task) has to be done, to consider the funconality complete (e.g. code review, performance tesng). Sources: T. Włodarek, Pragmac methods of soſtware producon, hp://www.slideshare.net/tomek_w/scrum-w-59-minut?from_acon=save What is Scrum?, hp://procognita.pl/nc/zasoby/artykuly/czytaj/artykul/co-to-jest-scrum-58/ Our own experience :) SPRINT BACKLOG SPRINT PRODUCT 7 days 24 h (ALL STORIES)