Blog Engineering Demo - Mapping work versus time, with burndown charts
Published on: April 25, 2017
1 min read

Demo - Mapping work versus time, with burndown charts

Our Frontend Lead Jacob Schatz explains how managers and ICs can benefit from our burndown chart feature, released in GitLab 9.1.

gitlab-2016-in-review-cover.png

Every software development team likely feels pressure to move faster, shipping more software in shorter time periods. With GitLab 9.1, we've introduced burndown charts to further help you track and manage your work.

Burndown charts for projects help teams visualize the number of issues that are incomplete as they progress through a milestone. You can see the number of issues left to do, along with their cumulative issue weight, "burn down" over the remaining time before your deadline. This prepares teams to foresee obstacles and make decisions sooner, for instance on resources or scope, if risks emerge further along in their timeline.

Demo:

In this brief overview, Frontend Lead Jacob Schatz explains how burndown charts help managers keep a high-level view of their team's work, even as they help engineers self-pace and stay focused.

Watch the webcast

For Jacob's entire presentation, watch the Managing the DevOps Culture Shift webcast on demand!

We want to hear from you

Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum. Share your feedback

Ready to get started?

See what your team could do with a unified DevSecOps Platform.

Get free trial

New to GitLab and not sure where to start?

Get started guide

Learn about what GitLab can do for your team

Talk to an expert