EURO MPMEuropean MasterIn Proyect Management

Bilbao, 23, October 2010

Andoni Gonzalo

Scrum Tools and Meetings

EURO MPMEuropean MasterIn Proyect Management 2

Agenda

I. Sprint

II. Product Backlog

III. Sprint Backlog

IV. Increment

V. Planning Meeting

VI. Sprint Meeting

VII.Daily Meeting

VIII.Retrospective Meeting

EURO MPMEuropean MasterIn Proyect Management 3

Review

PPPP E

SMPP E

Exposición de prioridades

Resolución de dudas

Estimación del esfuerzo para

cada requisito

Objetivo del Sprint

Reunión diaria SM E( )

IPP

Revisión del trabajo;

resolución de trabas

PPSM E I

Presentación del incremento,

sugerencias, anuncio próximo sprint

COMPONENTES

PRODUCT

BACKLOG

SPRINT

BACKLOG

INCREMENTO

PDP

PDS

INC

EURO MPMEuropean MasterIn Proyect Management 4

Sprint

• Length of an iteration

• 2 weeks – 8 weeks

• Recommended to keep same length (may be exceptions)

• Can’t be extended to finish the work

• Starts with Sprint Meeting and finishes with Review Meeting

Iteration

2-8 weeks

EURO MPMEuropean MasterIn Proyect Management 5

Tools

Product

Backlog

Sprint

BacklogIncrement

System requirement

Work to be done in a SprintPart of the product developed

in a sprint

Daily

cycle

EURO MPMEuropean MasterIn Proyect Management 6

• Premises for agile

• The needed output can be decomposed in functionality

• Each functionality makes sense and have value for the client and

can be deliver independently as soon as possible.

Product Backlog

• Client’s first step

• Define vision and scope of the project

• Identify first requirements (Product Backlog)

• Prioritize them depending on the ROI

EURO MPMEuropean MasterIn Proyect Management 7

• Alive Document

• Is updated when needed, continuously revised

• User Stories

• Prioritized by the Product Owner

Product Backlog

ID Priority User Story Long Description Estimation

1 Very High User Story 1 As a User I want… in order to… 5

2 Very High User Story 2 As Administrator I want… in order to… 2

3 High User Story 3 As Support I want… in order to… 3

4 Medium User Story 4 As Sales I want… in order to… 8

EURO MPMEuropean MasterIn Proyect Management 8

• Final output’s requirements

• Visible to everyone involved in the project

• PO

• Scrum manager

• Team

• Stakeholders

• Everyone can contribute to add items

• It’s own by the PO

• Only the PO can prioritized

• Needs to determine:

• How valuable or urgent is each User Story

• How much each User Story costs (effort)

Have the needed decision criteria for the Sprint Meeting

Product Backlog

EURO MPMEuropean MasterIn Proyect Management 9

Product Backlog

System Requirement and Product Backlog: similar

Predictive Development

SYSTEM

• System

Requirements

• SOFTWARE

• Predictive Gantt

Agile Development

• Product Vision

• Product Backlog

• User Stories

Sprint Objective

Sprint Backlog

EURO MPMEuropean MasterIn Proyect Management 10

Product Backlog

EURO MPMEuropean MasterIn Proyect Management 11

Sprint Backlog

• User Stories that will be done during the Sprint

• The Team is compromised

• Assigned (Not a must)

• Re- estimated

• May divided in Sub-Tasks

EURO MPMEuropean MasterIn Proyect Management 12

Sprint Backlog

EURO MPMEuropean MasterIn Proyect Management 13

Sub-Tasks

No more than 16 hours

DONE-DONE

Implemented Tested Documented

EURO MPMEuropean MasterIn Proyect Management 14

Increment

• Part of the product developed in one Sprint

• It should be deployable if wanted

• Potentially shippable product

EURO MPMEuropean MasterIn Proyect Management 15

Meetings

Project Scope

Meeting

(Create first

Product Backlog)

Sprint Meeting

(Create Sprint

Backlog)

Daily Meeting

(Follow up and

update Burn

Chart)

Review Meeting

(Show the work DONE

during the sprint)

Retrospective

Meeting

(What goes well

and what not)

EURO MPMEuropean MasterIn Proyect Management 16

Project Scope Meeting

• Vision of the project

• First Product Backlog

• Prioritize the most important items

• First estimation of the project length

• Product Owner

• Team

• Stakeholder

EURO MPMEuropean MasterIn Proyect Management 17

Sprint Meeting

• Resources are known

• There is a valid Product Backlog

• PO and Team work together

• Scrum Manager moderate meeting

• The Team masters the needed technology to execute the work to be

done

BEFORE STARTING THE SPRINT

EURO MPMEuropean MasterIn Proyect Management 18

Sprint Meeting

Product Backlog

Developed Product

Other information

INPUT

OUTPUT

Sprint

Objective

Sprint

Backlog

Sprint

Planning

EURO MPMEuropean MasterIn Proyect Management 19

Sprint Meeting

Product Backlog

Exposition

1 Day Max

Sprint Backlog

Resolution

EURO MPMEuropean MasterIn Proyect Management 20

Sprint Meeting

• Same place, same time – Recommended

• All Team members must attend

• Stand-up meeting agile meeting

• Scrum Master moderates

• Product Owner invited to listen

EVERY DAY – MAX 15 minutes

Each team member answers three questions:

1. What did you accomplish yesterday?

2. What is your goal for today?

3. What is preventing you from accomplishing your goals?

EURO MPMEuropean MasterIn Proyect Management 21

Review Meeting

• Max 4 h

• Live demo of the development done – NO PPT

• Shouldn’t need any special preparation

• Only show what is REALLY working

Objectives:

• Check the work done

• PO accepts or not the work

• Feedback for the evolution of the Backlog

• No criticism on this meeting

• New Sprint meeting date

At the end of the Sprint

EURO MPMEuropean MasterIn Proyect Management 22

Retrospective Meeting

• After the review meeting

Objectives:

• Check what was well done – Repeat in the future

• Check what was not well done – Avoid in the future

When needed

EURO MPMEuropean MasterIn Proyect Management 23

Q&A

EURO MPMEuropean MasterIn Proyect Management 24

References

www.scrummanager.net

Flexibilidad con Scrum -- http://www.navegapolis.net/content/view/905/89/

(Juan Palacio) https://www.safecreative.org/work/0711140303769