Small Projects and task names

[anovak]

I'm recommending that even for the smallest projects (2 weekers), that
each one is created as a project object in Project Server (for the
sake of meta data definition and reporting ease). On the other hand,
there would be no need for a detailed WBS - just start date, end date
and assign one or more resources to this "one-liner".

I believe you have to have at least one task line in order to assign
one or more resources to the project. I've noticed that all you are
required to do is enter duration, perhaps start, finish, and one or
more resource - not forced to enter a task name. Probably just as
well that we leave the task description blank because it would be
tough to control a standardization of what would be put in there
(project name, etc.).

On the other hand, is this a "best practice" "no-no" or is there a way
to "mix-n-match" and on the small projects that do not require a WBS,
assign resources at the project level and report progress at that
level? Any "gotchas"?

Thanks,
Andy Novak
UNT

 

[Sean]

While I cannot say if this is a best practice or not, it sounds like
you have lots of tasks, not projects. I would create a project
specifically for all the 1-task projects and have that contain each
small project. I don't know how many resources you have, but I'd say
if you have 20-35 resources on these 1-task projects it wouldn't be a
bad idea. It will certainly save you server space since you'll have a
lot fewer project entries but the same task and assignment data.

If you have too many resources that it makes the project clunky, make
several along common division in your corporation, perhaps by
function, group, or manager. That's what I would do at least.

--Sean

 

[anovak]

While I cannot say if this is a best practice or not, it sounds like
you have lots of tasks, not projects. I would create a project
specifically for all the 1-task projects and have that contain each
small project. I don't know how many resources you have, but I'd say
if you have 20-35 resources on these 1-task projects it wouldn't be a
bad idea. It will certainly save you server space since you'll have a
lot fewer project entries but the same task and assignment data.

If you have too many resources that it makes the project clunky, make
several along common division in your corporation, perhaps by
function, group, or manager. That's what I would do at least.

--Sean

We've thought about that; however, wouldn't that screw up your
portfolio views in PWA? That is, you couldn't display the same info,
filter, etc. alongside the large projects in the list? You would
end up having to replicate all project level custom fields at the task
level in order to capture all the portfolio data about the project.
There are ranking decisions made on these small projects (2-4 weeks;
2-3 months) compare with the larger ones.

By the way, as far as server space goes, we wouldn't have more than
400 projects total.

Thanks,
Andy Novak
UNT