Application Maintenance

S

ScottC55

I'm hoping that I'm missing something but there doesn't seem to be a good way
to track application maintenance in EPM 07.

I see four primary features as a requirement for app maintenance / mgmt:

1. Easy to make assignments and schedule (Not requiring a mpp file).
2. Non cluttered timesheets but with appropriate wbs (security, reporting,
arch, etc.) at the application level.
3. The ability for Management to understand which applications are costing
the most to maintain and whether there are any trending problem areas that
warrant the development of reusable components and or decomissioning an
application.
4. Decrementing resources availablity via committments to application work.

Seems like we have 3 options for App mgmt / maintenance none of which hit
the 3 requirements above.

1. Use an MPP file (fails at 1)
2. Use Admin work (fails at 3, probably 4?)
3. Use Activities (fails at 1 and 2) - If only you could make assignments
at the team level then this strategy would be viable.

Any thoughts on this?
 
G

Gary L. Chefetz [MVP]

Scott:

The timesheet system in Project Server is lacking, but it's functional at a
basic level. Dismissing those limitations, it sounds to me that activity
plans with Team Assignments might be the best way for you to go. You can
assign Team Resources to Activity plan tasks.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
 
S

ScottC55

Thanks Gary,

But it doesn't seem like all resources can charge time to the same task when
using a team assignment on an activity. The only way this can be done is if
you don't define tasks but assign the team to the activity and then they can
all charge to that activity. Obviously that's a little bit of a shortcoming
because you really can't determine where your spend is going.

Perhaps there is another option?
 
G

Gary L. Chefetz [MVP]

Scott:

There are lots of ways to skin this cat. I do not know your culture or the
rate at which these tasks are generated, or how many applications you're
managing, or your specific reporting requirements, so it is difficult to
give you sound advice. I typically spend a lot of time with clients
analyzing this type of problem before choosing a path. With that said, you
could use any of the methods you stated, but you've already dismissed them
all, plus the use of mpp files which you've also dismissed out-of-hand. I
don't believe that they all fail the way you state. Again, this is very
"preference" and "comfort" driven.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
 
S

ScottC55

I agree and good points...Fail is a bit of a strong word:).

Just wanted to make sure these are my options and I'm not missing something.
I can work with below albeit not entirely what I expected.
 
G

Gary L. Chefetz [MVP]

Scott:

My best advice to you is to do the least possible to effectively track this
work. What I mean by that is your solution should be minimalistic when it
comes to detail. Use just enough to get the job done. Following this
mandate, your end-user experience is less imposing which makes adoption
easier.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
 
S

Scott

Agreed - and as always, thanks for your help!

Gary L. Chefetz said:
Scott:

My best advice to you is to do the least possible to effectively track this
work. What I mean by that is your solution should be minimalistic when it
comes to detail. Use just enough to get the job done. Following this
mandate, your end-user experience is less imposing which makes adoption
easier.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
Click to expand...
 
Top