Scribd Logo
Upload

Welcome to Scribd!

  • 55 views

    Scrum Planning - Poker Proposal

    Uploaded by

    carlospatinos
    This document proposes using Scrum Poker to estimate story points for an upcoming sprint. It explains how Scrum Poker works, giving an example of estimating installing software on a laptop. Key aspects of Scrum Poker outlined are assigning numeric values to stories individually and revealing them simultaneously, explaining outlier high and low values, and discussing until reaching agreement on a consensus value. The purpose is to get different perspectives, decrease bias, and have a better shared understanding of appropriate story point values.

    Copyright:

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

    Scrum Planning - Poker Proposal

    Uploaded by

    carlospatinos
    55 views18 pages
    This document proposes using Scrum Poker to estimate story points for an upcoming sprint. It explains how Scrum Poker works, giving an example of estimating installing software on a laptop. Key aspects of Scrum Poker outlined are assigning numeric values to stories individually and revealing them simultaneously, explaining outlier high and low values, and discussing until reaching agreement on a consensus value. The purpose is to get different perspectives, decrease bias, and have a better shared understanding of appropriate story point values.

    Original Description:

    Just whal all know but sometimes we forget

    Copyright

    © © All Rights Reserved

    Available Formats

    ODP, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document proposes using Scrum Poker to estimate story points for an upcoming sprint. It explains how Scrum Poker works, giving an example of estimating installing software on a laptop. Key aspects of Scrum Poker outlined are assigning numeric values to stories individually and revealing them simultaneously, explaining outlier high and low values, and discussing until reaching agreement on a consensus value. The purpose is to get different perspectives, decrease bias, and have a better shared understanding of appropriate story point values.

    Copyright:

    © All Rights Reserved
    Download as ODP, PDF, TXT or read online from Scribd
    Download as odp, pdf, or txt
    55 views18 pages

    Scrum Planning - Poker Proposal

    Uploaded by

    carlospatinos
    This document proposes using Scrum Poker to estimate story points for an upcoming sprint. It explains how Scrum Poker works, giving an example of estimating installing software on a laptop. Key aspects of Scrum Poker outlined are assigning numeric values to stories individually and revealing them simultaneously, explaining outlier high and low values, and discussing until reaching agreement on a consensus value. The purpose is to get different perspectives, decrease bias, and have a better shared understanding of appropriate story point values.

    Copyright:

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

    Proposal for Estimation

    Agenda:
    1- Present estimation technique (Scrum Poker)
    2- Example explained
    - Practical Exercise

    !uestions

    "hat are #alid #alues


    for stor$ points%

    &o' man$ stor$


    points per sprint%

    "h$ do $ou think is


    important%

    Purpose

    (et different
    perspecti#es for
    estimations

    All of us get more


    idea of 'h$ specific
    #alue for stor$)))

    *ecrease +eing
    influenced as this is
    human nature)

    1- Scrum Proposal

    ,se scrum poker to estimate)


    *o'nload Android and -phone

    .ules

    .emem+er this is /ust estimation


    (ne#er expect full accurac$)

    All *e# team must participate in


    gi#ing #alues

    0alues allo'ed (11212 infinite)

    All re#eals his ans'er the same time

    &ighest and lo'est #alues must


    explain and then *e# team must
    agree 'hich is the most accurate)

    -nfinite tasks must +e splitter in


    shorter stories

    -dentif$ the a#erage points 'e do per


    sprint

    2- Example) -nstall E34 on $our
    3aptop

    -n this example #alues are small1 medium1


    large and extra large

    P5 explains 'hat is needed

    6he first idea)))



    1- Ask the team a+out the si7e of a
    stor$

    6he team thinks a+out all the implications of


    the tasks independentl$

    Each person in the *e# team
    choses one #alue

    And all of them hide the ans'er until all are


    read$)

    All present the #alue at the same
    time)

    So minimal influence is done and 'e get more


    ideas on the stor$

    &ighest and 3o'est Explain

    6his 'a$ 'e get more ideas and estimation


    'ill get different perspecti#es

    &ighest and 3o'est Explain

    6hat 'a$ 'e can ha#e a +etter idea as a team



    P5s Explain

    8larifications ma$ +e needed and then this


    can +e more precise

    All 'e get a +etter idea

    And in this case all #ote as infinite))) so 'e


    must split this epic into smaller stories

    Practical Exercise

    9ix technical de+t on mediation core



    Practice

    ,sing the app :)

    .egister 0alues here)))) and explain)))) P5


    clarifies :) all agree on some #alue)))

    *etails

    Scrum 9unn$ 0ideos

    Part 1

    Part 2

    Part

    9eed+ack

    "hat do $ou think%

    Some topics for the future)

    ;erging 'ith e(it

    Eclipse and <ira

    You might also like