Now that you've familiarized yourself with the ZenHub board, customized pipelines, and created and organized issues, it's time to take a look at Sprints!
|Creating your first Sprint schedule in ZenHub||✅|
|Sprint automation options||✅|
|Adding Issues to your Sprint||✅|
|The difference between Epics and Sprints||✅|
In Agile-Scrum, sprints are a fixed length of time (typically two weeks) during which an agreed-upon chunk of work is completed and ready to be shipped. ZenHub Sprints allow teams to group Issues together that will be completed within this timeframe. With Sprints, teams can automate their sprint planning process and automatically carry over unfinished work into upcoming sprints.
Creating your first Sprint schedule
To create your Sprint schedule in ZenHub, select the green + icon located in the top right corner of your Workspace and select Set up Sprints for your team
From here, you can set your sprint schedule by selecting the start date and end date for your first sprint from the calendar view. ZenHub will automatically create 3 Sprints. New Sprints will be created continuously as each Sprint ends:
Sprint automation options
1. Move unfinished Issues to the next Sprint
By toggling this option on, when a Sprint completes (passes its end-date), all Issues assigned to the Sprint that have not yet been closed will automatically move to the next Sprint. As Issues can live in multiple Sprints when incomplete Issues move from your past Sprint to the new current Sprint, the Issues will continue to exist in the Sprint they are being moved from (i.e these Issues will belong to two Sprints)
2. Automatically build new Sprints from the backlog
By toggling this option on, ZenHub will automatically build your Sprints. Choose the number of story points you'd like added to your next Sprint and the pipeline you'd like Issues added from. ZenHub will automatically add Issues from the top of this pipeline to your Sprint. Issues that are not already estimated, will be counted with the value of 2 Story Points when being added into the Sprint from your backlog pipeline. Learn more
Adding Issues to your ZenHub Sprint
Now that you've set up your automatic sprint schedule, it's time to add Issues to your sprint. To add Issues, head to your ZenHub board. From here, you will able to use multi-action or a combination of filtering and multi-action to add the desired Issues to your Sprint. This is a great way to eliminate the onerous process of performing certain actions over and over again.
For example, your team may dedicate a sprint to tackling bugs. The team can filter the Board by the bug label, select all Issues, and choose the option Set Sprint.
The difference between Epics and Sprints
As Epics and Sprints are both used to organize work and boost your productivity, you may be wondering about how these interact and the main differences between them:
|Sprints allow you to group together Issues that will be completed within a fixed timeframe ( typically two weeks)||Epics allow you to group related Issues together and are the best way to plan and track both short-term and long-term goals.|
|Sprints are used to track the progress of issues and pull requests. They contain issues related by time||Epics contain Issues related in subject|
|The scope of work is fixed once a sprint begins.|
The scope is flexible. Issues can be added or removed as teams discover more about the bigger goal.
Epics are intended to give you a broad understanding of larger initiatives. When paired with Sprints, you’re able to work towards these bigger goals in manageable iterations. This means you deliver more business value (e.g. workable code) more frequently. Pairing Sprints with Epics gives you a granular way to plan and achieve your product backlog. It clarifies both the big picture and the minute details that make it up, providing everything necessary to ship better projects faster.
You're all set! With Sprints and epics you can increase productivity by organizing and structuring your work!