SCRUM

Analyse MOON command

 SCRUM Common lifecycle

Daily
SCRUM

SCRUM
Release
Sprint result delivery

Preparation Sprint
Identifying needs
Result creation
and filling the backlog
 SCRUM Infographics
Developers Team
Create an increment

Product Owner
Responsible for
Roles
the product backlog SCRUM

SCRUM Master
Coordinates the process
 Preparation
Identifying needs and filling the backlog

Working on the
Product Backlog Sprint Planning

STEP 1 STEP 2

Story Sprint Goals

Story
Story
Big Epic
Story
Story

Story
 Sprint
Result creation

Sprint review
Daily SCRUM

Development

Retrospective

Demo
 Our gaps and possible improvements
What’s wrong?
Sometimes we don't decompose tasks enough

What it can lead to?

● one task takes a long time to complete
● other tasks may be blocked
● sprint scores go down

What can be done to remedy the situation?

● split large tasks into subtasks

● think more carefully about the dependencies between tasks at the planning stage
What’s wrong?
Stories are not always prioritized at the sprint planning stage

What it can lead to?

● tasks can block each other
● the probability of failing more important sprint goals

What can be done to remedy the situation?

● prioritize tasks at the planning stage

● plan enough time for force-majeure
What’s wrong?
There is no sprint review in the middle of the sprint

What it can lead to?

● the probability of failing the sprint goals, due to unnoticed difficulties

What can be done to remedy the situation?

● to update task statuses in the middle of the sprint, and adjust goals to the
situation
What’s wrong?
Users sometimes write directly to developers about minor issues

What it can lead to?

● distracts from tasks - developers are not meeting current sprint goals
● probability of failing to meet the sprint goals

What can be done to remedy the situation?

● set up organized issue collection

● schedule such tasks in the following iterations
What’s wrong?
Retrospective is not always held immediately after the end of a sprint

What it can lead to?

● problems remain unnoticed
● product quality is falling

What can be done to remedy the situation?

● to plan in advance the time for the retrospective immediately after

the end of the sprint
What’s wrong?
Action items are sometimes forgotten or not turned into tasks

What it can lead to?

● the same problems can recur with each sprint
● product quality is falling

What can be done to remedy the situation?

● create tasks from action items

● before each new retro, say the results of the past action items