Hi Grant --
Regarding these monthly recurring projects... are your intentions to
use EPM to track the progress of the tasks, or simply capture the Team
Members' actual work hours? Do they consist of a lot of task detail?
I've seen some organizations simply set up a set of year-long projects
to track ongoing or recurring work... such as operations / support /
maintenance work. These projects may consist of fairly detailed tasks
with links etc., or they may simply consist of one or more year-long
tasks which act as "time buckets" for capturing actual work hours.
At any rate, I don't think that you'll get good results from EPM by
simply repeating the same project schedule on a monthly basis; at the
very least -- if you need to track the detail, rather than establishing
time buckets -- I recommend that you duplicate the project schedule to
create 12 instances (1 per month), and set each "mini-schedule" to
start on the appropriate day of each month. These can be separate
project schedules in EPM (with potentially separate owners, status
indicators, etc.), or they can all reside inside of a single project
schedule. If you'd like to track them as separate schedules, but still
see a consolidated view of them all, then it's very easy to create a
master schedule which stacks them all up.
Good luck!
Tony Zink
========================================
http://www.msprojectreporter.com
http://www.pmreporter.com
http://www.sharepointreporter.com
http://www.msofficereporter.com
http://www.dotnetreporter.com
========================================
