Remember to describe which roles are typically responsible for deciding which stories define the scope of a minimally viable product. Several members of a scrum team often offer technical, usability, and feedback mechanism considerations that should be considered when determining MVP scope.

"A minimally viable product, or MVP, represents the product features that need to be completed for a product to launch initially. The initial release is usually developed for a small set of users who provide feedback that can be incorporated into future iterations. Product owners collaborate with the business and development team to determine the right mix of user stories to be included in the MVP. They also partner with the business to determine which users will be included in the initial release and how they will provide feedback.

As a technical program manager, I typically oversee the brainstorming processes involved in the selection of the scope for an MVP. I ensure the appropriate standards are followed and that the feature selection aligns with the work for other teams or products I have responsibility for. I also ensure the process is collaborative and incorporates feedback from the business and the development teams in addition to product owners."