Forums

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Change the "scopo" of a backlog's item.
Last Post 11 Mar 2013 08:06 PM by Susanta Kar. 3 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
arturo anniballo
New Member
New Member
Posts:2
arturo anniballo

--
10 Mar 2013 07:36 AM
    Hello to everyone over there,

    what does it mean to change the "scopo" of a backlog's item?
    I can't understand the meaning of the technical term "scopo" that it sounds in this context different from the Italian meaning "obiettivo".
    I'm reading an article about how a P.O. can influence stories to put into a backlog sprint. He had a story 'A' very big and after the scrum team says that it's to stuff for the next sprint, the P.O. has changed its scope the story becomes very little. Why? Could you make this clear to me by an example?

    Thank you very much in advance for you help.
    Arturo
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1694
    Ian Mitchell

    --
    11 Mar 2013 01:26 AM
    Suppose a Product Owner has a story on the Product Backlog that he wants doing in the next Sprint. It is a big requirement for a complex report generator. In the Sprint Planning session, the team estimate the requirement (perhaps by using Planning Poker) and ask the PO questions.

    At the end of the Planning Session, the PO has negotiated a much smaller story with them. Instead of a full report generator, all the team have to commit to is a highlight report generator.

    What has happened is the team and the PO have explored the requirements and separated out the must-haves, should-haves, and could-haves. They have identified the Minimum Usable Subset (or Minimum Viable Product) which creates value, and agreed to deliver that by the end of the sprint. So the big requirement that was "in scope" for the sprint became smaller.

    "Scopo" isn't an English word, which is a shame because it sounds cool.
    arturo anniballo
    New Member
    New Member
    Posts:2
    arturo anniballo

    --
    11 Mar 2013 02:56 PM
    Hi Ian,
    you are right the word is SCOPE, one of the possible translations into Italian is SCOPO = GOAL . So this thing makes me crazy because I'm not able to give the right meaning into Italian.
    I was reading this article where I found this word.
    http://www.mountaingoatsoftware.com...seburndown
    when he says : ' As with an increase in scope, a decrease in scope comes off the bottom.'
    So what is the meaning of scope?
    I can't think of another synonymous that could let me to translate the word SCOPE (in this context) into italian.
    Please, could you help me? Thanks in advance.
    Susanta Kar
    New Member
    New Member
    Posts:20
    Susanta Kar

    --
    11 Mar 2013 08:06 PM
    Hello -

    I went thru the release turndown chart explanation. In this example, PO has added 40 story points during the project in sprint 4, hence its showing below 0 scale. However, in sprint 6, PO cut/removed story points and hence gone up towards 0 from -40. Scope is meaningful to the over all release/project - across the sprint its changing as when it was added it has different object give but as time passed by during/before sprint 6, story points were removed.

    Hope this helps.
    You are not authorized to post a reply.


    Feedback