Scrum employs an iterative, incremental approach to optimize predictability and control risk. The primary objective of a Sprint (iteration) is to produce a potentially shippable product Increment. Having an Increment will allow the Scrum Team to know the right thing to do in the upcoming Sprint. Having a velocity is important but working software is the primary measure of progress.

Explanation
Explanation:
The Development Team may need to order the Product Backlog as they would know the most about technical limitations, risks, or dependencies between Product Backlog Items. As User Stories is a localized practice, Scrum does not govern it or dictate the practice. How the team describes the items is up to them as long as it has enough information to be transparent and understood.

The cost of developing, delivering, and sustaining products can impact how the flow of value is managed throughout the life of a product. Each Sprint is an opportunity to inspect the investment (financial, time, effort, etc.) against the returned value (customer satisfaction, revenue, etc.) of the work that has been delivered. The team can then decide on what it should do next to maximize the value of the investment.

The Scrum Master serves the Development Team by coaching it in self-organization and cross-functionality.