Planning your sprint
When you click on the Agile tab in your project, on the right sidebar you will find Version planning. A three-column table contains your project's tasks:
- The first column is for all issues, without prioritizing
- the middle column contains issues from the backlog - prioritized accordingly
- the last column is for specific versions (sprints)
If there is already a version named “Backlog”, it will be selected by default for the second column. If not, you will have to create it.
What is a backlog?
To manage your project well using an Agile approach, you have to know what tasks have to be completed to deliver a product. A backlog is a list of project tasks - user stories we want to implement - which are prioritized accordingly. To create a backlog in Redmine, you have to choose issues that have some importance for your project and move them to the backlog column in Version planning. Each task should be given a certain rank and estimation (story points or hours; to estimate a task, story points are often used, but to track the progress - time in hours, it should also be noted that a story point has its equivalent in hours).
How to plan your sprint
It might happen that too many tasks are in the backlog column. That's why there are sprints.
A sprint is a time interval, usually one or two weeks, during which the whole team is working to deliver tasks. The aim of a sprint is to prepare some part of the product, and during the iteration, it is being developed, tested, and shipped.
To plan a sprint, you can move issues from the backlog column to the sprint column.
To create a new version (new sprint), you first need to create a backlog. Then click on New Version, and provide some details for it.
You can also create a new version when you edit any issue. Just click on the green plus next to Target Version:
Version planning filters
You are able to filter issues in the table. You can filter tasks by author, status, tracker, priority, estimated time, and assignee.