scrum-master

To plan a sprint, you provide backlog items and team capacity, and the Skill generates ready-to-use sprint iterations and user stories. It enforces the Five Critical Standards for Stories and Definition of Done criteria to ensure backlog health for standard Scrum ceremonies.

Velocity tracking measures the work a team completes during a sprint. This Skill generates velocity reports and burndown insights to help size the backlog, determine team capacity, and plan accurate sprint goals for future iterations.

Yes, sprint planning requires structured input such as existing backlog items and defined team capacity. The Skill uses these inputs to draft user stories, establish sprint goals, and facilitate backlog refinement for the upcoming iteration.

Yes, you can use this to monitor sprint status and keep the backlog healthy. It facilitates backlog refinement by sizing items, tracking dependencies, and ensuring user stories meet the Definition of Done before the next sprint.

The best way to track sprint burndown and team capacity is by using velocity reports generated from completed sprint data. This Skill calculates velocity and produces burndown insights to monitor progress against the planned sprint goal.

User story creation requires acceptance criteria and dependencies to enforce the Five Critical Standards for Stories. This structured approach ensures backlog items are ready for sprint planning and meet the Definition of Done before development begins.