1. Scrum Burndown in Trac
    1. News
    2. Description
    3. Using the plugin
    4. Questions
    5. Bugs/Feature Requests
    6. Download
    7. Installation Instructions
    8. Related Plugins
    9. Recent Changes
    10. Author/Contributors

Scrum Burndown in Trac

News

Description

A plugin to enable burndown chart capabilities, a common part of Scrum and other agile development methodologies. Look here for all information about the plugin: Scrum Burndown plugin

This plugin is integrated with the TimingAndEstimationPlugin.

Using the plugin

At the beginning of a sprint, after the tickets have been inputted and estimated in Trac an admin user should click the 'Start Milestone' plugin. This inputs a datetime integer into the milestone table to indicate when the milestone was started. The daily burndown_job.py script will only record hours_remaining entries for milestones that have started, but have not been completed. It should be fairly obvious, then, that an admin user should click the 'Milestone Complete' button at the end of the milestone to prevent the burndown_job from continuing to collect data.

You can view different burndown charts, selectable by milestone and component by choosing from the dropdowns and clicking the 'Show Burndown Chart' button.

In order for this to work, it is imperative that developers keep the 'Estimated Hours' and 'Total Hours' fields accurate and up-to-date on the tickets they are working. The 'Total Hours' field itself should never be manually edited, but rather, it can be changed by inputting positive and negative values into the 'Hours to Add' field.

Questions

  1. Is there an easy way to move the start date of a sprint into the past? (For example when some tickets of a milestone already have been closed when starting a sprint, immediately after installing this plugin.)

This can be done in the administration panel (only in Trac 0.11.x)

  1. Is there any way to automatically grant BURNDOWN_VIEW to any/all users? It's slightly annoying to have to explicitly set that permission on every user (which in our case is about 40 people).

Answering my own question, figured it out on my own. Any authenticated user pulls it's default permissions from the 'anonymous' group. This is all explained in the TRAC documentation: http://trac.edgewall.org/wiki/TracPermissions , if you add BURNDOWN_VIEW to the anonymous usergroup, everyone can view it. If you add it to the authenticated usergroup, any authenticated user will be able to view it.

  1. It would be awesome if you could take the Burndown chart and embed it on another page. Say, any wiki page or anywhere else you could use a wiki macro or something similar. (Should I file a ticket on this as an enhancement?)

This will be added in a future version -- Daan

  1. How do you stop monitoring the milestone?

Bugs/Feature Requests

Existing bugs and feature requests for ScrumBurndownPlugin are here.

If you have any issues, create a new ticket.

Download

Download the Scrum Burndown plugin.

You can check out the source using Subversion or browse the source with Trac.

Installation Instructions

Installation instructions can be found here: Installation instructions

Related Plugins

Recent Changes

[6667] by daan on 10/07/09 22:06:31

Fixes #4504 (big thanks for the patch!) Created Python 2.6 egg This will be the last release to support Trac 0.10.5

[6666] by daan on 10/07/09 21:28:43

Tagging scrumburndown release 1.9.1

[6665] by daan on 10/07/09 21:26:35

Reorganising Scrumburndown source tree

[5058] by daan on 12/25/08 11:43:40

Release of version 1.9.1 of the Trac Scrum burndown plugin. See http://stuq.nl/weblog/2008-12-25/scrum-burndown-plugin-191-released for more information.

A new version of the Scrum Burndown plugin for Trac is released, bringing compatibility for PostgreSQL, MySQL, Trac 0.11.2.1, and many bug fixes. Upgrading is recommended.

New features The Scrum burndown plugin is currently compatible and tested with Trac 0.10.5, Trac 0.11.1, Trac 0.11.2.1 Python 2.4 and Python 2.5. Additional to the previous SQLite compatibility, support for both PostgreSQL 8.3 and MySQL 5 has been added.

The following issues are fixed:

  • Fixes #1462 better control of milestone: a way to ‘reset’ a milestone
  • Fixes #1217 database upgrade fails after installing latest scrumburndownplugin
  • Fixes #2476 Error: ‘line_graph’ is undefined - stop graph from displaying
  • Fixes #1730 couldn’t upgrade
  • Fixes #2729 Error while running under PostgreSQL
  • Fixes #3102 burndown_job.py fails INSERT NULL id
  • Fixes #1909 Overshooting estimate reduces remaining effort while ticket is open
  • Fixes #1189 TracBurndown?-01.05.10-py2.4.egg error
  • Fixes #1800 No chart when clicking Burndown chart button.
  • Fixes #4047 AttributeError?: ‘NoneType?’ object has no attribute ‘getValue’
  • Fixes #2224 Changing ticket component causes removal from burndown
  • Fixes #2562 Creating a new component breaks the burndown graphic for “All Components”
  • Fixes #4222 Install fails on mysql
  • Fixes #2218 ScrumBurndownPlugin, trac 0.10.4, mysql

Author/Contributors

Current maintainer: daan
Previous maintainer: sambloomquist
Contributors:

Attachments