Scrum Training

By Abderrahmen Mokrani
Project management, is the application of
knowledge, skills, tools, and techniques to
project activities to meet the project
requirements
Waterfall Management
The Waterfall Model was the
first Process Model to be
introduced. It is very simple to
understand and use. In
a Waterfall model, each phase
must be completed before the
next phase can begin and
there is no overlapping in the
phases. The waterfall model is
the earliest SDLC approach
that was used for software
development.
Agile, What is it ?
• Agile methodology is a type of project management process, mainly
used for software development, where demands and solutions evolve
through the collaborative effort of self-organizing and cross-functional
teams and their customers.

• It is a methodology that is commonly used to deliver complex projects

due to its adaptiveness. It emphasizes collaboration, flexibility,
continuous improvement, and high quality results. It aims to be clear
and measurable by using six main “deliverables” to track progress and
create the product.
Agile Values
•Individuals and interactions over processes and tools

•Working software over comprehensive documentation

•Customer collaboration over contract negotiation

•Responding to change over following a plan

Agile Frameworks
Scrum

XP Agile Kanban

SAFE
What is
Scrum ?
What Is Scrum ?
• Scrum is a container framework

• Focus on collaboration, within which people can address complex

adaptive problems, while productively and creatively delivering
products of the highest possible value.

• Scrum is :
• Lightweight,
• Simple to understand
• Difficult to master
What Is Scrum ? : Scrum Pillars

SCRUM
Transparency

Adaptation
Inspection
empiricism
 What Is Scrum ? Scrum Pillars
Transparency
• Providing visibility of
information about the work
and the outcome.
• Using common standards for
information so that observers
will share the common
interpretation and
understanding.
• By transparency, the
significant aspects of the
work must be visible to those
responsible for the outcome.
Inspection
• performing frequent reviews
of the Scrum artifacts and
progress towards the Sprint
Goal to get early feedback on
undesirable variances.
Adaptation
• performing adjustments if the
inspection finds variance
beyond acceptable limits, and
hence the resulting product
will be unacceptable. The
Scrum Team has collective
responsibility to make the
adjustments as soon as
possible to minimize further
deviation.
What Is Scrum ? Empiricism
• Scrum is founded on empirical process control theory, or empiricism

Empiricism asserts that knowledge comes from experience and

making decisions based on what is known

In an empirical process, information is gained by observation

empirical processes are best for complex problems

 What Is Scrum ? Empiricism : How it works.
Inspection and
adaptation

frequently inspect where

The frequency depends
we are so that we can
on how much risk we
adapt our next steps to
want to take
optimize the results

The more we go off target, the greater

The greater the unknown, the more
the waste to reorient us, undo the
quickly we can go off target
useless work, and start again.
 What Is Scrum ? Empiricism : How it works.
The events of Scrum set the frequency of the inspection and adaptation, where the artifacts contain the information to be inspected and
adapted

EVENT INSPECTION ADAPTATION

• Product Backlog • Sprint Backlog
Sprint Planning • Commitment Retrospective • Sprint Goal
• Definition of Done
Daily Scrum • Sprint Goal • Sprint Backlog
• Sprint Progress • Daily plan
Sprint Review • Increment • Product Backlog
• Product Backlog
Sprint Retrospective • Team and collaboration
• Technology and engineering • Actionable improvements
• Definition of Done 

These are the formal events that Scrum foresees as opportunities to inspect and
adapt to the actual situation
What Is Scrum ? Scrum Values.
 What Is Scrum ? Scrum Values.
Commitment Courage Focus Openness Respect
• Of every team • To work on tough • Of the team on • Of the Scrum • Each other as
member to problems prioritizing and Team and its capable and
achieve the goals • To do the right completing the stakeholders in independent
of the Scrum thing by accepting Sprint work to expressing and people so that it
Team that the future achieve the goals facing the facts can provide a
• In following the cannot be of the Scrum and truths about trustworthy
pillars of predicted and Team all the work and environment to
empiricism and responding to • Helps to avoid challenges learn and share.
self-organization emerging change doing other • to collaborate
and using them to • Helps everyone to things not related
achieve the goals be grounded in to the Sprint Goal
reality, not giving
into personal
pride.
Scrum is a framework not methodology
Ball Point Game
The rules :

• You are one big team

• Ball must have air-time
• No ball to your direct neighbour
• Start Point = End Point
• Iteration = 2 min
• In between = 1 min
• We play 5 iterations
Scrum Roles
 Scrum
Roles :
Scrum Team
 Scrum Roles : Scrum Team

Accountability

Characteristics

Scrum
Team

Size
Scrum Team : Characteristics
• Team members share the same
Sharing norms and rules

