Description

The Sprint Instant Scheduling purpose is to take the backlog issues and set them automatically into the future sprints according to the team velocity and capability (Sprint future Velocity) in one click.
The use case: after the initial planning (Epic break down to issues) the program manager can automatically set the draft sprints plan
The app will assign issues from the backlog which have estimations set for them. There is an option to automatically set default values for non estimated issues in the backlog.
The app will set relevant issues from the backlog log based on the system ranking
If there is velocity left over in a sprint and the next issue is too big to fit, then the system moves to the next sprint to fill up.
The sprint availability is according to the Sprints potential velocity setting - the current sprint issues (points / hours - depends on board setting)

Use case

Teams use the Sprints Instant Scheduling to help in their sprint planning efforts. By setting a value for the Sprints potential velocity, the Sprint Scheduling will set the issues in the backlog onto the future sprints set. You have options to automatically open new sprints as needed.
Another way to use theSprint Instant Scheduling is to enter different Sprints potential velocity values until all the backlog items are completed within a given set of sprints. This provides an estimate of what velocity is required to complete your backlog of items.
You can then choose Rollback to clear the last issue automatic settings.
You can then assess the delta between the current team's sprints potential velocity and the required prints potential velocity to determine what additional resources are required to meet production demands within a required time.

User Interface

Features

Hour / Points -
- Reflecting the the board settings (estimations based on points or hours)
Future Sprints Velocity -
- The user will define the velocity per future sprints (points / hours)
Set default estimation to non estimated issues -
- This option will enable you to set default value (hours / points) to backlog issues which has no estimations set.
Future sprints -
- User choice whether to use existing future sprints, or to open new sprints in the backlog screen to host the assigned issues.
- Use only existing future sprints will assign issues based on the velocity set (Future Sprint Velocity) taking in account any existing set issues in those sprints.
- Create only X new future sprints will create new sprints as needed (limited by the number of future sprint set) first using the existing open sprints, and if there are still issues in the backlog - creating new sprints till they are filled - according to the velocity. The future sprints amount will be added to the existing open future sprints in your backlog screen.
- Add future sprints as needed - will behave the same as the prpeiviuse option, but without the limit of # of sprints. the app will open as much sprints as needed to fix up all the issues in the backlog.
Filtering issues from Backlog
- User can define the issue types to include in the auto scheduling. pressing the button will give a list of issue types for the board to choose from. there is an option "All" to be able to select all. All - is the default
- User can define the status to including the auto scheduling. pressing the button will give a list of statuses for the board to choose from. there is an option "All" to be able to select all. All - is the default
Baseline -
- Ability to set a baseline to which in case of rollback the system will revert to
- There is only one baseline that can be set at any given time. No option to return to prevues baseline if another baseline was se before.
Rollback -
- The app has a rollback to last baseline option.
- The rollback is relevant only to the backlog issues that were set in the Instant Scheduling performed.
- Any default estimation set will be reverted to 0
- Any new future sprints created by the App will be deleted from the system.
- You can not undo Rollback operation after performed.
General -
- issues with no estimation will be ignored and left out in the backlog