Agile Frameworks: Scrum, Values, and Principles Presentation

Agile Frameworks
ICAM - mc2i
13/10/2025
Grégoire GUY
Rim SMAOUI
WELCOME!
Who are we ?
Rim SMAOUI
Manager
Retail
[email protected]
Gregoire GUY
Confirmed Consultant
Retail
[email protected]
3
Discover my journey
Engineering School
Generalist
Major in Information
systems and Logistics
2nd mission
Scrum Master & Agile
Coach BI FACTORY
(Finance Data &
People Data)
2021-2022
2016-2021
2025
2023-2024
2022-2023
1st mission :
Functional consultant
(AMOA) for an
Electronic Document
Management tool for
electrical service
connections
3rd mission
Scrum Master in
Logistics (WMS /
AS400)
2024-2025
Exceptional leave
One-year trip in North
America
4ème mission :
Agile Coach for Data &
Tech factory
Professeurs en entreprise - Novembre 2023
4
Découvrez mon parcours
Master in International
Project Management
Product Owner
In the Quality
department for the
Incident Request
system tool
2016-2021
2016
2023-2025
2022
2021-2022
Product Owner:
Projects related to
Energy savings
certificates and
renewable energy
contracts
Project manager
Migration of Solaris
stores to Sunglass Hut
Brand
2023
Product Owner
Implementation of Agile
framework (Scrum)
Adoption lead
Deployment of New
Point of Sale worldwide
for 7 brands of the
group
5
OUR JOB
Digital Transformation Consultant
Customer service
Expertise
Adaptability
Cultural, organisational,
technological
Business cases
Change management
Revolution!
Every field and every job
Source of innovation
Objective point of view
Advise and support
I
Management & KP
Data analysis
Align information systems with our clients’ strategy, support their digital transformation, adapt their organisation to
new ways of working
6
BEING A CONSULTANT
Works
for
clients
Works on
timed
missions
Is employed by
a consulting
firm
Operates in
various
contexts
A consultant…
Works with
other
consultants
Is able to
master new
topics
Likes to be
challenged
7
OUR
KEY FIGURES
36
years
of digital transformation
consulting
13
In 2024
%
/year
+1500 9 /10
employees including +
100 managing partners
of client satisfaction
8
THEY TRUST US
ENERGY ET
UTILITIES
TOTAL Energies
EDF
ENEDIS
RTE
ENGIE
GRDF
GRT Gaz
SUEZ
ORANO
VEOLIA
GREENYELLOW
SIAAP
TRAPIL
MOBILITY &
TRANSPORTATION
BANK,
FINANCE,
INSURANCE
SOCIAL CARE
PUBLIC SERVICES
TRADE & RETAIL
AGIRC ARRCO
Ministère des Finances
Carrefour
CNP
Ministère de la Justice
Les Mousquetaires
SNCF
BNP PARIBAS
CNAM
Ministère de l’Intérieur
Auchan
RATP
CREDIT AGRICOLE
CNAF
Ministère de l’Education
La Poste
IDFM
SOCIETE GENERALE
KLESIA
CISIRH
Fnac Darty
TRANSDEV
BPCE
ACTION LOGEMENT
AIFE
Decathlon
COMUTITRES
CAISSE DES DÉPÔTS
Mairie de Paris
Comptes du Luxe
AIR FRANCE
BANQUE DE FRANCE
INDUSTRY
AFD
EIFFAGE
LA BANQUE POSTALE
FAURECIA
AXA
L'ORÉAL
GROUPAMA
Région Ile-de-France
HEALTH
Région Hauts de France
Ville de Lyon
MEDIA
Ministère de la santé
Pôle Emploi
France TV
GIP SESAN
VNF
TF1
France Médias
Monde
APHP
Conseil d’Etat
M6
Havas
RENAULT
ANSM
Eurosport
Radio France
THALES
ARS IDF
Canal +
SFR
SAINT-GOBAIN
GHT
SAFRAN
9
INTRODUCTION
INTRODUCTION
WATERFALL APPROACH LIMITATIONS
AGENDA
Introduction
Statistics and figures
Agile frameworks… Why?
AGILE FRAMEWORKS
Agile Values
Agile Principles
FOCUS : SCRUM FRAMEWORK
Introduction
Responsibilities
Artefacts
Events
GOOD PRACTICES AND TOOLS
Good practices
Tools
CONCLUSIONS
Agile Frameworks
11
Key Outcomes
Présenter les principes
01
AGILES
Have a solid
understanding of key
agile concepts
02
03
Promote agile practices
Introduce agile
principles
04
Share tools and
techniques
Waterfall approach
limitations
Tell us…
1) Have you heard about the “Waterfall” concept when it comes to managing the
development of a product ?
2) What are the limitations of such approach ?
Agile Frameworks
14
“Waterfall” limitations
TUNNEL
DELAY
STUCK
LACK OF
REACTIVITY
INCOMPLETE
CUSTOMER
NEEDS
COST
PO / PM
Agile Frameworks
15
Statistics
AGILE vs WATERFALL
Waterfall projects
0-10% dif.
Agile projects
10-20% dif.
+20% dif.
According to Standish Group 2018
Agile Frameworks
16
Agile Frameworks… Why?
Focus on what works!
If you are on the wrong path, you better realize it quick!
The more you breakdown a task, the simpler it becomes
In the 90-2000s, new frameworks start to appear and
allow IT managers to reduce the risk of failure when
developing products
Agile Frameworks
17
Agile Frameworks
Agile Values
The Agile Manifesto is the reference document (2001) grouping together the common values of several new project
methodologies that emerged in the 90s. It is the first document to unite these methodologies under the "Agile" label.
Individuals and interactions
Responding to change
over processes and tools
over following a plan
Working software
over comprehensive documentation
The 4
Agile
Values
Customer collaboration
over contract negotiation
Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries,
Jon Kern, Brian Marick,Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas
Agile Frameworks
19
Agile principle : iterative development
Iteration 1
Expression of
requirements
Iteration 3
Iteration 2
Specifica
-tions
Dev.
Testing
Iteration 4
Delivery
Short and steady length
Agile Frameworks
20
Agile principles
Deliver often : to reduce failure or
fail faster
Manage risks : regular
delivery check
Better quality : test in every iteration
Improve satisfaction : iterative review
and validation
Limit the tunnel effect : deliver a
finished increment at the end of
every iteration
Deal with complexity :
Breakdown complex items into
smaller ones
Agile Frameworks
21
Your turn!
TRUE OR FALSE?
1) There is no documentation in Agile projects
2) Testing is done only before releasing the product to end users
3) If the client’s need changes, we can integrate it in one of the following
iterations
Agile Frameworks
22
Focus on :
Scrum Framework
Scrum Framework
94%
of companies applying Agile Framework apply Scrum
framework
78%
apply Scrum mixed with other Agile Frameworks (e.g. KANBAN)
16%
solely apply Scrum
According to Scrum Alliance 2018
Agile Frameworks
24
Scrum Framework – Key Principles
Scrum Projects rely on sprints (= iterations !)
Sprint length is between 1 and 4 weeks (agreed upon at the beginning of the project)
Several events happen during and at every Sprint (Sprint Planning, Daily
Scrum, Sprint Review, Sprint Retrospective)
A steady Sprint length is crucial
An increment (partial product) is specified, developed and tested every Sprint
Agile Frameworks
25
SCRUM – Overview
Product Backlog
1 to 4 weeks
Sprint Backlog
Usable increment
SPRINT
Agile Frameworks
26
Your turn!
What would be the consequences of having 3-month long Sprints?
What are the differences between a Product Backlog and a Sprint Backlog?
Agile Frameworks
27
SCRUM
1
2
3
RESPONSIBILITIE
S
ARTEFACTS
EVENTS
Agile Frameworks
28
Responsibilities
PRODUCT
OWNER
• Defines and orders customers’ needs
• Updates the Product Backlog to reflect the current state of customers’
needs
• Defines and shares the Product Vision
SCRUM
MASTER
• Establishes Scrum values and principles within the team
• Facilitates problem solving
• Facilitates collaboration between team members
DEVELOPERS
• In charge of product development
• Display various and complementary technical capabilities
• Are self-managed and self-organised to reach the Sprint Goal
Agile Frameworks
29
Your turn!
1.
Product Development
Product Owner
2. Update the Product Backlog
Scrum Master
3. Scrum Values
4. Share Product Vision
Developers
5. Problem solving
6. Various and complementary technical
capabilities
Agile Frameworks
30
Your turn!
1.
Product Development
Product Owner
2. Update the Product Backlog
Scrum Master
3. Scrum Values
4. Share Product Vision
Developers
5. Problem solving
6. Various and complementary technical
capabilities
Agile Frameworks
31
SCRUM
1
2
3
RESPONSIBILITIE
S
ARTEFACTS
EVENTS
Agile Frameworks
32
Artefacts – Product Backlog
Product Backlog
User value
+
US 98
Value : 144
“As a customer, I want to
see the list of products in
order to manage my
inventory”
Effort : 5
The Product Backlog contains all known
customer’s needs to implement to the product
-
Split into User Stories
It is ordered by user value
Agile Frameworks
33
Artefacts – Ordering
Product Backlog
Sprint Backlog
+
-
US in stock
US blocked
US in refinement
US in refinement
+
US to be refined
-
User value
User value
Selected US
Agile Frameworks
34
Artefacts – Users Stories (US)
A User Story describes a functionality from a
user point of view
« As… I want… in order to… »
Each item is estimated and ordered :
US 98
« As a customer, I
want to see the list of
products in order to
manage my inventory
»
- « Value » : customer value
- « Effort » : to complete the US
Value : 144
Effort : 21
A User story must be :
Independent– Negociable – Valued – Measurable – Short - Testable
Agile Frameworks
35
Your turn!
TRUE OR FALSE?
A Product Backlog only contains the most urgent customer’s needs
OPEN QUESTION:
What is the #1 criterion when ordering a Product Backlog?
Agile Frameworks
36
SCRUM
1
2
3
RESPONSIBILITIE
S
ARTEFACTS
EVENTS
Agile Frameworks
37
The Sprint
A Sprint is an iteration during which ideas are transformed into value.
It's a period of time during which a piece of the product is "finished" and potentially usable by users.
It is the "container" event for all the ceremonies.
A new Sprint starts immediately after the
end of a Sprint.
Daily
Sprint Planning
SPRINT
EXECUTION
Sprint Review
Sprint
Retrospective
Sprint Planning
SPRINT N (1 to 4 weeks)
…
SPRINT N+1
During the Sprint:
• No changes that would affect the Sprint Goal are allowed.
• The composition of the development team and the quality objectives to be achieved may not be revised.
• The scope of the work to be done during the Sprint may be revised following discussions within the Scrum Team.
38
Sprint Planning
Content
Timebox: 2h / week Sprinting
Product Owner shares the product evolutions he envisions for this sprint to the rest of the
team
● The Scrum Team explores the Product Backlog and chooses a coherent Sprint Goal
● Developers (while discussing with the PO) select US to be developed for the next Sprint that
will fulfill the Sprint Goal and commit to it
If needed, a first US breakdown into tasks can be done by the developers
●
Sprint Backlog
At the end of this event, the Sprint Backlog is initialised:
•
•
•
Sprint Goal (Why?)
Selected US (What?)
A plan to reach the Sprint Goal (How?)
Agile Frameworks
39
Daily Scrum
Daily SCRUM
Timebox: 15 minutes, whatever the size of the team and the Sprint length
Everyday, ideally at the same time and same place to reduce complexity
Allows developers to synchronize themselves and evaluate how well they are doing
regarding achieving the Sprint Goal
3 key questions (example)
What did I do yesterday?
What is my plan for today?
Is there any impediment which keeps me from working towards the Sprint Goal?
Agile Frameworks
40
Sprint Review
Review
Timebox : 1h / week Sprinting
The Scrum Team presents the work that has been done during the Sprint
to stakeholders: final users, managers, operations, etc.
The Scrum Team gets feedback on the presented work
The Scrum Team and the stakeholders discuss on any work left and
identify future development requirements
In addition to delivering value to end user, one of the objectives of the Sprint Review is to make the audience react
and foster feedback and collaboration with them in order to get “leads” for future sprints.
Agile Frameworks
41
Sprint Retrospective
Retrospective
Timebox : 45 minutes / week Sprinting
The Scrum Team inspects how well they applied Agile principles and how well they worked
with each other. The aim is to step back and find areas for improvement for the next sprint
Appropriate themes for a Retrospective are tools, processes, individuals and their
interactions (communication)
Goal : Allow the Scrum Team to inspect themselves and ultimately identify ways to increase effectiveness and quality
Agile Frameworks
42
Your turn!
Sprint Planning
Daily Scrum
Sprint Review
Sprint
Retrospective
1.
Present the work that has been
done and collect feedback
2. Share current, short-term impediments
and evaluate how far we are from
achieving the Sprint Goal
3. Choose which US will be done in the
Sprint and set the Sprint Goal
4. Inspect ourselves in order to better
ourselves in the future
Agile Frameworks
43
Your turn!
Sprint Planning
Daily Scrum
Sprint Review
Sprint
Retrospective
Present the work that has been done and
collect feedback
Share current, short-term impediments
and evaluate how far we are from
achieving the Sprint Goal
Choose which US will be done in the
Sprint and set the Sprint Goal
Inspect ourselves in order to better
ourselves in the future
Agile Frameworks
44
SCRUM
1
2
3
RESPONSIBILITIE
S
ARTEFACTS
EVENTS
OVERVIEW
Agile Frameworks
45
Global schema
DAILY
PRODUCT
BACKLOG
BACKLOG
REFINEMENT
SPRINT
PLANNING
SPRINT
EXECUTION
SPRINT
REVIEW
SPRINT
RETRO
•Product review
•Feedback
•Self-Inspection
•Plan for
continuous
improvement
INCREMENT
TESTS
DELIVERABLES
•User Value
•Effort
•“Ready” US
•US selection
•Sprint Goal
•Work plan
•Development
•Synchronization
•Testing
•Usable
increment
Agile Frameworks
46
Your turn!
OPEN QUESTION:
Who decides who does what among the developers?
TRUE OR FALSE?
During a Sprint Review, the Scrum Team only present the work that has been done
Agile Frameworks
47
Good practices and tools
Some tools for Retrospectives
The Speed Boat
KEEP
KEEP
DROP
What works well
What doesn’t work
START
DROP
The team
START
What is unclear
Goal
UNCLEAR
Action to be taken
Agile Frameworks
49
Tools - Doesn’t have to be sophisticated
Product Backlog
Sprint Backlog
User Story
Agile Frameworks
50
Tools – But it can be sophisticated!
Product Backlog
Sprint Backlog
User Story
Agile Frameworks
51
The “Post-it” (KANBAN) method
BACKLOG
READY
TO DO
IN PROCESS
DONE
US summarily
described by the
PO or one of its
AMOA.
UDS detailed and
on-board fot the
next sprint.
US onboard SPRINT.
US being processed
by the team, which
can be broken down
into tasks
US finished and
validated by the
team.
US prioritized and
evaluated once by
the PO and the
team.
US refined by the
team, and possibly by
business/technical
experts.
US completed before
the end of the
SPRINT to be shown
during the
demonstration.
Agile Frameworks
52
ANY QUESTIONS ?
CONCLUSION
mc2i
51, rue François 1er - 75008 Paris
01 44 43 01 00
[email protected]
www.mc2i.fr