Scrum

-
More useful if the problem is complex
-

Project team and customers cannot predict what they want

scrum > take the problem and break into smaller chunks
F- E-commerce website
g.
Accountability Product Owner Developers Developers
Product Backlog Sprint Backlog
( To do list ) of the top Increment
( few
-

- the ones on top to-do items)

are more important

|↳
SPRINT
sign Up "^" "
sign Up
>
> ↳9in
duration at most.

CMT PLANNING
one month

pay
:

Keep running the sprint and refining the product backlog .

-
have enough knowledge improve to our to-do list
-
with acquired knowledge from each increments
-
until customer decides that the product is good enough or no more budget
to make this work

scrum has 5 events

1. Sprint (container)
2. Sprint Planning
3. Sprint Review ( inspecting the increment and adapting product backlog)
4. Sprint Retrospective .
( team 's continuous improvement inspecting the team &
,
adapting)
5 .
Daily Scram (short meeting that happens daily )
 IN hat is scrum ?
- A mechanism to optimize the value delivery system
-
Complex environment
whogt
Chaotic

complicated
↳
-
Rp,
1 I
> how
simple
-
In a complex environment ,
these is only one
thing that is known for sure :

You don't know

everything

← Hard to predict something in the beginning

-

Change along the way

guide changes!
•
scrum : -
A mechanism to
A FRAMEWORK that can use foundation to
you as a
-

work on complex problems

what are the types of changes ?

-
effectiveness ; delivering the right product
-

efficiency ;
how would
you deliver making
-
the team the people
work the best
way possible

Traditional ( predictive waterfall) , Agile

-

plan & execute -

responding to change
-

good for projects which you -

deliver in shot cycles
don't expect much change -
get feedback after each deliverable
-

getting to the correct product by

reducing waste
lean
 Manifesto for Agile Software Development
Individuals and interactions over processes and tools

working software over comprehensive documentation

customer collaboration over contract negotiation
Responding to
change over
following a plan

12 Agile Principles in 4 categories

-

project
-
product
-
people
-

process

of
cone
Uncertainty ( How
uncertainty varies through time ]
The evolution of product 's knowledge over time
a

Project snaps product snG@nC.gzIpz5ioo.usBones

- Estimates (time & cost ) are subject to large uncertainty
Research and development iqngn.no information :aprpmqE
ago
-
Uncertainty tends to decrease , reaching zero ,
which usually happens by
the end of project

scrum Definition
-

lightweight
framework
-

generate value through adaptive solutions

-
for complex problems /environment
scrum master is required to foster an environment where :

1. Product Owner orders the wook into a product Backlog

2. Scrum Team turns a selection of work into an Increment

3. Scrum Team and its stakeholders inspect the results and adjust
for the next sprint
4 Repeat
.
 lnlhich agile aspect claims that overtime must be avoided ?
-
Sustainable Pace

Scrum Framework
- Rules , Events ,
Accountabilities, Artifacts
① Product Backlog : contains all the work to be done
: maintained by the Product owner
makes sure that the top
items are the most important ones

: describes what will fulfill the product Goal

② Sprint Planning : Select some of the top Product Backlog items

into the Sprint Backlog

Sprint Backlog : contains the work to be done during the given sprint
performed by the developers lasts at most one month
:
expectation alignment between business and
promotes
technical people
Daily Scrum : the Developers run this daily to synchronize their
work and maximize chances of achieving the
sprint Goal defined during Sprint Planning
Sprint :
During sprints the moment a Product Backlog item
meets the Definition of Done , an Increment is born
Increment :
A concrete
stepping stone toward the Product Goal
at Sprint Review Product owner and invited stakeholders inspect

