Sprint Demo

Purpose:

A session that closes a sprint in which completed functionality is reviewed with the Product Owner. Very often such review is called Sprint Demo because it is suggested to provide that information in form of a live demonstration showing completed functionality.

Objective:

Analyze requirements to ensure they are necessary and sufficient .

Description:

At the end of each Sprint, the full Scrum Team comes together to inspect the increment produced. The meeting is intended to elicit high-quality feedback. It is neither a pitch in which the Team attempt to dazzle a critical Product Owner, nor a party at which everyone congratulates themselves on what a great job they did.

The Scrum Team needs to demonstrate the work that has been produced and the Product Owner needs to identify what has been ‘done’ or ‘not-done’, give feedback (along with that of any other stakeholders) and consider the remaining Product Backlog. The feedback and discussion that follows will form much of the input into the next Sprint Planning Meeting. There can be significant changes of direction or new ideas generated from these meetings which may have a considerable impact on the rest of the Product Backlog.

RASIC:

 

Inputs:

<?>

Outputs:

<?>

Controls:

<?>

Task Instructions:

Initiate Request for Sprint Review

    1. Using the Sprint User Stories, [the Scrum Master] is responsible for ensuring that the Sprint stories meet the specified requirements.
    2. Using the Relevant Sprint User Stories Specific Checklist, [the Scrum Master and/or the Author] is responsible for using the relevant Sprint User Stories specific checklist to refer for completeness of the Sprint User Stories.
    3. Using the Sprint User Stories, [the Scrum Master] is responsible for identifying the supporting documents required for the review of the Sprint User Stories.
    4. Using the Review Package Template, [the Scrum Master] is responsible for preparing the Review Package.
    5. Using the Review Package, [the Scrum Master] is responsible for sending the Review Package to the Moderator and Project Manager.

Check Sprint Work Product Readiness

    1. Using the Sprint User Stories and Sprint User Stories supporting Documents, [the Scrum Master] is responsible for verifying the review readiness of the documents. Schedule Sprint Review Meeting
    2. Using the Sprint Review Meeting within the Sprint Review Invitation, [the Scrum Master] is responsible for completing the document.
    3. Using the Sprint Review Meeting, [the Scrum Master] is responsible for scheduling a Sprint Review meeting.

Prepare for Sprint Review Meeting

    1. Using the Meeting Documents within the Sprint Review Meeting, the is responsible for reviewing the work products and work product supporting documents.

Conduct Sprint Review Meeting

    1.  Using the Sprint Review Meeting, [the Scrum Master] is responsible for presenting the review package.
    2. Using the Sprint Review Meeting, [the Scrum Master] is responsible for updating the Action Items section.
    3. Using the Consolidated Review Log within the Sprint Review Invitation, [the Scrum Master] is responsible for documenting the identified modifications.

Sprint Review Follow Up

    1. Using the Sprint Review Meeting and Consolidated Review Log, [the Scrum Master] is responsible for sending the Meeting Minutes to all invited reviewers and [the Project Manager].
    2. Using the Consolidated Review Log, [the Scrum Master] is responsible for following up with the Reviewers for clarification and confirms reviewers concern, comments, or questions.
    3. Using the Sprint Review Summary Report within the Sprint Review Invitation, [the Scrum Master] is responsible for updating the content.
    4. Using the Sprint Review Meeting, [the Scrum Master] is responsible for scheduling an additional review.

Fix Modifications from Sprint Review

    1. Using the Sprint Review Summary Report, [the Scrum Master], with support from the Scrum Team is responsible for tracking the effort spent to resolve identified modifications.
    2. Using the Consolidated Review Log, [the Scrum Master], with support from the Scrum Team is responsible for consulting with [the Project Manager] to get agreement on which modifications to be updated and which need to be classified as out of scope.
    3. Using the Consolidated Review Log, [the Scrum Master], with support from the Scrum Team is responsible for fixing the identified modifications and ensures they do not introduce new or unintended modifications.
    4. Using the Project Document Control, [the Scrum Master], with support from the Scrum Team is responsible for ensuring that the work product is revised per the Project Document Control.
    5. Using the Consolidated Review Log, [the Scrum Master], with support from the Scrum Team is responsible for verifying closure of the review modifications

Document and Communicate Sprint Review Results

    1. Using the Sprint Review Plan within the Product Quality Plan, [the Work Product Owner] is responsible for ensuring that the review conducted meets the defined exit criteria for the worked product.
    2. Using the Sprint Review Summary Report, [the Work Product Owner] is responsible for completing the document and sending it to [the Project Manager].
    3. Using the Review Plan within the Product Quality Plan, [the Project Manager] approves that Review conducted meets the defined exit criteria for the worked.
    4. Using the , , Sprint Review Summary Report and Project Document Control, [the Work Product Owner] is responsible for checking in the documents into Configuration Management Library.