scrum-event-sprint-planning

To plan a sprint, select the highest-priority ready Product Backlog Item (PBI) and define a concrete, measurable sprint goal based on its benefits. This ensures alignment and focus before breaking the work down into subtasks for execution.

Subtask decomposition breaks the selected sprint work into small, deterministic, and testable subtasks. This TDD-style structure ensures each subtask follows a specific schema, making the development cycle measurable and ready for execution.

You need a single source of truth file named scrum.ts and a YAML-formatted subtasks schema. These prerequisites ensure the sprint goal and the decomposed subtasks align with the project's defined structure and format.

No, you cannot use this approach without a defined backlog. The sprint planning process requires a ready backlog to automatically select the top priority Product Backlog Item (PBI) and frame the sprint goal.

The best way to frame a sprint goal is to define a measurable objective derived directly from the chosen Product Backlog Item's benefits. This ensures the AI team maintains alignment and focus throughout the sprint execution.

Sprint planning requires a YAML-formatted subtasks schema to standardize the breakdown of sprint work into deterministic, testable units. This format enforces the TDD-style cycle structure and ensures the generated subtasks are ready for execution.