Forums

By posting to our forums you are agreeing to the Forum terms of use.
Spring Review Approval Document
Last Post 04 Nov 2013 11:44 AM by Ian Mitchell. 3 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages Not Resolved
kinu554
New Member
New Member
Posts:1
kinu554

--
01 Nov 2013 02:59 PM
    Hello All.
    I am new to the forum, so my apologies up front for not doing research.
    I am desperately looking for a template/sample document which is used during a Sprint Review.
    The document should talk about the user stories covered in the Sprint review, any user stories that were not completed (if any) and then a sign off from the client about approval.
    I am not able to find anything like this. Just hoping that someone can provide some guidance. My email is jskaran@msn.com. Please contact me if possible.
    FredrikWendt
    New Member
    New Member
    Posts:2
    FredrikWendt

    --
    04 Nov 2013 02:35 AM
    Wow. Why would you want this? Scrum does NOT require such a document, and
    If you do some digging into xUnifiedProcess, I'm sure you'll find the document you're looking for.
    Joshua Partogi
    New Member
    New Member
    Posts:98
    Joshua Partogi

    --
    04 Nov 2013 07:11 AM
    Like Fredrik said. Scrum does not require this. Ask your customer why they require it. This is an opportunity for you to coach your customer about value driven development.
    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:571
    Ian Mitchell

    --
    04 Nov 2013 11:44 AM
    If the Development Team is a third party contractor, and incremental funding is in effect, it is plausible that some type of sign-off will be needed in order to release further funds. However, this should *not* be on the basis of user stories completed. It should be on the basis of the client having received an actual working increment.

    If this template is just a sprint summary, one that captures metrics and preserves findings for the team's own reference, then that's a different matter. In that case it hardly matters what the "template" is...just go ahead and put together your own. Nobody needs to sign that off.

    If the template is intended to convey metrics to parties *outside* of the team, then that is a different matter again. You just need a dashboard report...or better still, a chart on an information radiator. Again, nobody needs to sign that off.
    You are not authorized to post a reply.


    Feedback