Scribd
Upload
42 views31 pages

Framework Scrum: Dr. Marco Toranzo Septiembre - 2020

Framework Scrum outlines the key aspects of the Scrum framework for agile project management. It describes Scrum as an iterative, lightweight and flexible process. The key Scrum artifacts are the Product Backlog, Sprint Backlog and Product Increment. Scrum uses cross-functional Scrum roles of Product Owner, Scrum Master and Development Team. Core Scrum events are the Sprint Planning meeting, Daily Scrum meeting, Sprint Review and Sprint Retrospective.

Uploaded by

Daniel López
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
42 views31 pages

Framework Scrum: Dr. Marco Toranzo Septiembre - 2020

Framework Scrum outlines the key aspects of the Scrum framework for agile project management. It describes Scrum as an iterative, lightweight and flexible process. The key Scrum artifacts are the Product Backlog, Sprint Backlog and Product Increment. Scrum uses cross-functional Scrum roles of Product Owner, Scrum Master and Development Team. Core Scrum events are the Sprint Planning meeting, Daily Scrum meeting, Sprint Review and Sprint Retrospective.

Uploaded by

Daniel López
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 31

Framework Scrum

Dr. Marco Toranzo


Septiembre - 2020
Agenda
 What is Scrum?
 Scrum roles
 Scrum artifact
 Scrum meeting
What is Scrum?
What is Scrum ?
(project based work)
 What is Scrum?
 Characteristics
 Iterative (many pieces) Transparent (nothing hidden)
 Lightweight yet robust Flexible and adaptable
 Simple to understand Transparent (nothing hidden)
Scrum artifacts (deliverables)
Scrum artifacts
 Product backlog
 Sprint backlog (assign to sprint)
 Product Increment.

Artefact
1) Product backlog
2) Sprint backlog (assign to sprint)
User stories
3) Product Increment
Product Backlog
Spring Backlog

Spring Backlog 1

Spring Backlog 1

Spring Backlog 1
Product Increment
 Development Team delivers a “done” Product
Increment at the end of every iteration.
 To create something potentially shippable is
difficult if some skills are missing in the team—
for example testers
Scrum Roles
Scrum Roles

 Product Owner

 Scrum masters.

 Team (authority on how what is done)

Team specialist. Subject matter experts are call when


is necessary-
Business owner ($$ i need ..)
Product Owner
 Most important position/person scrum project
 Understand What is the business want?
 Owns the product vision. Vision visible and
understood by the team. He agrees to change the
vision.
 Identifies the work for the team. Creates the user
stories. Document with What is required?
Product Owner
 Approves each Sprint. What
is in the Sprint ?and review
and approves the work in the Spring
Backlog 1

sprint
 Managers the Backlog.
Spring

Prioritizes stories Backlog 1

 Must be avaliable 3-4 hrs


every day Spring
Backlog 1
Scrum masters (SM)
 Main job – remove roadblocs.
 Ensure Scrum principles are applied.
 Making sure the Scrum process is understood and
adhered to
 Making problems transparent and making sure
they are being solved
 Focusing project participants on the project goals
 Not full-time position (sometimes)
Profile Scrum masters
 SM does not have any technical or domain work
to do. SM needs soft skills:
› Communication skills › Moderation/facilitation skills
› Conflict resolution skills › Motivational skills
› Negotiation skills/diplomacy › Discipline
› Openness › Reflection skills (for herself
› Courage and others)
Development Team (DT)
 DT is responsible for transforming the product
requirements into a finished product.
 DT select the right amount of work for each
Sprint.
Scrum Meeting (Events)
Meeting
 Sprint Planning (SP)
 Daily Scrum (15 minutes)-
 Scrum Review. This present results.
 Scrum Retrospective.
Sprint Planning
 Sprint Planning (SP).
 SP is the first thing that happens in the cycle and is
the official start of a Sprint.
 The goal is to reach agreement between Product
Owner and Development Team what is wanted in the
next Sprint.
 The Development Team to plan this next Sprint
 The final outcome of this meeting is the Sprint
Backlog.
Daily Scrum
 Daily Scrum (15 minutes)-
 What did we do?
 What are going to do?
 Issues/problems?
Scrum Review
 Product Owner inspects the outcome of Product
Backlog Items as soon as they are completed
during the Sprint.
 The Sprint Review is open for anybody who is
interested in the Sprint outcome.
 Lengthy presentations are forbidden.
 Also, the primary goal is not to formally accept
the outcome of the Sprint.
Sprint Retrospective (SR)
 SR is the official end of a Sprint.
 Only the Scrum Team is present in this meeting,
no guests are allowed.
 the process is inspected and measures to improve
it are identified.
 It just makes problems transparent and allows the
organization to solve them.
Burn down
Burn down

You might also like