Patrick Altman

I am the VP of Engineering at Eldarion, Co-Founder of Amino Software, and a Mentor at jumpstart foundry.

I am equally passionate about writing code as I am about building businesses.

You really should

Posted On

Sept. 5, 2006, 12:55 a.m.


Do you have an iOS or web application that you'd like help with?

Eldarion offers lean coaching, software development, code reviews, and in some cases staff augmentation.

Give me a call at 615-300-2930 or send us an email and let's see how we can help you.

This site is hosted on

You should consider it for your Django/Python web hosting as well!

Sprint Burndown from FogBugz

We've been using FogBugz to track work items for the Lysine project at Amino Software until we can make the move towards Team Foundation Server. 

In the meantime, we are leveraging our existing FogBugz licenses to give us a simulated Scrum workflow.  We've renamed the "Default" release bucket to Product Backlog and have created other "releases" named "Iteration 1", "Iteration 2", and so on, that are scheduled to complete at the 1st of each month. 

So far so good, except as we find bugs and add and close items on the current iteration, there is no good reporting for our burndown or velocity.  I spent some time digging in the database today to see what type of history and metrics were recorded by FogBugz on the individual work items. 

I found enough to allow me to build the following stored procedure which I plan on consuming either in Excel or some other reporting tool to provide us with simple burndown charts for each Sprint, or iteration.

Simply pass the id of the "FixFor" release bucket and viola, you'll get a nice dataset ready for plotting/reporting.

Feedback and Commentary

blog comments powered by Disqus