A sprint is a feedback container
In Scrum, a sprint is a fixed-length period in which the team works toward a sprint goal and creates a usable increment. The official Scrum Guide defines the accountabilities, events and artifacts that make up Scrum.
Planning is not a promise to the future
A sprint plan should create a credible path toward the goal. It should not encourage teams to hide uncertainty simply to make a commitment look precise.
Incremental delivery
Delivering smaller slices makes feedback cheaper. If a customer dislikes a direction after six months, the cost of discovering that is high. If the customer sees a usable slice after two weeks, the team can adjust earlier.
Plan around an outcome, not a full calendar
Sprint planning is stronger when the team knows what it is trying to accomplish rather than simply filling capacity with unrelated tickets. A sprint goal creates a reason for the work to belong together.
Protect the Definition of Done
An item is not done until the agreed acceptance criteria pass, code is reviewed, required tests are complete, defects at the agreed level are resolved, and the increment is in a state that stakeholders can inspect.
Carryover is useful feedback. Repeated carryover can indicate oversized stories, unstable dependencies, unrealistic capacity assumptions or unclear requirements.
Create a sprint goal for improving checkout. Choose four stories that support it and write a practical Definition of Done for the team.