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.

Question? (Scrum_Guide, S. Retro Or S. Review)
Last Post 02 Feb 2014 03:38 AM by Ian Mitchell. 3 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Mehdi Hafezi
New Member
New Member
Posts:46
Mehdi Hafezi

--
02 Feb 2014 02:08 AM
    1)Introduction: in the current Scrum Guide (July 2013) in page 11,
    the elements are listed which are included in Sprint Review:
    "...
    3rd bullet point: The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;"
    ..."

    2) Question: Why should it be discussed during Sprint Review? Is the Sprint Retrospective not the better place to handle these topic?
    Ilia Pavlichenko
    New Member
    New Member
    Posts:71
    Ilia Pavlichenko

    --
    02 Feb 2014 02:24 AM
    During Retrospective we discuss people, their relationship, process etc.
    Focus of the Review Meeting is on Product and issues we observed while developing this product during the Sprint.
    Mehdi Hafezi
    New Member
    New Member
    Posts:46
    Mehdi Hafezi

    --
    02 Feb 2014 02:33 AM
    @Illya: You are right, thank you for your clarification.
    Mehdi
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1457
    Ian Mitchell

    --
    02 Feb 2014 03:38 AM
    Illya is spot on. The Review should be focused on the Product. The Retrospective should address the process and behavior of the Scrum Team and its interfaces. In their own distinct ways, both are opportunities to inspect and adapt the value stream.

    However, I can sympathise with Mehdi's concern. The problems that are identified in a Sprint Review are often human ones. The important thing is not to solutionize behavioral or process problems in the Review, but rather to identify facts. These are the facts that certain problems happened and that they were addressed in a certain way. Such objective findings can then be used to inform the Sprint Retrospective, and dysfunctions in process can be remedied.
    You are not authorized to post a reply.


    Feedback