Locked lesson.

Upgrade

About this lesson

The Sprint Demonstration is the formal meeting where the Scrum Team demonstrates to the Product Owner the performance of each deliverable that was created during the Sprint.

Quick reference

Step 5: Sprint Demonstration

The Sprint Demonstration is the formal meeting where the Scrum Team demonstrates to the Product Owner the performance of each deliverable that was created during the Sprint.

When to Use Revenues and Profits

The Sprint Demonstration is usually immediately after the completion of the last day of the Sprint. It is normally the following day.

Instructions

The Sprint Demonstration is the only external review of the project deliverables in the Agile/Scrum process. It is the meeting where the Product Owner determines whether the Scrum Team has completed each story in the Sprint Backlog.

  • This is a formal documented meeting. It often has meeting minutes and the results are filed in the project archives.
  • This is a meeting between the Product Owner and Scrum Team. The Product Owner will often invite senior managers, business team members, or other subject matter experts who provided input to the Stories to participate in the meeting. However, that is a decision for the Product Owner to make.
  • During the course of the meeting, the Scrum Team will demonstrate, and if appropriate, allow meeting attendees to test the results of the stories. The demonstration and test should be based upon the documented Demo Criteria on the Story Card. If during the demo, other criteria are identified, a new Story Card should be created by the Product Owner.
  • If some stories were only partially completed, the Scrum Team can demonstrate the portion that was completed and a new or modified Story Card can be created for the remaining work.
  • If a story was never started, the Scrum Team will provide any roadblocks or other impediments that may have contributed to why it was not started.
  • If you are taking the Scrum Master, Product Owner, or Agile Practitioner version of this course, there will be another session that will discuss how to plan and facilitate a Sprint Demo meeting.

 

Hints and Tips

  • It is normally a good idea for the Product Owner to invite key stakeholders to this meeting, especially if they have concerns about the progress of the project.
  • Take as long as you need on this meeting.  I have seen some done in 30 minutes and others take over 4 hours. Spend the time needed to fully validate that the deliverables are acceptable.
  • In the museum website upgrade project, I invited the museum director, museum staff, and the museum Board of Directors to review the Sprint Demo. About 25% attended, which was in line with what I expected.
  • We reviewed the first three stories:
    • Response web template was acceptable to all. We selected an iphone, ipad, and laptop to review the responsive resizing. We also reviewed using the four most common browsers.
    • The fifteen existing pages were all transferred. All of the text and pictures were there and they looked good in all three formats and with all browsers.
    • All of the contact buttons worked in all formats and browsers.
    • The Scrum Team identified that the donor button would only work with Paypal, (which was demonstrated) but would not work with the direct merchant service account. This issue would require further study and analysis and a Story Card was written for this feature for the next Sprint. The Scrum Team explained that they just ran out of time to resolve this before the end of the Sprint.