[
run :

the end of
the produced increment , give informed feedback
a sprint that might impact the product backlog

sprint Retrospective : Inspects and adapts how the work is

being done improving continuously ,

scrum Master : Responsible for scrum running smoothly

 Pwducttbacklog
Artifacts
/ Sprint Backlog
Increment
* Serum is a series of
rolling wave
plannings
Product Owner The Scrum Master observes and supports the

( Developers
*

Roles team making scrum work .

Scrum Master
Sprint Product Backlog retirement

(
-

Sprint Planning does not just happen here .

Events It ongoing process in which

Daily Scrum is
-

an

sprint Review the scrum team collaborates on

Sprint Retrospective the details of the Product Backlog

"

""
Increment
sprints
r
Review
>
Same
Work Structure
sprint
As
.

Retrospective
Sprint >

Backlog →
Sprint sprint I
7 4
'

Sprint

÷:*
"

>
Planning Daily
Ideas Samm
Product
Product
Back Backlog
iffnntpWÉ
just different versions of product backlog
-

Used for Sprint

product 1 and
Sprint unfired rer )
Owner
:* .
>
?⃝
Sprint Goal : Product Backlog items and the plan to deliver them are

defined in the Sprint Backlog

Increment : frequent delivery
Ready to go features
- -

wishing product
Definition of Done : - definition of what done means

brings a balance between delivering fast and

with quality
* we
always build on top of the past increment
If in sprint one we deliver an Increment
,
with poor quality ,
this will
certainly
negatively affect future work

Scrum
Theory
Scrum is founded on Empiricism and Lean Thinking .

Empiricism : knowledge comes from experience and making decisions based on

what is observed
LeanThinking : reduces waste and focuses on the essentials .

Empiricism
Transparency : -
to have a common standard so that all the observers
share a common
understanding of what is being seen

knowing about the work done , challenges and the

team 's neat steps
-
in artifacts to make everybody have an aligned
understanding of the artifacts .

Inspection : artifacts and progress towards Sprint Goals mustbe

frequently inspected
Adaptation : whenever deviation is detected outside the acceptable
limits ,
adjustments must be made

Have opportunity to inspect and adapt during the four events

 Scrum Values
Commitment : Personally commit not just get involved
,

Courage : to do the right thing to solve tough problems

Focus :
everyone focuses on the wook of the sprint and the goals
of the scrum Team
Working on what is more important first
.

open cess : scrum Team and stakeholders agree to be open about all
the work and the challenges with performing the work
: Good teamwork , asking and offering help when needed &
admit mistakes
Respect : Scrum Team members respect each other to be capable ,

independent people

Question lnlhich Scrum value is manifested information radiator

when an

such as burn down burn up or cumulative flow chart is made

,

available so that everyone can see it ? (choose the best answer)

a) Openness A- correct answer

b) Communication ✗

c) Adaptation ✗

d) Transparency d- sounds correct but this is not a scrum Value

e) Simplicity ✗
 The Scrum Team
- to people or bees / multiple cohesive scrum team
product goal product backlog product owner
same
, ,

Product owner : a business person , takes case of product backlog

Developers : form the ideas sehested in the product backlog
into increments
scrum Master : make serum run
smoothly
scrum Team : - all product related activities
- accountable for creating a valuable usable
,

increment sprint
every
-
self -
managed & cross-functional

Product Owner Developers Scrum Master

-
Value maximizer -
transform Product Backlog -
accountable for
-
Product Backlog items into a usable Increment Scrum Team 's
Management -
Cross-functional effectiveness
/ \ - self -

managed -

establishing Scrum
Product Product -

remove impediments
Goal
Backlog Items -
leads and facilitates
Transparent Order Scrum adoption
- have
authority
* Product owner and scrum Master can be a
part of the Developers .

Q .
How does the Scrum Master help the Product owner ?
A •
Helping the scrum Team understand the need for clear and concise
product Backlog items
•
Helping find techniques for effective Product Backlog Management
•
Leading and coaching the organization in its scrum adoption

* Scrum Master can serve different serum Teams at the same time
 Product Backlog Refinement : Product owner + Developer
-

breaking down and further defining Product Backlog items

into smaller , more precise items .

-
Scrum Master might facilitate and coach the retirement
but not directly responsible

* The undone work must not be part of an increment .

The increment is only composed of work that adheres to the

Definition of Done .

* The undone work must not be part of the sprint Review .

Scrum Master Scrum Team

Teaching& Coaching Self -

Management
Impediment Removal

Question Inlho has the final say on the Product Backlog ordering ?
Ans : Product Owner
Estimates → Ans : Developers
 Scrum Artifacts
Product Backlog Sprint Backlog
, ,
Increment

Artifact Commitment
Product Backlog Product Goal
Sprint Backlog Sprint Goal
Increment Definition of Done

Artifact Transparency
If the Increment is not representative of the Product Backlog ,

inspecting the Increment would be useless too .

