A
anovak
We are putting together some project portfolios per responsible group
within our IT organization (listings for now), most of which are <
month that may not need WBS. There are literally hundreds of these
and we are trying to get our arms around general staffing requrements.
I figured it doesn't make sense to try to create a single project file
for each one of these. It would get very tedious. If a project
required a "project plan", we would create one, change the entry in the
project list to a milestone, then make the last task of the project
plan the predecessor to the entry in the list so that the dates match
up.
Does anyone see any better way of approaching this? This way, we can
provide an overall "project list". If the plans existed separately,
it would be difficult to include them in the "list".
Another ? -- related to this....what is the task limit in each project
file (that would affect the total number of projects we could track in
the list).
Thanks!
Andy Novak
University of North Texas
within our IT organization (listings for now), most of which are <
month that may not need WBS. There are literally hundreds of these
and we are trying to get our arms around general staffing requrements.
I figured it doesn't make sense to try to create a single project file
for each one of these. It would get very tedious. If a project
required a "project plan", we would create one, change the entry in the
project list to a milestone, then make the last task of the project
plan the predecessor to the entry in the list so that the dates match
up.
Does anyone see any better way of approaching this? This way, we can
provide an overall "project list". If the plans existed separately,
it would be difficult to include them in the "list".
Another ? -- related to this....what is the task limit in each project
file (that would affect the total number of projects we could track in
the list).
Thanks!
Andy Novak
University of North Texas