J
joewatson
Hi,
I am a newbie to Project/Project Server 2007. I have some questions
on best practices with regards to non-project tasks.
My question is related to maintenance items and non-project tasks.
From the reading I have done here it seems that it is recommended not
to use the Administrative categories and create a stand alone project
for maintenance tasks.
How is the reporting aspect of this work?
Here is my situation:
I have an E-commerce team of 6 developers and there is also a
Peoplesoft team of 8 at my company. Initially I want to use Project
Server 2007 for managing projects for just the E-commerce team.
We have 14 websites that we maintain and about 10 web service portals
and one stand-alone application we distribute to users.
I am trying to figure out the best way to manage my resources by
planning out their projects and tasks. One developer can be working
on 3+ projects and then also have a laundry list of small changes to
any one of our websites or gateway. These are often from 1-2 hours of
work to 3 days - but still simple enough to not warrant a project.
If a high priority change comes in that is a 1 day task, I need to be
able to assign the task to a developer and work it into his schedule
and adjust his planned work accordingly. BUT....what I want to be
able to do is look back and see that in the last 6 months, 20 hours
was put into website A, 3 into website B, etc. and be able to show
the impact on a project by pulling a developer for a 2 day update here
or 1 day fix there.
Does it make sense to have a single maintenance project? The idea of
having 14 maintenance projects (1 for each website) and for each
portal plus the application is not appealing - especially with
growth. If I have a single maintenance project, is there a way to
classify tasks to allocate it toward a single website or application?
Hopefully this makes sense!
Thanks,
Joe
I am a newbie to Project/Project Server 2007. I have some questions
on best practices with regards to non-project tasks.
My question is related to maintenance items and non-project tasks.
From the reading I have done here it seems that it is recommended not
to use the Administrative categories and create a stand alone project
for maintenance tasks.
How is the reporting aspect of this work?
Here is my situation:
I have an E-commerce team of 6 developers and there is also a
Peoplesoft team of 8 at my company. Initially I want to use Project
Server 2007 for managing projects for just the E-commerce team.
We have 14 websites that we maintain and about 10 web service portals
and one stand-alone application we distribute to users.
I am trying to figure out the best way to manage my resources by
planning out their projects and tasks. One developer can be working
on 3+ projects and then also have a laundry list of small changes to
any one of our websites or gateway. These are often from 1-2 hours of
work to 3 days - but still simple enough to not warrant a project.
If a high priority change comes in that is a 1 day task, I need to be
able to assign the task to a developer and work it into his schedule
and adjust his planned work accordingly. BUT....what I want to be
able to do is look back and see that in the last 6 months, 20 hours
was put into website A, 3 into website B, etc. and be able to show
the impact on a project by pulling a developer for a 2 day update here
or 1 day fix there.
Does it make sense to have a single maintenance project? The idea of
having 14 maintenance projects (1 for each website) and for each
portal plus the application is not appealing - especially with
growth. If I have a single maintenance project, is there a way to
classify tasks to allocate it toward a single website or application?
Hopefully this makes sense!
Thanks,
Joe