5

I get it, EBS seems pretty useful. But, how do I organize my stuff to get the most use out of EBS?

flag

1 Answer

4

For example, let's start off with 2 areas, Back-end and Front-end, and 2 teams. Each one with its own Primary Contact who is responsible for that Area. Now, let's add new functionality called 'X' scheduled to be delivered. Each functionality contains some portion of back-end and some portion of front-end. Now, that's great when you have one case, but typically there'll be many cases, so you'll want to make a 3rd area called 'General'. Place the parent case for feature 'X' in the area 'General', then create appropriate, two in this scenario, sub-cases in the areas 'front-end' and 'back-end'.

How do I see the chances to finish on time outside of the EBS visual graphing reports?

So this parent case in 'General' represents the whole description of functionality with no estimate, and the 2 sub-cases would have the estimates. Then, create a filter for the parent case and/or area 'General' and FogBugz will summarize the hours in the grid view. For example:

Estimate Hours Per Feature

Essentially, the parent case is for organization only, and the estimates and actuals are on the sub-cases for EBS. In the list view, you can filter by area:General and see the summed times in the grid.

link|flag
What does this have to do with EBS? It seems to just be about filtering cases and braking hours to the correct person. – cdeszaq Nov 5 at 15:28

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.