Scrum VS V Cycle presentation

1. www.pentalog.fr
SCRUM VS V-CYCLE OCTOBER 2011
p e n t a l o g . com

2. SUMMARY
Presentation goals
About SCRUM
About V-Cycle
Expectations
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 2

3. PRESENTATION GOALS
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
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 3

4. ABOUT SCRUM
Iterative development No hierarchy
Daily collaboration Changes are welcomed
Enhanced visibility Sustained pace
Business integrated to the team Search of autonomy
Intense communication Continuous improvement
Frequent delivery and demo presentations
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 4

5. ABOUT V CYCLE
Manufacturing through
stage gates
Link between
preparation and control
Sequential
organization
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 5

6. I NEED TO START DEVELOPMENT FAST
To start, you need :
V CYCLE SCRUM
Requirements folder 100% The complete list of stories in the
completed backlog and their priorities
Detailed planning A sufficiently detailed description
of stories for the first sprints
I.A.D. Folder 100%
completed Work on the I.A.D on your first
sprints
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 6

7. I HAVE AN IMPOSSIBLE PROJECT
V CYCLE SCRUM
We can evaluate this only We can evaluate this after the
when the development first sprints
starts. This means after :
Requirement, I.A.D phases
are completed
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 7

8. REQUIREMENTS WERE NOT 100%
UNDERSTOOD
V CYCLE SCRUM
Customer needs are The Product Owner is integrated
described in requirements into the team
Presentation meetings are A global detailed view doesn’t
organized exist at the beginning of the
project
The business analyst is
available for questions A daily meeting allows
uncertainties to be clarified
A demo presentation is
organized at the end of each
sprint
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 8

9. I WANT TO HAVE VISIBILITY
V CYCLE SCRUM
Weekly follow-up At the end of the sprint : Team
After each phase of the velocity is calculated.
project there is a clear Burndown chart is always
view on the advancement present.
of the project A demo is made for the
Monthly planning updated Product Owner and Business
Stakeholders may attend also
and communicated
between parties Product Backlog is continually
updated.
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 9

10. I WANT TO HAVE THE BEST ESTIMATIONS
V CYCLE SCRUM
The Project Manager The stories are explained in
makes the estimation. details by the Product Owner
The Project Manager can The estimations are made by
organize other estimations the team
with experts to ensure Estimations are made in
current estimation is relative points. The capacity of
realistic. the team is related to team’s
velocity.
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 10

11. MY PROJECT MANAGER IS TOO MANDATORY
V CYCLE SCRUM
The Project Manager will There is no Project Manager.
install a Team Leader to The purpose of the Scrum
replace him during his Master is to build an
absence 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.
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 11

12. I WANT TO CHANGE THE REQUIREMENTS
To change, you need :
V CYCLE SCRUM
Identify the impact on the Add a new story in Product
project Backlog that could be inserted
in future sprints backlog
Update the planning
Change delivery date
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 12

13. IT IS ALWAYS FINISHED « BUT »
V CYCLE SCRUM
The Project Manager must Definition of Done
organize control actions
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 13

14. I WANT TO MAKE A PRESENTATION
V CYCLE SCRUM
There is always a risk if Every partial products
there was no tests delivered at the end of the
occurred yet sprint are tested
We need to wait for the If sprint fulfills the DoD of the
acceptance Sprint it can be used for demo
presentations
If some necessary
functionality is missing we can
change the priorities for the
next sprint.
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 14

15. I WANT A PROJECT OF VERY GOOD QUALITY
V CYCLE SCRUM
There are some very Continuous integration
important validation practices
phases Everyone is implicated in the
Acceptance phase is quality of the project
mandatory
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 15

16. WE MUST IMPROVE THE ORGANIZATION
V CYCLE SCRUM
Strictly related to the Retrospectives at the end of
capacity and involvement each sprints
of the project manager It is one of the responsibilities
and project director of the Scrum Master
Quality Audits Quality Audits are still there
OCTOBER 2011 SCRUM VS V-CYCLE pentalog.com 16

17. www.pentalog.fr
T H A N K S F O R Y O U R ATT E N T I O N
p e n t a l o g . com