• The Scrum team as a whole is

Accountability accountable for the delivery

Autonomy & • It is working as autonomous and

Self-organization self-organized as it is possible
Scrum Roles : Accountability

The Scrum Team as a whole is responsible to deliver the committed

delivery in time and with the defined quality.

A good result or a failure is never attributed to a single team member

but always the result of the Scrum Team.
 Scrum Roles : Size
• Scrum Teams are small. The ideal size is 7 +/- 2 people.

Why ?

• If there are more : communication overhead gets too large

• If there are less : performance and quality won’t be as good as needed
Scrum Roles : Members
 Scrum Roles : Product owner
Who ? :
• The sole person responsible for managing the Product Backlog
• He is ONE PERSON / Team

How ? :
• Clearly expressing Product Backlog items.
• Ordering the items in the Product Backlog to best achieve goals and missions.
• Optimizing the value of the work the Development Team performs.
• Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum
Team will work on next.
• Ensuring the Development Team understands items in the Product Backlog to the level needed.
Scrum Roles : Product owner
Expectations :

act as the ultimate owner of the product. Even the top executive of
the company needs to support Product Owner in his/her ownership
of the product.

maximize the value of the product by constant collaboration with

stakeholders and defining the product needs.
 Scrum Roles : Product owner
Key Responsibilities :

• Ensure that good economic decisions are continuously being made at the release, sprint, and
product backlog levels.
• Participate in the product & release planning activities.
• groom of the product backlog, which includes creating and refining, estimating, and prioritizing
product backlog items.
• Define the acceptance criteria for each product backlog item (functional and nonfunctional are
met ).
• Collaborate with the development team on a frequent basis.
• Is the single voice of the entire stakeholder community, internal and external.
 Scrum Roles : Product owner
Key Responsibilities :

• Maintain the Product Backlog Order by sequencing the items to best achieve
goals and missions.
• Maintain the Product Backlog Content by clearly expressing Product Backlog
items and by updating it with the latest insights and customer/market needs.
• Maintain the Product Backlog Availability by ensuring that the Product Backlog is
visible, transparent, and clear to all, and shows what the Scrum Team will work
on next.
Scrum Roles : Product owner
Summary

• Product Owner can delegate one or more responsibilities to others in the team. But
they are still accountable for product value
• No one can change the Product Backlog other than Product Owner.  However,
Development Team/Scrum Master/stakeholders can recommend the items that could
be added to Product Backlog
• No one can cancel the Sprint other than Product Owner. But, Development
Team/Scrum Master/stakeholders can influence the Product Owner to take that
decision
• If a stakeholder or customer needs to communicate anything to the team, they should
direct such communications through the Product Owner
Scrum Roles : Scrum master
Who ?
• A servant leader, responsible for ensuring Scrum is understood and enacted.
How ?
• Coach the Scrum team (both the development team and the product owner. )
• Ensure that its highest-priority needs of the scrum team are being met.
• Ensure that the Scrum team enacts and adheres to the Scrum values,
principles, and practices along with the Scrum team’s specific approaches
• Remove impediments that inhibit the team’s productivity 
Scrum Roles : Scrum master, Serving the PO
• Ensures that goals, scope, and product domain are understood by
everyone on the Scrum Team.
• Finds techniques for effective Product Backlog management.
• Understands product planning in an empirical environment.
• Ensures the Product Owner knows how to arrange the Product
Backlog to maximize value.
• Facilitates Scrum events as requested or needed.
Scrum Roles : Scrum master, Serving the DT
• Coaches the Development Team in self-organization and cross-
functionality.
• Helps the Development Team to create high-value products.
• Removes impediments to the Development Team’s progress.
• Facilitating Scrum events as requested or needed.
• Coaches the Development Team in organizational environments in
which Scrum is not yet fully adopted and understood.
Scrum Roles : Scrum master, Serving the
Organization
• Leads and coaches the organization in its Scrum adoption.
• Plans Scrum implementations within the organization.
• Helps employees and stakeholders understand and enact Scrum and
empirical product development.
• Causes change that increases the productivity of the Scrum Team.
• Works with other Scrum Masters to increase the effectiveness of the
application of Scrum in the organization.
Scrum Roles : Development Team
Who ?
• A team responsible for doing all of the work to produce one or more
slices of working product functionality each sprint, including the
design, development, integration, and testing of that functionality.
Characteristics
• Self-organized: No one (not even the Scrum Master) tells the
Development Team how to turn Product Backlog into Increments of
potentially releasable functionality.
Scrum Roles : Development Team
Characteristics
• CROSS-FUNCTIONAL: The team is unified in such a way that there are
no specialist roles or sub-teams. Individual Development Team
members may have specialized skills and areas of focus, but
accountability belongs to the Development Team as a whole.
• • High-Bandwidth & Transparent Communications:  Development
team members need to communicate with one another, as well as
with the product owner and Scrum Master, in a high-bandwidth &
Transparent manner, where valuable information is exchanged quickly
and efficiently with minimal overhead.
Scrum
Events
Scrum Events
Scrum encourages us to hold five key
events during a Sprint, all intended
to help us work efficiently and closely
together, as well as to improve our
knowledge and become more
effective in the future.
These five events are:
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
• The Sprint
Scrum Events : The Sprint
• Sprint is the heart of Scrum.
• Sprint is time boxed : can’t be longer than a month
• An increment is delivered at the end of each Sprint
• ONLY the product owner can cancel a sprint ( usually when the
sprint goal becomes obsolete )
• Sprint includes all the events and the development work
Scrum Events : The Sprint Planning
Meeting
• An 8 hours meeting long for a
month long sprint.
• The meeting is composed of two
parts : What meeting and How
meeting.
• All the scrum team is invited to
participate.
• Members outside the scrum team
can participate, under the request
a member of the scrum team.
Scrum Events : The Sprint Planning
Meeting
Scrum Events : The Sprint Planning
Meeting
Sprint Planning
Meeting

