Representing to do list in one task

[Spunky]

MS Project 2003 (11.2.2005.1801.15) SP2
Project Server 2003 SP1 (we have SP2 but were advised by our consultants to
not install)

What is a good way to have a to do list under a task so the task will
represent the duration of all and be resource loaded but yet have a list
below it of things to happen during that task being accomplished? I want
these visible on a line in the project not in the notes field. We are now
adding a task under a summary task to be the "summary" of the list below it.
We don't want it a summary task that rolls up because we want to resource
load, have dependancies and duration. The ones below are not resource loaded
but can show duraion. For visibility we are adding three dots on the
supporting tasks to indent them. Are we setting ourselves up for
complications later?

 

[Dale Howard [MVP]]

Spunky --

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

To answer your question, why don't you upload a "To Do List" document in
Word format to the document library associated with the project? When you
upload it, you can also associate the document with the individual task.
Team members assigned to that task will then be able to see an Document
indicator to the left of the task in the Indicators column of their PWA
timesheet view. Team members can edit the document as needed by clicking
the Documents menu, selecting their project, hovering the mouse pointer over
their "To Do List" document and clicking the pick list button, and then
selecting the "Edit in Microsoft Office ______" option.

The current service pack for Project Server is SP2a. Out of curiosity, why
have your consultants advised you not to upgrade? SP2a appears to be a very
stable service pack and fixes a number of issues with Project Server. I'm
just curious about their reason for the recommendation.

Hope this helps.

 

[Spunky]

I agree and would like to encourage more use of the document library but the
users are not comfortable enough to use it to that extent. Our customer also
wants to see the detail on the schedule as well.

I'm trying to find out why our consultants recommended not to load SP2.
Will let you know.

Spunky (Peggy - heard you speak last night in Denver)

 

[Wiley]

There will be some who disagree with me, and this is a practice I never do.
But what about loading the resoruces on the summary task, rather than than
the subtasks(to do's)? You get your loading, the to do's will allow the
detail with their dependencies and durations, and the duration rolls up to
the summary.

Please note that if you assign at the summary level, do not assign the
resources on the subtasks. Otherwise, the resources are assigned double work.