none
Timesheet for Support projects RRS feed

  • Question

  • Need expert advice on managing timesheet in EPM 2010.

    Requirement –

    Irrespective of the actual hours, we want the support task to have resources assigned at a fixed allocation daily till end of the task.

    Implementation -

    We have EPM implemented with all project (that will end) and support (created as a project) with single entry mode enabled. We expect every resource in the organization to report their complete hours (40 hrs/week). For resources working on support, following is done

    Here is what is happening

    Day 1, 12/31/2011 support project created

    Task – Support EPM

    Start - 1/3/12

    Duration – 255

    End - 12/31/12

    Resource – Jim assigned at 10%

    Behind the scene, MS assigns Work = 204 hrs

    April 10<sup>th</sup>, 2012

    Actual Work = 204 hrs

    Remaining work = 0

    Task % complete = 100%

    We really don't want the task to get completed or remaining work to drop. Basically remaining work on this task should always be sum of hours based on  % allocation of all resources from current date till finish date. This way resources are always allocated at a certain % for support and remaining for the normal project.

    Wednesday, April 25, 2012 9:17 PM

All replies

  • EPM User --
     
    Your requirements are unrealistic, as your expectations are NOT how either Microsoft Project 2010 or Project Server 2010 work.  What you will need to do is to teach your team members to monitor the Remaining Work on their support tasks.  You will need to instruct them to increase the Remaining Work when it approaches 0 hours.  This must be the responsibility of each team member to make sure that the task is not marked as 100% complete until the end of the year.
     
    So, in other words, you cannot force Project Server 2010 to work the way you want it to work.  Instead, you will need to implement a methodology for tracking progress in the support project.  Hope this helps.
     

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Thursday, April 26, 2012 12:44 AM
    Moderator
  • Hello Dale,

    How about using Resource plan. Some time back I came across similar situation and customer was happy to use Resource Plan for support projects, but it was in 2007.

    I am sure there must be big difference as compare to normal project tracking , but do you think something is better than nothing?


    Hrishi Deshpande – DeltaBahn Senior Consultant
    Blog | < | LinkedIn

    Thursday, April 26, 2012 1:56 AM
    Moderator
  • Hrishi --
     
    The only problem with using a Resource Plan is that the team members have no way to enter progress.  You should only use a Resource Plan for a project or a proposal that is in the planning stages when you want to �??reserve�?� a resource�??s time.  However, before the project goes live, the Resource Plan should be replaced with actual resource assignments in the project.  So, no, a Resource Plan will definitely NOT help this user.  But thanks much for trying, my friend!  :)
     

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Thursday, April 26, 2012 2:35 AM
    Moderator
  • As Dale pointed out this is not how Project works even if it would be cool if it did.

    the upside to doing as Dale suggests is that it does encourage (by requiring it) your resources to take ownership of their tasks and the amount of work required to complete them. This will make a HUGE difference when they are doing the same thing on 'normal project' tasks. Making them constantly monitor the remaining work of their tasks is a very good thing for your organization. This is not just me making an excuse for the way Project works. It is seriously just a great way to increase the communication between the team members and their PMs. All status updates should include an update of actual work AND an update (or at least a verification of) remaining work.


    Brian Kennemer - Project MVP
    DeltaBahn Senior Architect
    endlessly obsessing about Project Server…so that you don’t have to.
    Blog | Twitter | LinkedIn

    Thursday, April 26, 2012 7:22 AM
    Moderator
  • Brian --
     
    I LIKE your approach, my friend.  :)
     

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Thursday, April 26, 2012 12:06 PM
    Moderator
  • Appreciate all your comments and feedback. We are extensively using the work remaining field (along with reasons for change) for the "true" projects. In those projects, resources do know exactly what's on their plate and what it will take for them to complete. Support on the other hand is unplanned, unknown. Letting individuals provide work remaining will create variable level of allocation for suppor, that is something we want to avoid.

    Currently we have recommended everyone in support to use "insert row" to pull the task in the timesheet. This way they are able to report actual to the support and we can manage the allocation implicitly at a certain percentage.

    Monday, April 30, 2012 6:28 PM
  • EPM User --
     
    Well, your technique will work as well.  Either way, however, it is more work for the users to submit time against a support task that is already completed.  But thanks for sharing a clever solution to the problem.  :)
     

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Monday, April 30, 2012 6:32 PM
    Moderator