Product Goal
-
Contained within the Product Backlog
- Describes the future state of the Product

what fulfills the Product Goal?

-
The rest of the Product Backlog

Product Goals are

stepping stones towards the Product Vision
Increments are concrete stepping stones towards the Product Goal .

Who is accountable for the Product Goal ?

-
Product owner

* A product is a vehicle to deliver value It has .

a clear boundary ,

known stakeholders well defined

,
-

users or customers .
A product
could be more abstract
a service ,
a
physical product or
something
Backlog
"
Product Goal reach GER entire Product @Earpoof
•
*
.
Done
Product Backlog
• An emergent ,
ordered list of what is needed to improve the product .

•
Defines what will fulfill the product goal .

•
A product has a single product backlog .

artifact
As the product is
• The Product Backlog is a
living .
<

inspected we can
,

have more
Features : It is complete
never
items
product Backlog
dynamic
.

: It is
: As long as product exists
a
,
its Product Backlog also exists

card As an [ actor]
User story conversation I need to [ action]
Confirmation so [ do]
* Usually higher ordered (top]
,
Product Backlog items
are clearer and more detailed than lower ordered ones . .

The Product Owner orders the Product

•
Backlog considering
whatever he/ she judges as appropriate .

o Size o Risk o Value Dependencies

o

Value
Kano Model
°
Mandatory o Linear o exciter
must include in
product Backlog

Product Backlog Management

o
Ordering Product Backlog items
o
Developing and explicitly communicating the Product Goal
o
Ensuring that the Product Backlog is transparent ,
visible
and understood
o
Creating and clearly communicating Product Backlog items .
 Product Backlog Refinement
•

Emergent → continuously refined during the product development

collaboratively by the scrum Team .

• The actof breaking down and further defining Product Backlog items
into smaller precise items
more

Usually it is what enables getting top product items

•
,
the
Backlog
Ready
• The Scrum Team decides how and when refinement is done
• How much partof the capacity should retirement consume is
up to the scrum
Team .

• For each selected Product Backlog item, the Developers plan the work
necessary to
create an increment that meets the Definition of Done .

This is often done by decomposing Product Backlog items into one

day or less .

How this is done is at the sole discretion of the Developers . No one else

tells them how to turn Product Backlog items into incremental value .

Monitoring Progress Towards Goals

Three projective practices ;
burndown burn up and cumulative flow
,
Bum down chart
-
Buon up chaste -

effort (point ) point •

? ?

µ
•
• • •

too too

\
85 -

→ time (sprint ) isprint

cumulative flow Done

point not Done

^

4.1*1
In progress

µ
too -
too

.
> sprint ABM >
Sprint Goal
o The single objective for the sprint
o The Scrum Team defines Sprint Goal during the sprint Planning
and added to the Sprint Backlog
o Developers can collaborate with the Product owner to negotiate
the scope of the sprint Backlog without affecting the sprint Goal .

Increment
•
Commits to the Definition of Done
Additive to all prior increments and verified
•

thoroughly , ensuring
that all increments work together .

Definition of Done
• The moment a Product Backlog Item meets DoD, an increment
is born

If the Product Item does not meet DoD it cannot be

•
Backlog ,

released or even presented at

sprint Review the
-

It returns to the product Backlog for future consideration

who defines DoD ?

-
the Organization or the scrum Team
-
if it is not an organizational standard, the scrum Team must
create a Definition of Done appropriate for the product

Each Increment has only a single DoD .

• DoD can be modified

Technical Debt
•
Consequences of poor software development practices
•
Might lead to code decay and architecture deterioration .

• Scrum can manage it

Increment

•
The increment is the sum of all the Product Backlog items
completed t
• For second sprint + value delivered of all
previous sprints
• Whenever a Product Backlog item meets Definition of Done ,

an increment is born
:. Multiple increments may be created within a sprint
The increment must
•
always
be in usable condition

I. You don't need to release an increment at the end of

every sprint .

•
Increment supports empiricism .

•
The scrum Team can release it whenever it feels like it is
valuable .

2. The sprint is not a gate ; release might be performed during

a sprint .

•
The increment is the sum of all the Product Backlog items completed
during the sprint .

Impediment List
- done
by scrum Master
-
The Scrum Team prioritizes the list and works on them in order
-
The Scrum Master discusses the impediments with the serum Team .
 Scrum Events

