Just want to share how our Sprint Review went.
Week 4 of the Sprint - I brought up during the daily scrum that the
developers who committed to deliver features should be ready to demo
their stuff during the Sprint Review. I provided a box where all the
builds and codes will be demonstrated. Gave the team 2 hours to
prepare the box before the Sprint Review. Every developer who had
something to deliver did the demo to the entire team. I, the
ScrumMaster, simply created a documented that listed what we were
delivering (with the name of the responsible person) and circulated
it to the team. We have features that were Server code complete (UI
not ready) and still were demonstrable. The discussion flowed
between the product owner and the developers. After the meeting,
team members were responsible for adjusting their tasks on anything
that the product owner requested.
Cheers - Lou
--- In firstname.lastname@example.org
, "Victor Szalvay"
> One of the main tenets of Scrum is that working software is
> demonstrated to the product owner during the sprint review. The
> primary measure of project/release progress is the tested,
> working software. This is in the spirit of high visibility; the
> customer knows exactly how far the team got with the product. In
> spirit, avoid powerpoint or any other indirect demonstration
> This requirement also fosters the agile principle of highly
> development. It forces the team to actually produce tested (and
> integrated) code from sprint one moving forward rather than simply
> non-software artifacts/documents.
> I recently sat in on a "sprint review" where a "project manager" sat
> in front of the team and the product owner with a powerpoint
> presentation. The PM discussed the vision of the project, made
> abstract references to the goals of the current sprint, and then
> out stated that the goals were indeed met. This without a demo or
> product owner's indication as to whether the goals were met. Why
> weren't members of the team speaking? Bottom line: I walked out
> no idea what this team actually did during this sprint or where the
> product currently stood.
> I've heard arguments that sometimes working software "cannot be
> demonstrated" because it has no UI component (e.g., a service). But
> in IMHO it is still better to (build and) demonstrate interaction
> a sample client in such a circumstance rather than show a powerpoint
> or nothing at all. My advice is to get creative and come up with a
> way to showcase the product even those circumstances. It makes me
> nervous when teams are so eager to throw in the towel on showcasing
> working software during sprint reviews.
> To answer the original question about agenda for sprint review:
> K.I.S.S.! There is no need for a complex agenda, simple put on an
> informal demonstration of the working software produced and contrast
> it to the team's committed goals and exit criterias.
> -- Victor Szalvay
> Danube Technologies, Inc.
> --- In email@example.com, "Allan Schwartz"
> > I don't know how typical this is, because we have only
> > been using Scrum for less than six months.
> > We have been using the Sprint Review just to inform
> > others in Development and also Product Support,
> > Product Marketing, and Sales exactly what our Scrum Team
> > had done in the past Sprint period.
> > For example, in our last Sprint Review, I presented about
> > 20 slides. First, an overview.
> > What we accomplished; what we didn't complete.
> > Then about one slide per feature (Backlog Task) delivered.
> > The Team Member talked about the feature, it was demo-ed,
> > if possible.
> > Then a short discussion on what was learned in this Sprint
> > period.
> > Then a preview of what features might be developed in the
> > next Sprint period. (a pre-Sprint Planning discussion).
> > In the past, certain Stakeholders such as members of Product
> > Marketing and Product Support had many questions and
> > comments. (Possibly, the Product Owner hadn't communicated
> > fully with them, and some of the features were surprises.)
> > -allan
> > --- In firstname.lastname@example.org, "Ramu"
> > >
> > > Hi All,
> > >
> > > I am new to this scrum methodology. could you help me in
> > > sprint review checklist.exactly what needs to be checked at the
> end of
> > > the sprint.
> > >
> > > Thanks
> > >
> > > ramu
> > >