Login to download
  • 00:03 Hi, I'm Ray Sheen again.
  • 00:05 Well, the Sprint has just finished, so it's now time for
  • 00:08 step number five, the Sprint Demonstration.
  • 00:11 Or, as it's commonly called, the Sprint demo.
  • 00:14 This is the moment of truth for the Scrum Team.
  • 00:18 They must prove that what they have developed does what it is supposed to do.
  • 00:22 The Sprint demo is a formal documented meeting that normally
  • 00:25 occurs the day after the Sprint effort completes.
  • 00:28 By formal, I mean there usually minutes of the meeting, attendance lists, and
  • 00:32 the results get filed in the project archives.
  • 00:35 Officially, the meeting is between the Scrum Team and the Product Owner.
  • 00:38 The team reviews and demonstrates the results of every Story Card completed, and
  • 00:43 the Product Owner decides whether to accept the result or not.
  • 00:46 Most of the time, the Product Owner will invite some of the management or
  • 00:49 business team to attend also.
  • 00:51 However ,the acceptance decision is made by the Product Owner,
  • 00:54 not all the invited guests.
  • 00:57 The result of every story is demonstrated.
  • 00:59 Don't rush this meeting.
  • 01:00 Take the time to check out everything.
  • 01:03 If appropriate, the demonstration is conducted as a test by the Product Owner
  • 01:07 and or invited guests.
  • 01:09 In some cases, the demonstration is a presentation or an analysis.
  • 01:13 Whatever the form and format, the demonstration is done using
  • 01:16 the Demo Criteria from the Story Card as the standard.
  • 01:20 Many times, the Product Owner or
  • 01:21 invited guest may ask the result to do more than the Demo Criteria.
  • 01:25 If it can, great.
  • 01:27 If it cannot, and the Product Owner determines that he or she would like it
  • 01:30 to, the Product owner will create a new Story Card for a later Sprint.
  • 01:36 If the demonstration reveals that the results of the work by the Scrum Team
  • 01:39 does not meet the Demo Criteria, or that the Scrum Team identifies in a meeting
  • 01:44 that they did not finish a story, the Product Owner will determine if a new
  • 01:48 Story Card is required, or if the orignal Story Card should still be used.
  • 01:52 If the Scrum Team knows that a story is not complete, they should identify any
  • 01:56 roadblocks or other impediments that prevented them from completing the story.
  • 02:00 Again, the Product Owner can determine whether to rewrite the story or not.
  • 02:05 If you are taking this course as part of the Scrum Master Product Owner or
  • 02:08 Agile Practitioner version, there will be a later session that provides guidance
  • 02:13 on how to plan and facilitate a Sprint Demo meeting.
  • 02:15 Once again, it's time to review the roles, responsibilities, and deliverables.
  • 02:20 As you look at this table, you may think I overlooked something.
  • 02:24 This doesn't show the Scrum Team providing any deliverables.
  • 02:27 That is because in the table with the Sprint execution,
  • 02:31 I showed the Scrum Team completing and delivering the results of each story,
  • 02:35 in order to move that story to the done column.
  • 02:38 I didn't want to imply that they had to do the work again.
  • 02:41 You can see in the responsibilities portion of the table
  • 02:44 that they must demonstrate the result.
  • 02:46 But my point is that the result was actually completed in Sprint execution.
  • 02:51 The Scrum Master is in a facilitation role at this meeting.
  • 02:54 They keep track of which stories are accepted as done and which ones are not.
  • 02:59 They help the Product Owner plan the backlog for the next Sprint.
  • 03:03 The Product Owner is the person who makes the decisions in this meeting.
  • 03:06 They review the results and provide a thumbs up or a thumbs down for each story.
  • 03:12 Senior Management is often invited,
  • 03:13 and their input is used by the product owner to help make their decision.
  • 03:18 Well, let's look at our museum website upgrade project.
  • 03:21 The infrastructure story and the responsive web template were
  • 03:24 demonstrated with the review of the website pages.
  • 03:27 In this case, we did the review on an iPhone, an iPad, and a laptop.
  • 03:32 We also looked at everything using the four most popular Web browsers.
  • 03:36 The content on each of the 15 pages was compared to the old site.
  • 03:40 And we showed that all of the text and
  • 03:42 pictures are there, only now things were responsive.
  • 03:46 We also checked all of the links on all of the pages.
  • 03:49 Now, at this point, the Scrum Team could have said
  • 03:53 that they provided exactly what was on the old web pages.
  • 03:56 But fortunately, they went beyond this and
  • 03:58 they actually fixed a few of the broken that were on some of the old pages.
  • 04:03 We then checked all the contact buttons and the donor button.
  • 04:07 There was a problem with the donor button that the Scrum Team identified for us.
  • 04:11 The button worked great if you used PayPal, but
  • 04:13 it would not work with our merchant service account.
  • 04:15 Scrum team explained that this was the last part of the lowest priority task in
  • 04:19 the Sprint backlog.
  • 04:20 And they just ran out of time to get this working.
  • 04:23 The code from the old page would not work in the new template.
  • 04:27 And they did not have time to find or develop new code that would work.
  • 04:30 In this case, I wrote a new Story Card for
  • 04:33 just the feature to include on our next Sprint.
  • 04:36 The Sprint Demo is the culmination of a Sprint.
  • 04:41 This is the time for the team to show the Product Owner and
  • 04:44 key stakeholders what they have accomplished.

Lesson notes are only available for subscribers.

PMI, PMP, CAPM and PMBOK are registered marks of the Project Management Institute, Inc.

Gift this course