A forum for technical support discussion related to Fogbugz.
I'm posting this here, to get feedback and maybe even provide an idea that others find useful...
We’ve had several big projects where risk management and tracking has been necessary.
Risks are things like:
* “Not meeting performance requirements”
* “Software has security flaws”
During a milestone iteration, we attempt to “address” risks, just as we “implement” features or “fix” bugs.
So far, we’ve been tracking risks in Excel and have found that it’s less than ideal. I had the idea that we could create a custom category in FogBugz for tracking “Risks” -- I even found a cool dice icon on Google Image Search that I used for the category icon:
For the Resolved Status, I configured the following:
* Resolved (Addressed)
* Resolved (Won’t Address)
* Resolved (Duplicate)
* Resolved (Not a Risk)
* Resolved (Already Addressed)
So, I'm curious what others think about this. Also, what other custom categories have others created that they find useful to track in FogBugz?
Thursday, October 22, 2009
I did the same thing, calling the category "Technical Debt". It's working well for us, as it allows us to pick a good mix of bugs, features, and technical debt when we scope a release.
Friday, October 23, 2009
I've put this on StackExchange:
> I've put this on StackExchange:
Monday, October 26, 2009
Hehe... "Technical Debt > youthful transgressions" reminded me of the first credit card that I got while in college :p
Tuesday, October 27, 2009
This topic is archived. No further replies will be accepted.Other recent topics