Some specific questions about Deliverables

[med111]

As Deliverable is new feature in project 2007, I have some question
about it

1) When creating a template for projects, is it possible to indicate
the deliverables in the template?I already know that we must publish
the project before creating deliverable. but I need to define
deliverable in the template. how can I proceed?
2)What is the meaning of start date and finish date of deliverable and
how can this be usefull
3)When creating a deliverable and we associate in to "the selected
task". what does this mean? is that only done just to dislay a bar
representing the deliverable on the Gantt diagram ?
4)when we conceive a solution. What is the best way to manage
dependecies between projects : working with task linking, working with
deliverable or the both?

 

[Dale Howard [MVP]]

med111 --

In the future, please post your Project Server 2007 questions to the
microsoft.public.project.server newsgroup, as this newsgroup is devoted to
the Microsoft Project desktop application only. To answer your questions:

1. No, you cannot save Deliverables in a project template, because as you
noted, you must actually publish a project before you can set Deliverables.
However, the following Web site offers an incredibly helpful technique for
rapidly creating Deliverables in a project by using a custom Flag field to
indicate Deliverable tasks, and a macro to create the Deliverables on the
flagged tasks:

http://blogs.msdn.com/project_programmability/archive/2007/02/19/working-with-deliverables.aspx

Using the technique referenced in the above article, you could indicate
Deliverables in a template, and then the PM could create a project from the
template and rapidly create the Deliverables by running the macro after
he/she publishes the project.

2. You can use the Start and Finish date to indicate when the Deliverable
work is scheduled to start and Finish. How you use that information, if at
all, is entirely up to your organization's methodology for tracking
Deliverable work.

3. Yes, I believe your assumption is correct. If you want to see the Gantt
bar for a Deliverable, associate it with a specific task. If not, create
the Deliverable without linking it to a task.

4. If you want automatic updating of projects that are dependent on other
projects, I would recommend using cross-project dependencies. If automatic
updating is not important, then use the Deliverable Dependency feature.

Hope this helps.

 

[med111]

thank u for all these informations. it will be very helpfull for me.
In future, I will try to post in the correct group.

 

[davegb]

med111 --

In the future, please post your Project Server 2007 questions to the
microsoft.public.project.server newsgroup, as this newsgroup is devoted to
the Microsoft Project desktop application only. To answer your questions:

1. No, you cannot save Deliverables in a project template, because as you
noted, you must actually publish a project before you can set Deliverables.
However, the following Web site offers an incredibly helpful technique for
rapidly creating Deliverables in a project by using a custom Flag field to
indicate Deliverable tasks, and a macro to create the Deliverables on the
flagged tasks:

http://blogs.msdn.com/project_programmability/archive/2007/02/19/work...

Using the technique referenced in the above article, you could indicate
Deliverables in a template, and then the PM could create a project from the
template and rapidly create the Deliverables by running the macro after
he/she publishes the project.

2. You can use the Start and Finish date to indicate when the Deliverable
work is scheduled to start and Finish. How you use that information, if at
all, is entirely up to your organization's methodology for tracking
Deliverable work.

3. Yes, I believe your assumption is correct. If you want to see the Gantt
bar for a Deliverable, associate it with a specific task. If not, create
the Deliverable without linking it to a task.

4. If you want automatic updating of projects that are dependent on other
projects, I would recommend using cross-project dependencies. If automatic
updating is not important, then use the Deliverable Dependency feature.

Hope this helps.

--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultanthttp://www.msprojectexperts.comhttp://www.projectserverexperts.com
"We wrote the book on Project Server"







- Show quoted text -

Just curious here. What is the definition of "deliverable" as you're
using it here? When I took PM classes many years ago, a task had to be
"measureable and deliverable". I was taught that every task had a
deliverable, or it was not a properly defined task. I'm gathering that
you're using a very different definition. Is this another MS
redefinition of a term? Or does it come from somewhere else?