Scribd Logo
Upload

Welcome to Scribd!

  • 23 views

    Sprint Team: Scrum Checklist

    Uploaded by

    Raluca Andreea Turcu
    The document describes the key elements of a Scrum process, including roles like the Product Owner, Scrum Master, and team. The team works collaboratively in sprints to deliver working software, holding daily standups, sprint planning meetings, demonstrations, and retrospectives. The Product Owner prioritizes work in the backlog and ensures the team understands requirements.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Sprint Team: Scrum Checklist

    Uploaded by

    Raluca Andreea Turcu
    23 views1 page
    The document describes the key elements of a Scrum process, including roles like the Product Owner, Scrum Master, and team. The team works collaboratively in sprints to deliver working software, holding daily standups, sprint planning meetings, demonstrations, and retrospectives. The Product Owner prioritizes work in the backlog and ensures the team understands requirements.

    Original Description:

    scrum

    Original Title

    Scrum Checklist Prio1

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document describes the key elements of a Scrum process, including roles like the Product Owner, Scrum Master, and team. The team works collaboratively in sprints to deliver working software, holding daily standups, sprint planning meetings, demonstrations, and retrospectives. The Product Owner prioritizes work in the backlog and ensures the team understands requirements.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    23 views1 page

    Sprint Team: Scrum Checklist

    Uploaded by

    Raluca Andreea Turcu
    The document describes the key elements of a Scrum process, including roles like the Product Owner, Scrum Master, and team. The team works collaboratively in sprints to deliver working software, holding daily standups, sprint planning meetings, demonstrations, and retrospectives. The Product Owner prioritizes work in the backlog and ensures the team understands requirements.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 1

    Team sits together

    Team members collaborate to


    bring stories all the way to
    Done.

    Team delivers something after each sprint

    Team

    Sprint

    Team members not locked into


    specific roles

    Team follows PO's priorities


    Team usually delivers what
    they committed to

    Same time, same place every day

    Team has a SM
    SM sits with the team
    SM focuses on removing
    impediments

    Starts and ends on time

    Daily Scrum

    Scrum master (SM)

    All team members present

    Demo is done after each sprint


    Team has one PO

    PO understands the product


    enough to prioritize well

    Demo shows working code

    Sprint demo

    PO has the power to prioritize


    what his team does

    Only stories that are Done are


    demonstrated

    Product Owner (PO)

    Retrospective takes place

    PO has at least 1 dedicated team

    All team members + PO


    participate

    PO owns PBL
    PBL is visible
    PBL is updated before sprint planning

    Results in concrete
    improvement suggestions

    Retrospective

    Some improvement
    suggestions actually get
    implemented

    Product Backlog (PBL)

    PO understands all stories

    Scrum checklist

    Team has impediment backlog

    Each story has a DoD (or


    inherits a default DoD)
    Team respects DoD

    Definition of Done (DoD)

    Impediment backlog

    PO can get estimates from the team

    Impediment backlog is
    up-to-date

    Velocity is written down after each sprint

    PO is available when team is estimating

    Velocity

    Only the team writes the estimates


    Everyone on the team
    participates in estimating

    Impediment backlog is visible

    Estimation

    Velocity only includes stories


    that are done according to DoD
    Velocity is used for release planning

    Top priority stories are small


    enough that several can fit in a
    sprint

    Team has a burndown chart


    Burndown chart highly visible

    Burndown chart

    PO participates

    Burndown chart updated every day


    Team takes action when
    burndown is too high/low

    All team members participate


    Results in a sprint plan
    All team members think the
    plan is realistic, and commit to
    it.
    PO is satisfied with the priorities
    All stories in the sprint plan
    have an estimate.

    Scrum checklist.mmap - 2008-01-14 - Henrik Kniberg

    Team has a sprint backlog

    Sprint planning meeting

    SBL is highly visible

    Sprint backlog (SBL)

    SBL updated every day


    Task estimates updated every day

    You might also like