AGIL E PROJ EC T MANAGEMENT

Scrum Methodology
Index

Scrum Methodology
What

Why

When

Differences w/ Waterfall

How

Scrum Inputs

Scrum in HUGO BOSS IZMIR

Project Examples
 What is Scrum?

It is a methodology
which focuses on
producing the worthiest output
within the shortest period of
time.
So, instead of a large group spending a long time
building a big thing, we have a small team spending a
short time building a small thing.

But integrating regularly to see the whole.

When Scrum?

High uncertainty

Complex projects

High interaction between modules

 Why choose Scrum vs Waterfall for Software Projects?

WAT E R FA L L SCRUM

Success is defined by achieving the planned scope. Success is defined by responsiveness to customer
requests
Why choose Scrum vs Waterfall for Software Projects?

WAT E R FA L L SCRUM

Requirements are well-understood and will not Requirements change frequently, even from month to
change month
Why choose Scrum vs Waterfall for Software Projects?

WAT E R FA L L SCRUM

All steps are known and can be estimated with All steps are not known in advance, and estimates are
reasonable accuracy not expected to be reliable
Why choose Scrum vs Waterfall for Software Projects?

WAT E R FA L L SCRUM

Whole Process is essential M.V.P* is essential

 Why choose Scrum vs Waterfall for Software Projects?

WAT E R FA L L SCRUM

Some steps may involve long lead times, or lots of Certain lead times* and identified resources
specialized resources
* 2 weeks of sprints in HUGO BOSS IZMIR
?
M.V.P
Scrum Process
 ROLES
Scrum Process

• Orders the work according to highest value

• Responsible for sprint planning
• Responsible for the value and the content of the
outputs
• Accepts or rejects the work completed by the team
 ROLES
Scrum Process

• Removes obstacles that keep the development

team from working at their highest capacity.
 ROLES
Scrum Process

• Self organized team, with the right competencies,

which pulls work from the backlog and completes
it
Scrum Process ARTEFACTS

• Is an ordered list of work to be put into a sprint

• Work that is added to the backlog should
preferably be in the form of user stories by the
product owner
• Stories are short, simple descriptions of a feature
told from the perspective of the person who
desires the new capability
Scrum Process CERAMONIES

• Where the team commits to a certain amount of

stories
Scrum Process CERAMONIES

• Every morning where the team answers the

questions:
• «What did I do yesterday?
• What am i planning to do today and are
there any impediments for that work?"
Scrum Process CERAMONIES

• The Demo where the work performed during the

sprint is demonstrated to stakeholders and the
PO signs off either accepting the work done,
rejecting it and giving feedback to improve in
another sprint
 USE CASE

BUILDING A NEW SEWING

LINE IN THE PLANT
EPIC : BUILDING A NEW SEWING LINE IN THE PLANT

FEATURES : • Machine Inventory

• Line Balancing
• Production Planning
• Layout Planning

User Stories & Backlogs **next slides

User Stories and Backlogs for Feature 1 : Machine Inventory
User Stories and Backlogs for Feature 2 : Line Balancing
User Stories and Backlogs for Feature 3 : Production Planning
User Stories and Backlogs for Feature 4 : Layout Planning