Sprint backlog Sprint goal

What ? how ?
Scrum Events : The Sprint Planning
Meeting
What Meeting :
• First leg of the sprint planning meeting.
• During witch the development Team forecasts the Product Backlog
Items it will deliver in the Sprint and the sprint goal.
• The Sprint Goal is a tool for team coherence. The selected Product
Backlog Items deliver one coherent function, which can be the Sprint
Goal.
•  As the Development Team works, it keeps the Sprint Goal in mind
Scrum Events : The Sprint Planning
Meeting
How Meeting :
• Second leg of the sprint planning meeting.
•  The Development Team decides how it will build this functionality
into a “Done” product Increment during the Sprint.
Scrum Events : The Daily Meeting
• A daily meeting that usually happens at the same time same place.
• The daily meeting is timeboxed event that doesn’t exceed 15min.
• The daily meeting is a dev. team exclusive event.
• The scrum can attend the daily meeting to ensure that the
Development Team has the meeting & keep it within the 15 min.
Scrum Events : The Daily Meeting
During the daily meeting :
• The team discuss the progress thus far. This is done by inspecting the work
done since the last Daily Scrum.

In addition, the Development Team members explain:

• What did I do yesterday that helped the Development Team meet the Sprint
Goal?
• What will I do today to help the Development Team meet the Sprint Goal?
• Do I see any impediment that prevents me or the Development Team from
meeting the Sprint Goal?
Scrum Events : The Sprint Review
Meeting
• A meeting that happens at the end of the sprint.
• A 4 hours meeting for a sprint that takes a month.
• A Meeting that Stakeholders and scrum team are required to attend.
• During this meeting the Scrum team and the stakeholders inspect
what is done and figure out what to do next.
Scrum Events : The Sprint Review
Meeting
• The Sprint Review
provides an
important
opportunity for
the Scrum team
to get feedback
from people who
typically are not
available on a
daily basis during
sprint execution
Scrum Events : The Sprint Review
Meeting
What happens during the sprint Review :

• The Product Owner explains what Product Backlog Items have been
“Done” and what has not been “Done.”
• The Product Owner discusses the Product Backlog as it stands. They
project the likely completion date based on progress to date, if
needed.
Scrum Events : The Sprint Retrospective
Meeting
• The Sprint Retrospective is a formal opportunity where the Scrum Team
inspects itself and creates a plan for improvements for the next Sprint.
• This is a three-hour time-boxed meeting for one-month Sprints. For
shorter Sprints, the event is usually shorter.
• The Scrum Master encourages the Scrum Team to improve its
development process and practices.
• The Scrum Team plans ways to increase product quality by adapting the
definition of “Done.”
• The outcome is a list of identified improvements that will be
implemented in the next Sprint.
 Scrum
Artifacts
Scrum Artifacts
Scrum’s artifacts represent work
or value to provide transparency
and opportunities for inspection
and adaptation. Artifacts defined
by Scrum are specifically
designed to maximize
transparency of key information
so that everybody has the same
understanding of the artifact.
Scrum Artifacts : Product Baclog
• The Product Backlog is an ordered list of everything that is known to
be needed in the product.
• It is the single source of requirements for any changes to be made to
the product
•  The Product Owner is responsible for the Product Backlog, including
its content, availability, and ordering.
Scrum Artifacts : Product Backlog
• The Product Backlog is an ordered list of everything that is known to
be needed in the product.
• It is the single source of requirements for any changes to be made to
the product
•  The Product Owner is responsible for the Product Backlog, including
its content, availability, and ordering.
• A Product Backlog is never complete
•  If a product exists, its Product Backlog also exists.
Scrum Artifacts : Product Backlog
Product Backlog Refinement :
•  It is the act of adding detail, estimates, and order to items in the
Product Backlog.
• It is an ongoing process in which the Product Owner and the
Development Team collaborate on the details of Product Backlog
items.
• During Product Backlog refinement, items are reviewed and revised. 
Scrum Artifacts : Product Backlog
Qualities of the Product Backlog :

