Administrative Projects - By Year?

[clin341]

All,

I'm in the process of creating an Admin project to capture non-project time
such as Vacation, Customer Support, Unplanned System Support time. I'm
trying to decide whether to create a project for each year. For example, I
would have an Admin Project 2005 with a start and end date of 1/1/2005 -
12/31/2005 and an Admin Project 2006 with a start and end date of 1/1/2006 -
12/31/2006. My purpose for dividing it up is to allow for archiving. Would
this be a good idea? Does anyone have other thoughts for this?

Thanks in advance,
CLin

 

[RickD]

Makes sense to me.

 

[mark.everett]

Clin -

Sounds like an excellent plan. This will also allow you to capture
metrics year over year.

Mark S. Everett | PMP
www.quantumpm.com

 

[clin341]

Rick, Mark,

Thanks for your replies. I just wanted to make sure I wasn't doing anything
that I'll regret later.

Thanks again,
CLin

 

[Ray McCoppin]

Administrative projects should not be to large. They can get to large with
all the timephased data for Project Pro to process effectively (accept
updates).

See statement below:

You can include an unlimited number of resources in an administrative
project; however, it is recommended that you limit the number of resources in
each administrative project. A summary resource assignment is created for
every resource that is assigned to a task in an administrative project. If a
resource is assigned to one or more administrative projects, then one or more
summary resource assignments are also created. Every time a project is opened
that contains that resource, all of the related summary resource assignments
for that resource are also opened. Summary resource assignments utilize large
amounts of network resources, increasing costs to your organization. For
example, if a project that includes 10 tasks has 100 resources assigned to
those 10 tasks, but each of those 100 resources are also assigned to tasks in
100 other projects, then this project when opened is the size of a project
that has 10,000 tasks. Therefore, it is recommended that you structure
administrative projects in your organization in a way that minimizes the
number of summary resource assignments and associates each resource with the
smallest possible number of administrative projects.

It has been recommended in some cases to do quarterly administrative projects.

 

[Gary L. Chefetz [MVP]]

Other than not using them, I'd go for making them quarterly and departmental
in nature.