A forum for technical support discussion related to Fogbugz.
Should I create one schedule item for debugging per project per release per developer?
Thursday, September 20, 2007
What we did here was have one person (in our case, me as the QA person) have a big debugging schedule item. And then as bugs rolled in during beta testing, those were estimated and assigned to developers. If you have a big schedule item for debugging for each developer, then when you assign them individual bugs, things will get confused.
We're still figuring out best practices ourselves, so we'll be interested to see how this works for everybody else.
We have many different products and as cases come in, we organize them and assign a release to each case. A developer knows he/she should work on several cases that concern a release. These cases may be bugs or features. For bugs, we enter one debugging schedule item for each developer/product/release.
I am also not sure if this is the best because we can't get useful EBS reports yet, because we have just installed FogBugz and there is lack of historical data.
Just need to know what is the best practice here. Anyone from FogCreek?
Friday, September 21, 2007
Oops, Eric... you are from FogCreek, aren't you? If you are I am sorry for my "Someone from FogCreek" comment. I assumed you weren't because you expressed an uncertainty regarding how to best use a schedule item.
Friday, September 21, 2007
Yes, I am from Fog Creek, but using EBS is still new enough (we've only been using it for several months internally) that "best practices" is still an evolving state. We are interested to hear how our customers start using EBS and see if we can learn together how to use this tool to its greatest potential.
We use schedule items for situations when you know you will have to spend time doing something, but it's unclear exactly what the specifics of that task are. For instance, if you have a list of features to be implemented for a given release, you shouldn't need a schedule item, because you can specify exactly what needs to be done. But if you know you are going to have to spend some time helping debug a different product and answering questions, you might create a schedule item for that, as it's a non-specific task you have to do.
Debugging in general is a non-specific task, so schedule items seem appropriate, but the difficulty is that as bug cases roll in, and you assign them to developers, the estimated delivery time of the release will keep getting later as it's counting both the debugging schedule item and the actual bug cases being fixed, which is a sort of double counting. We got around that here by having a non-developer (myself) with the debugging schedule item.
Does that make more sense?
This topic is archived. No further replies will be accepted.Other recent topics