Sprint container of all other scrum Events;

is a

sprint Planning Daily scrum , sprint Review Sprint Retrospective

, ,
.

• To keep the scrum Team focused all events are time boxed
-

Sprint : 1 month ( Max)

/
Sprint Planning : 8 hours ( max for a one-month Sprint) for shorter
minutes sprints
Daily screen : 15 u ,

the time is
Sprint Review : 4 houses ( fora one-month Sprint )
sprint Retrospective :3 houses u usually shooter

• These events are a formal opportunity to inspect and adapt

something .

•
Optimally ,
all events are held at the same time and place to
reduce complexity .

Sprint planning
-
The Product Owner must have a set of Product Backlog items
and their mapping to the Product Goal .

Who ? → scrum Team + Invited Stakeholders

How ? →

1 .

Why is this Sprint valuable ? Sprint Goal Scrum Team

ftp://ep.LI?;?:?-;?:!-
" ••↳ seeded Items *ease.

3 .
How will the chosen work get done ? Work Plan Developers
often done by decomposing Product Backlog items into smaller work items of

•
The sprint hood + the Product Backlog items for thesprint -1
the plan for delivering them
Sprint Backlog
fixed

Sprint select@ an
+
Goal Product Backlog Items
Why
? What ? How ?

• Commits to sprint Goal

• Planned by developers
•
Updated throughout the sprint as more is learned .

•
Inspect progress in the Daily scrum
•
Developers collaborate with Product Owner to negotiate the scope
of the sprint Backlog within the sprint without affecting the
sprint Goal .

The Sprint
•
A new Sprint starts immediately after the conclusion of the
previous Sprint .

•
Time boxed at most
-

, ,
one month
•
Helps the scrum Team to control risk
•
Must have fixed durations
•

During the sprint

0 No changes are made that would endanger the sprint Goal
0
Quality goals do not decrease
o The Product Backlog is refined needed as

0
Scope may be clarified and re negotiated with -
the Product owner as

more is learned
Cancelling a sprint

o
Only the Product owner has the authority to cancel the sprint .

o A sprint can
only be cancelled when the sprint Goal becomes obsolete

various practices exist to forecast progress like ,

burn downs , burn ups,
- -

or cumulative flows While proven useful these do not replace the

.
,

importance of empiricism .

The Development Work

0 Since the team is cross -
functional, they must be able to do all the work

necessary to deliver the Increment .

Daily most minutes)

scram ( at 15

inspect
0
Developers talk about their progress towards the sprint Goal
and to adapt the sprint Backlog as needed .

'

o Scrum master ensures that the meeting takes place & time box -

0
Identify impediments that prevent them from the
reaching
sprint Goal

Sprint Review
(at most 4 hours )
o To inspect the outcome of the sprint and determine future adaptations .

0 The undone work should not be demonstrated during the sprint Review
o
Only the Increment is demonstrated during the sprint Review .

o The Sprint Review is about transparency and collaboration .

o The Scrum Team presents the results of their work to key stakeholders
and progress towards the product goal is discussed

Sprint Review is NOT a formal demo session .

It is a formal opportunity for inspecting and adapting .

Sprint Retrospective (at most 3 hours for a one - month Sprint)

• To plan ways to increase quality and effectiveness

•
Opportunity for the scrum Team to reflect on their methods and

teamwork
•
The Scrum Master ensures that the event is positive and productive .

• 3 Questions
° What went well during the sprint ?
What didn't well ?
go
o

o How can we improve ?

• DoD can be reviewed and adapted
• The most impactful improvements are addressed as soon as possible .

They may even be added to the Sprint Backlog for the next sprint
.

Scaled Sorum
having multiple scrum teams working on one product ( 3- q Scrum Teams )
•
one Product Backlog ,
one product Goal, one Product Owner
•
one integrated Increment
when multiple scrum Teams develop one Product their work should
,

be
integrated into a single Product Increment
•
at least with every sprint .
If possible ,
even multiple times per sprint
what is the function or purpose of Management is scrum ?
-

Support the Product owner with insights and information into high
value product and system capabilities Support the scrum .
Master to

encourage organizational change that fosters empiricism ,

self-management bottom-up intelligence and intelligent product delivery

, ,
.