Product Owner Role in Sprint Review(Sprint Demo)

by Avienaash Shiralige

Sprint Review meeting facilitates developing a successful product. Hence it is a very good avenue for scrum team to directly interact with stakeholder to get their perspective. Product Owner(PO) who is responsible for overall product should facilitate having all the stakeholders like Marketing, Sales, Senior management, End Users to the demo.

In my last post where-in I discussed about Product Owner responsibility of Accepting or Rejecting user stories as and when it gets DONE. Only accepted stories will go to Sprint Demo. Product Owner kicks-off Sprint review meeting where-in he compares product increment(accepted stories) with current sprint goal to the stakeholders.

For PO to be confident on this, he should get involved early in the sprint and should run few tests himself on new features developed. He will accept stories which are DONE as per “definition of done” defined by Scrum team and only if user story satisfies all the acceptance criteria.

PO should never accept any partially done stories. They earn zero points to the team and are put back into the Product Backlog. Carrying forward partially done stories give a false impression of done and will distort Release burn-down chart.

scrum_release_burndown

In fact, Release burndown chart shown above is an ideal chart to present to all the stakeholders. PO and team as a whole do status check as per release calendar and evaluate any risks they foresee. Once demo is done, PO along with team take feedback from different stakeholders. Product Owner should always give very honest and constructive feedback to the team with due respect to all the scrum team members.

About Avienaash Shiralige


Avienaash Shiralige is an Agile Coach, Trainer, Business Optimisation and Agile Transformation Consultant @ AgileBuddha. He has been on senior leadership positions in various companies and comes with very rich 17+ years of experience in product and service companies. He has consulted companies in India, US, Europe and Australia on Agile/Scrum/Lean/Kanban and successfully set-up various distributed agile teams across timezones. He can be reached at avienaash@gmail.com.

{ 4 comments… read them below or add one }

Vernetta Cabriales June 18, 2012 at 12:40 am

There is noticeably a bundle to know about this. I consider you made various good points in features also.

Reply

Avienaash Shiralige June 20, 2012 at 7:07 am

Thanks Vernetta for coming here.

Reply

Priyanka October 4, 2012 at 8:11 pm

When we prepare a burndown chart for a sprint, should we add the story points of the user stories which are carry forwarded to this sprint as well? e.g. Carry forwarded story points are 10 and current story points are total 30. So should I put the burndown against 40 story points or 30 story points?

Reply

Avienaash Shiralige October 8, 2012 at 10:17 am

Priyanka,

I use hour burndown for sprints. In my experience using hour burndown for sprints facilitates self organization and I don’t use points at sprint level. Story point estimation is done at release level and during backlog grooming session. Hence I use release burndown chart using story points.

Don’t carry forward points from sprint to next sprint. If any story is not completed as per acceptance criteria and definition of done, then you will put it back to product backlog. Let PO prioritize it.

You hour burndown chart for current sprint would be on what you have committed in this sprint only.

Thanks,

Avie

Reply

Leave a Comment

Previous post:

Next post: