Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Overview of the Scrum Framework

High level overview of Scrum

Jean-Louis Marechaux

on 18 January 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Overview of the Scrum Framework

Scrum Framework Overview
Sprint Planning
Sprint Review
Sprint Retrospective
Daily Scrum
Product Backlog
Sprint Backlog
Scrum Team
Product Owner (1)
Scrum Master (1)
Development Team members (3 to 9)
Scrum relies on:

Product Owner
Scrum Master
The Development Team
Scrum Team
delivers products iteratively and incrementally, maximizing opportunities for feedback
Defines the product features
Maximizes the value of the product and the work of the Development Team
Manages the Product Backlog

Responsible for ensuring Scrum is understood and enacted
Is a servant-leader for the Scrum Team
Is sometime called "Agile Coach"
Works to deliver a product increment
Cross-functional and self-organized
3 to 9 members
.scrum.org (Scrum Guide 2013)
The work done is visible to all the stakeholders

Everyone share a common understanding of:
to achieve
definition of "Done"
Scrum users continuously review artifacts and progress toward goals
Adjustments to the process or the artifacts are made when necessary
Product Backlog
Ordered list of features (epics and stories)

Living artifact. The Product backlog is refined over time (details, estimates, order)

Higher ordered items usually clearer than lower order ones

The Product Owner is responsible for its content
Sprint planning topic 1:
What can be done this Sprint?
Sprint planning topic 2:
How will the chosen work get done?
Daily Scrum
The Development Team assesses progress toward the
Sprint Goal
What did I do yesterday?
What will I do today?
Do I see any impediment?
Sprint Review
Sprint Retrospective
The Product Owner explains the objectives of the sprint, and the related Product Backlog items

The Development Team forecasts the number of items it can accomplish in upcoming Sprint

The Scrum Team defines a
Sprint Goal
The Development Team creates the
Sprint Backlog
Items selected from the Product Backlog
A plan to complete the selected items (
definition of "Done"

The work planned is decomposed into tasks

The Development Team can explain how to:
Accomplish the Sprint Goal
Create the next product increment
Sprint Planning
Collaborative planning (the entire Scrum Team)

Work to be performed in the Sprint

Timed-boxed: Maximum of 8 hours for a one month Sprint
No changes are made that would endanger the Sprint Goal
Quality goals do not decrease
Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned
Time-box event of one month or less
Focus on development work to create a product increment
Includes a
Sprint Planning
Daily Scrums
, a
Sprint Review
and a
Sprint Retrospective
A 15-minute time-boxed for the
Development Team
Inspect the work since the last Daily Scrum
Forecast the work for the next 24 hours (
Not a status meeting
The Scrum Team and key stakeholders are attending

Inspect the increment and adapt the Sprint Backlog

Time-boxed event: 4 hours for a one-month Sprint

The Development Team demonstrates and explains the increment
The Scrum Team is attending

Time-boxed event: 3 hours for a one-month Sprint

Inspect how the last Sprint went with regards to people, relationships, process, and tools

Refine the
definition of "Done"

Identify improvements for the next Sprint
All Product Backlog items completed during a Sprint

Must comply with the Scrum Team's
definition of "Done"

Potentially releasable product increment
The Product Owner decides if it should be released

Team, Events, Artifacts
--> Optimize value and control risk
Full transcript