www.pentalog.fr

SCRUM VS V-CYCLE OCTOBER 2011

p e n t a l o g . c o m

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 2

Presentation goals

About SCRUM

About V-Cycle

Expectations

SUMMARY

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 3

About both models/frameworks

Instead of making a comparison step by step into both frameworks, we gathered generic organizational questions.

Audience: people with theoretical knowledge about both frameworks or basic knowledge about software manufacturing processes

PRESENTATION GOALS

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 4

ABOUT SCRUMIterative development

Daily collaboration

Enhanced visibility

Business integrated to the team

Intense communication

Frequent delivery and demo presentations

No hierarchy

Changes are welcomed

Sustained pace

Search of autonomy

Continuous improvement

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 5

ABOUT V CYCLE

Manufacturing through stage gates

Link between preparation and control

Sequential organization

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 6

I NEED TO START DEVELOPMENT FAST

V CYCLE

Requirements folder 100% completed

Detailed planning

I.A.D. Folder 100% completed

SCRUM

The complete list of stories in the backlog and their priorities

A sufficiently detailed description of stories for the first sprints

Work on the I.A.D on your first sprints

To start, you need :

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 7

I HAVE AN IMPOSSIBLE PROJECT

V CYCLE

We can evaluate this only when the development starts. This means after : Requirement, I.A.D phases are completed

SCRUM

We can evaluate this after the first sprints

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 8

REQUIREMENTS WERE NOT 100% UNDERSTOOD

V CYCLE

Customer needs are described in requirements

Presentation meetings are organized

The business analyst is available for questions

SCRUM

The Product Owner is integrated into the team

A global detailed view doesn’t exist at the beginning of the project

A daily meeting allows uncertainties to be clarified

A demo presentation is organized at the end of each sprint

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 9

I WANT TO HAVE VISIBILITY

V CYCLE

Weekly follow-up

After each phase of the project there is a clear view on the advancement of the project

Monthly planning updated and communicated between parties

SCRUM

At the end of the sprint : Team velocity is calculated.

Burndown chart is always present.

A demo is made for the Product Owner and Business Stakeholders may attend also

Product Backlog is continually updated.

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 10

I WANT TO HAVE THE BEST ESTIMATIONS

V CYCLE

The Project Manager makes the estimation.

The Project Manager can organize other estimations with experts to ensure current estimation is realistic.

SCRUM

The stories are explained in details by the Product Owner

The estimations are made by the team

Estimations are made in relative points. The capacity of the team is related to team’s velocity.

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 11

MY PROJECT MANAGER IS TOO MANDATORY

V CYCLE

The Project Manager will install a Team Leader to replace him during his absence

SCRUM

There is no Project Manager. The purpose of the Scrum Master is to build an autonomous team that could continue without him if needed.

The entire team value the openess on the project => making the advancement visible is not an individual activity.

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 12

I WANT TO CHANGE THE REQUIREMENTS

V CYCLE

Identify the impact on the project

Update the planning

Change delivery date

SCRUM

Add a new story in Product Backlog that could be inserted in future sprints backlog

To change, you need :

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 13

IT IS ALWAYS FINISHED « BUT »

V CYCLE

The Project Manager must organize control actions

SCRUM

Definition of Done

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 14

I WANT TO MAKE A PRESENTATION

V CYCLE

There is always a risk if there was no tests occurred yet

We need to wait for the acceptance

SCRUM

Every partial products delivered at the end of the sprint are tested

If sprint fulfills the DoD of the Sprint it can be used for demo presentations

If some necessary functionality is missing we can change the priorities for the next sprint.

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 15

I WANT A PROJECT OF VERY GOOD QUALITY

V CYCLE

There are some very important validation phases

Acceptance phase is mandatory

SCRUM

Continuous integration practices

Everyone is implicated in the quality of the project

O C T O B E R 2 0 1 1 S C R U M V S V - C Y C L E p e n t a l o g . c o m 16

WE MUST IMPROVE THE ORGANIZATION

V CYCLE

Strictly related to the capacity and involvement of the project manager and project director

Quality Audits

SCRUM

Retrospectives at the end of each sprints

It is one of the responsibilities of the Scrum Master

Quality Audits are still there

www.pentalog.fr

p e n t a l o g . c o m

THANKS FOR YOUR ATTENTION