One-Click Sprint Planning is one of Rapids’ most powerful features, allowing you to instantly generate an optimized, mathematically sound sprint schedule that respects team capacity, ticket estimates, and complex blocking dependencies.
Note that this feature depends on issues having actual estimates, either in Days or Story Points. A backlog filled with unestimated stories renders the allocation unrealistic. While it does support Kanban projects, it’s a feature targetting Scrum projects.
How it Works
Rapids combines your ticket estimates with your team’s historical velocity to structure an optimal plan:
- Capacity Allocation: You input your team’s sprint capacity (e.g., in Story Points or Man-Days).
- Dependency Sequencing: The engine analyzes the interactive dependency graph and CPM calculations to identify which issues must be completed first.
- Optimized Packing: Rapids uses an advanced scheduling algorithm to automatically distribute issues across upcoming sprints. It ensures that no sprint exceeds capacity and that no issue is scheduled before its blockers are resolved.
Interactive Planning Table
Once the plan is generated, Rapids presents an interactive draft plan view:
- Clean Interface: Dependencies between issues are hidden from the view by default in this mode, only displayed on hover, or in case an issue or arrow is selected.
- Change Suggestions: Composed by a blue dashed placeholder box marking the current issue position and a blue arrow pointing to the issue in its proposed position, both being selectable.
- Dismissing Suggestions: By selecting either the arrow part or the placeholder of a move suggestion and hitting “delete” you are able to dismiss that suggestion. Dismissing suggestions won’t take you away from the draft plan mode, still allowing the remaining suggestions to be commited.
- Commit to Jira: Once you are satisfied with the generated plan, click Commit. Rapids will automatically update the “Sprint” field of all modified issues in Jira in a single batch operation, saving hours of manual admin work.
- Safe Discards: If you are not confident with the plan or are just interested in the plan for simulation purposes without taking immediate action, feel free to hit Discard. Generating a draft plan is a no-op.
- Feature Compatibility: Be mindful other features that represent write operations are still available in this mode, such as drag-and-dropping issues and link creation/exclusion. The graph will instantly recalculate dependencies to highlight any new scheduling conflicts, but the draft plan will be discarded, since the new configuration requires a new planning.