Detailed Appropriately

Estimated

Emergent

Prioritized
Scrum Artifacts : Product Backlog
Qualities of the Product Backlog : Detailed Appropriately

• The product backlog items are detailed appropriately.

• Higher-priority items are described in more detail than lower-priority ones.

“The lower the priority, the less detail, until you can barely make out the
backlog item,” write Schwaber and Beedle.

Following this guideline keeps the backlog concise and ensures that the items
likely to be implemented in the next sprint are workable.
Scrum Artifacts : Product Backlog
Qualities of the Product Backlog : Estimated
• Each product backlog item has a size estimate corresponding to the
effort required to develop the item.
• The product owner uses these estimates as one of several inputs to
help determine a PBI’s priority (and therefore position) in the product
backlog.
• Also, a high-priority, large PBI (near the top of the backlog) signals to
the product owner that additional refinement of that item is
necessary before it can be moved into a near-term sprint.
Scrum Artifacts : Product Backlog
Qualities of the Product Backlog : Emergent
• As long as there is a product being developed or maintained, the
product backlog is never complete or frozen.
• It is continuously updated based on a stream of economically valuable
information that is constantly arriving.
• The structure of the product backlog is therefore constantly emerging
over time.
• As new items are added or existing items are refined, the product
owner must rebalance and reprioritize the product backlog, taking new
information into account.
Scrum Artifacts : Product Backlog
Qualities of the Product Backlog : Prioritized

• All items in the product backlog are prioritized.

• The most important and highest-priority items are implemented first.
• They can be found at the top of the product backlog.
• Once an item is done, it is removed from the product backlog.
Scrum Artifacts : Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the
Sprint, plus a plan for delivering the product Increment and realizing
the Sprint Goal.

The Sprint Backlog is a forecast by the Development Team about what

functionality will be in the next Increment and the work needed to
deliver that functionality into a “Done” Increment.
Scrum Artifacts : Sprint Backlog
•  The Sprint Backlog is a forecast by the Development Team about
what functionality will be in the next Increment and the work needed
to deliver that functionality.
• The Sprint Backlog is a plan with enough detail that changes in
progress can be understood in the Daily Scrum.
• The Development Team modifies the Sprint Backlog throughout the
Sprint, and the Sprint Backlog emerges during the Sprint.
• As new work is required, the Development Team adds it to the Sprint
Backlog. As work is performed or completed, the estimated remaining
work is updated.
Scrum Artifacts : The Incriment
•  The Increment is the sum of all the Product Backlog items completed
during a Sprint and the value of the increments of all previous Sprints.
• At the end of a Sprint, the new Increment must be “Done,” which
means it must be in useable condition and meet the Scrum Team’s
definition of “Done.”  
• An increment is a body of inspectable, done work that supports
empiricism at the end of the Sprint.
• The increment must be in useable condition regardless of whether
the Product Owner decides to release it.
Scrum Artifacts : The Incriment
 Other
Materials
Definition of Done
• DoD is a checklist of the types of work that the team is expected to
successfully complete before it can declare its work to be potentially
shippable.
• In a definition of ‘done’ the conditions are expressed that need to be
met by an Increment of product in order for it to be ‘shippable’.  
• It is an overview of all the activities, criteria, tasks and work that need
to have been performed on a working piece of software in order to be
able to release it into production.
• Primary ownership of the definition of done lies with the
Development Team.
User Story
• User stories are short, simple descriptions of a feature told from the
perspective of the person who desires the new capability, usually a
user or customer of the system. They typically follow a simple
template:

As a < type of user >, I want < some goal > so

that < some reason >.
User Story
Who writes user stories?
• Anyone can write user stories.
• It's the product owner's responsibility to make sure a product backlog
user stories exists, but that doesn’t mean that the product owner is
the one who writes them.
• Over the course of a good scrum project, you should expect to have
user story examples written by each team member.
Poker planning
Useful Links
Agile glossary:
https://www.volkerdon.com/pages/agile-glossary

Scrum Guide : https

://www.scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-
US.pdf
Work Shop
• Building an Aero port Using the scrum Framework