The basics
To start, you’ll want to create a Scrum project. Here’s how:
- Create a new project and use the Scrum category
- Create a scrum board in that project.
- Set your sprint cycles (e.g. 2 week sprint, 4 week sprints) and how you want to estimate work (e.g. using story points, days worked, etc.)
- Start creating stories and tasks and putting them into your backlog
- When you are ready for your first sprint, start moving tickets into the first sprint.
Boards
Separating your backlog from your board columns is a great way to keep your team focused on work that is ready to be ingested. By doing this, you provide team members that are performing Product Ownership roles a dedicated place to work within to prioritize/rank work that is in the pipeline. We believe that reducing clutter in every view is important.
The purpose of columns on a board are to group issues that are in a particular status together, and to provide users with a low-friction way of updating issue status (with a simple drag and drop functionality).
Note: Board columns can be configured so that they match your workflows and processes. We recommend mimicking the workflows statuses on your board. However, if you have lengthy, complex workflows, consider aggregating the board columns to include multiple statuses. Simple is always better.
Scrum masters will then be able to schedule work into active sprints and work with developers to follow the Scrum framework and methodology.
Level-up your use case
Beginner: Use reports to look at the data and monitor progress and improvement ideas.
Intermediate: Leverage out of the box configuration as much as possible, especially for the first couple of sprints. Avoid customization until you have some key learnings.
Advanced: Use the Team feature in Advanced Roadmaps to drive ownership of work and enable work management and capacity planning across teams. Expose this field on your issue screens to ensure the data is always captured (which will improve filtering capabilities).
