Plan a sprint with AI
Shape a credible sprint goal, account for the team’s capacity and turn a retrospective into a small experiment the team can review.
Plan a sprint with AI when the backlog is longer than the available time and the team needs a reasoned commitment. The scrum-master skill guides an agent through planning, impediment follow-up, sprint review and retrospective work. It keeps facts from the board separate from estimates or recollections.
A task carried over from last sprint may still depend on the same missing approval. Bringing its points forward does not remove that dependency. Identify who can obtain the decision, when it is needed and what happens to the sprint goal if it arrives late. The next review can then examine what happened rather than just counting closed tickets.
What it does
- Define a sprint outcome that connects the chosen work.
- Compare the planned load with time and capacity actually available.
- Record a blocker with its impact, owner and follow-up date.
- Distinguish finished work from items merely started.
- Choose one retrospective experiment with a testable result.
Install and use
- Give an agent the authorised backlog, current team capacity and working definition of done. A separate tracker connection is needed only for approved updates there.
- Ask for one achievable goal and a short list of assumptions that might put it at risk.
- Review the plan with the team and verify the evidence again when the sprint closes.
FAQ
Source
Made by Hieu T. Luu. Original skill: scrum-master, published on GitHub under the MIT licence.
View on GitHub