Scrum

To break epics into sprint-ready user stories, you decompose large features into estimable stories using clear acceptance criteria and a definition of done. Any stories larger than 8 points are decomposed further before sprint entry to ensure executable scope.

The best way to prioritize a product backlog is by applying value versus effort frameworks like RICE, MoSCoW, or WSJF. This approach orders work effectively to ensure highest-value items are groomed for upcoming sprints.

You forecast sprint capacity using velocity and burndown trends by tracking historical story point completion and analyzing burndown or burnup charts. This makes delivery predictability measurable and surfaces carryover constraints for upcoming sprints.

Running a sprint retrospective with specific and time-bound action items involves analyzing recent delivery trends and velocity to identify process bottlenecks. You then produce actionable, time-bound follow-up tasks to drive continuous improvement.

You should lock sprint scope immediately after sprint planning to avoid chaotic delivery. Locking the scope ensures the team focuses on committed work, while carryover constraints are surfaced to maintain predictable velocity.