We're having a hard time understanding how to best use the Pipeline features in Daylite 3. As best we can tell, there is an assumption that no Stage can be entered unless the previous Stage has been completed.

But projects aren't always linear. Sometimes a Stage is completed in advance of another, and there does not appear to be any way to set the Status of a Stage other then to move forward from it.

Project Management software such as Omni Group's new OmniPlan is aware of this, and allows for pipelines to branch and nest.

How are users making use of linear Pipelines in our non-linear world?

As an aside, why on earth aren't the Pipeline numbers displayed in the Activity list, and why can't I see the graphic Pipeline Stage view at the same time I see a list of the Activity of those stages?

You can choose a new pipeline stage at any time, and revert to an "earlier" one at any time as well.

Pipeline stages don't have status, per se; they are either the current stage (in progress) or they are not. Daylite pipelines are fairly straightforward, for the time being.

As for the activity view, the numbers are a good suggestion. Activities, though, are not specifically tied to certain pipeline stages. So, generally you can look at the activities (tasks and appointments) for a project, while looking at its pipeline diagram, but the activities you are seeing are for the entire project.

HTH,

Dear Adam,

I have the same problem as David: in our design team, we work in a non-linear projects too with linear stages for parts of the project and that's always difficult to work with the pipelines.
For instance, on a design project, we work simultaneously on the product, the packaging, the tools etc... and we don't know which one will be finished the first. But for each part of the project (pack, product, tools etc) we work linearly, each stage must be finished before going next stage.
In Daylite 3, is it possible to show and use many pipelines at the same time for a single project ? If not, do you think you could update Daylite in this way ?

Thanks in advance.
Best regards.

Eloi.

Dear Adam,

I would like to add a better suggestion.
Graphically, pipelines are very pleasant to use, do not change that.
But I think you could consider pipelines much more like a checking list: Main pipeline could be like the current one but without arrow. You will click on a stage when it's done and the color change. Furthermore, sub-pipeline could appear just under the main one when you click on a stage, and sub-sub-pipeline etc... Main stage color change when all the sub-stages are checked.

Thanks for your attention.
Best regards.
Eloi.

I like pipelines well enough. But they don't end up doing much except offer eye candy.

To make them more useful I wish I could attach a task to a particular pipeline status so I could group and sort my tasks by phase.

In Projects, pipelines don't seem to be much more than eye-candy. They seem to be more useful for the Opportunities section since they can give a nice view of where a sales person is in the selling process, which for many types of sales processes, are fairly linear.

I like where Shawn is going with his idea of attaching Tasks to a particular stage on a Project Pipeline (as opposed to an Opportunity Pipeline). Let me suggest that we explore the concept of taking it further and add the ability to attach Activity Sets and Individual Tasks to Project Pipelines. This will make them truly useful and you will be able to know not only what stage you are in by which tasks have been completed, but you can also get a percentage of a stage's completion report.

This will not solve the problem for the people that need a true Project Manager. However, without a complete rewrite of Daylite I cannot see that happening. However, I think that there is a solution in the works that is made possible by Daylite's developer API. I think that high on Marketcircle's To Do list is integrating a couple of "real" project manager's with Daylite. How this will take form, I don't know. But there are threads on that very thing in the forum.