As we know, a Sprint Retrospective is a meeting held at the end of an iteration to evaluate the Scrum Team's performance, what happened in the iteration and identify actions for improvement going forward. Suppose we are working on a minimum viable product (MVP) to be launched shortly. The product is not launched in the market and is awaiting customer feedback. So it is very essential to evaluate the Sprint items rigorously in a meeting. Basically, I want to conduct the best and most efficient retro meeting.

  • VTC as too broad. Take a look at this, though: martinfowler.com/articles/itsNotJustStandingUp.html
    – Sarov
    Commented Sep 5, 2018 at 13:14
  • 1
    The above links described about the daily stand up meeting. I would like to know the suitable method to conduct retrospective meeting for a MVP. Commented Sep 5, 2018 at 13:18
  • Oh, misread, sorry. Anyway, you should be able to just search for "Scrum Retrospective Tips". If you want help from PMSE, you'll probably need to narrow the scope of your Question.
    – Sarov
    Commented Sep 5, 2018 at 14:49

2 Answers 2


The described context does give much specifics for the retrospective. As you don't have customer feedback, the retrospective should probably focus on the team interworking. It can be any format from benlinders.com/exercises. If you give me more info, then I can pinpoint you to specific exercises that might be suitable.

  • Thanks for the information. Basically i am trying to understand the features implemented in each sprint is perfect and would like to prove with some data with the help of retrospective meeting. For example : We have implemented a new report "Performance report" to evaluate the portfolio return and performance of all the clients. So i would like to explain or prove to the external party with some date that the report satisfies the design, usability, and other technical factors. How this can be proved in the retrospective meeting ? Commented Sep 6, 2018 at 7:16
  • Thanks for the additional info. What you are trying to do makes a lot of sense, certainly within a Lean Startup approach when you're creating an MVP. But I don't think the retrospective would be the right meeting to do this, as the main purpose of the retro is to learn and improve as a team, not to improve the product (see benlinders.com/2013/…). Also the retrospective focus is internal, where your focus is (for very good reasons) externally on the product and business value.
    – BenLinders
    Commented Sep 7, 2018 at 8:08
  • @JithinAntony: What you describe here sounds more like a product demonstration to the external party. Commented Sep 7, 2018 at 14:12
  • It's more than/different from a product demo. The aim of the demo is to get feedback, but if I'm not mistaken then he wants to validate the MVP, closing the build-measure-learn loop, right?
    – BenLinders
    Commented Sep 7, 2018 at 18:14

MVP is to bring product to customer's table quicker to bring more understanding of what customer has conceptualized and to get the alignment of feels & thoughts against the product. In sprint retrospection, you can discuss what went good and what can be improved to bring more stories to the delivery.

Post customer feedback, one can fine tune definitions of 'what' needs to be delivered.

But, sprint retrospection can help in fine tuning 'how' part of delivery.

Not the answer you're looking for? Browse other questions tagged or ask your own question.