5

2

FogBugz seems like a nice way to have to views on the same database: one for engineers and one for project managers. This way new tasks (i.e., bugs) added to the bug tracker automatically show up on the project plan, thus minimizing the effort in keeping things in sync. However, searching the various databases and playing with the trial fogbugz on demand led to a dead-end regarding one critical feature: how to set up task dependencies.

With this, I could see how to use it as a replacement for a Gantt chart. Without it, I don't see how to properly set priorities / determine the critical paths.

flag

4 Answers

3

This is the kind of thing that milestones are designed for. Milestone dependencies filter down to the per-developer timelines, which have a lot of the features of Gantt charts, but don't obscure important information.

Per-Dev Timelines

Task-by-task dependencies, or Bugzilla-style blocking, seems like a natural idea. I can't do X until Bob gets off his butt and does Y. What could possibly go wrong?

Well, it turns out that offering this kind of blocking is hideously inefficient and actually prevents projects from going forward or bringing all their resources to bear on the problems they're trying to solve.

But milestone dependencies, that seems sort of heavy-handed, right? Well, that depends on what you think of as a milestone. Once you start thinking of a milestone as any fixed point along the project lifespan, and creating as many as you need to do your job, dependencies become much easier. A milestone can represent a sprint, a release, anything.

Beyond that, we find that sub-cases and hierarchy give enough dependency indication that people can see at a glance where they are in the project.

link|flag
1 
One of the problems with a different tool paradigm is trying to understand how to do an old paradigm thing in the new system. In this case, how would milestones determine critical paths so that I, as the project lead, refocus / reassign engineers? – Steve Friedman Dec 17 2009 at 23:32
1 
There does not solve task interdependency within a sprint. Suppose Tasks A and B are assigned to different team members but B depends on A's completion. It is very unrealistic to create milestone for case such as this which is very common. Without this feature it's not really possible to detect schedule conflicts between tasks. – Gabi Davar May 15 2010 at 21:36
2

I know theres dependencies available for Milestones, but thats not as granular enough for my company's personal need.

Basically we need to be able to set up dependencies between any two cases/sub-cases, across all projects. Which would require displaying (among other things) two fields on the case add/edit page 1. cases that depend on this case(X) 2. cases this case(X) depends on.

It would help out with our scheduling, making it easier to keep tract of what tasks/cases/sub-cases need to wait until case X is at a certain status.

link|flag
2

Check out the Dependencies Plugin. As of this writing, it's currently only available for licensed FogBugz installs.

link|flag
Are there any plans to get the dependencies plugin into hosted FogBugz? Not having this feature is causing considerable consternation when dealing with tasks that are required for multiple new features (making subcasing tricky), where it is uncertain whether some features will be in the early milestones (making milestone dependencies tricky). – Todd Aug 22 at 20:22
@Todd this plugin is available for both On Demand and licensed FogBugz. For On Demand, go to Admin > Plugins, View All Available Plugins (At the bottom of the page). – Ben McCormack Aug 23 at 14:07
Thank you. I was apparently having one of my periodic low-IQ moments when I looked for it. I have every reason to hope that it does exactly what we need, and will learn more shortly. – Todd Aug 25 at 14:51
1

You can create Dependencies (under Admin->Projects) for your Milestones -- does that help?

link|flag
1 
I think that you would end up with too many milestones in order to properly reflect the critical path. However, I'll review that functionality. (The ideal goal, of course, is for tasks on the critical path to automatically elevate in priorities on the individual developers task list. The other advantage is to allow the senior developers to recognize when they need to help out on tasks that risk the delivery date.) – Steve Friedman Dec 18 2009 at 2:20

Your Answer

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