A critical part of regular sprint planning is prioritizing new feature requests. We ask questions, challenge assumptions, and encourage prioritization based on factors such as value to the business, user needs, cost of implementation, and timeline/resource constraints.
We go through this prioritization exercise a LOT because building a great product is an ongoing, dynamic experience, and we’re not afraid of changing requirements or new ideas.
We know that with a great framework for prioritization, we’ll ultimately build a successful product, in the most efficient way.