Previously we talked about the ability to add tickets en-masse as part of the Agile features. In this post, we'll be starting to look at Sprints and how they can be used to assist with your workflow: beginning with the Burndown Chart.

The Burndown Chart

As you may already know, Sprints are part of the SCRUM development methodology (outlined in further detail at, and allow you to group together tickets into "effort" based subsets, with the objective of completing all work outlined in the tickets before the deadline set in the Sprint. This is most often useful when you're aiming to complete a set of tickets that all relate to the release of a new feature.

Codebase allows you to track your Sprints with a Burndown chart, which you'll see when you come to the Sprint Management page in Codebase. You can use the chart to easily track the current performance of a Sprint, as well as compare it to the past performance of older sprints.

Burndown chart

The grey line represents the ideal "burndown" (the rate at which work should be done in order to meet the requirements of the Sprint) and the blue line shows the actual work rate, dependant on the calculation method defined in your project settings.

If the blue line is above the grey line, you're behind schedule, or it's below then you're ahead. The green line as a further addition shows how many tickets have been completed.

In Part 3, we'll be covering time and effort estimation, and how they're used in Sprints.

Drop us an email to if you have any questions.

Tell us how you feel about this post?