| Treb さんのプロフィールEvil Doctor PorkChopフォトブログリスト |  ツール  ヘルプ |
|
3月10日 Ad Hoc Work RevisitedIf you were able to attend my presentation at Project Conference on Managing All Your Work using Project 12, my apologies! We had significant technical difficulties which made the demos less than effective. I've since re-recorded these demos for the DVD.
The goal was to show four common scenarios we've found in managing work could be handled in Project. In the interest of adding value, I wanted to recap the scenarios so that you will get the full value out of what we did in Project 12.
In this post, I want to review managing ad hoc work in Project 2007. Ad hoc work is the largest segment of work performed in most organizations. In some instances, it is as high as 80% of all work. My personal opinion is that this capability is the greatest enhancement to Project for this release. As we can now capture all activity, it enables a much clearer picture of overall resource utilization.
Ad Hoc WorkTwo examples of this type of activity can be Help Desk and Customer Service. In these cases, you don't know you have work to do until it shows up in the queue. However, it takes up a significant amount of time and affects your availability for other efforts.
Ad Hoc work is characterized as the following:
To capture this type of activity, you have three setup decisions to make.
Reserving Resource AvailabilityThe resource plan is used to reserve resource availability. This may be desirable when you have shared resources that are also used across multiple activities. In these environments, you may want to prevent other projects from "stealing" your ongoing activity resources. Otherwise, required activities may be impacted since your resources are busy working on project work. If this is true, then you will want a resource plan.
A resource plan is a way to "assign" a work resource to a project / plan for a set amount of time without having to specify a detailed work plan for the resource.
For example, I may be working on a project for 25% of my day. However, the Project Manager doesn't have 3 hours of work specified for me each day. With a resource plan, the PM can specify the 3 hours a day without requiring the work plan tasks to support it. This will in turn, reduce my availability by 25%.
So, if you have a shared resource environment, consider using a resource plan.
Logging Time on a Project/PlanThe work team is used to denote which resources can be assigned work and can log time against the project/plan. If you care about the actual amount of time spent on a project/plan at the highest level, you will want to add the work resource to the team for that effort. You would do this by using the Teambuilder function in Project Pro or PWA.
Note, the Teambuilder that appears on Resource Plans allows you to add resources to the Resource Plan. It does not add the resource to the work team. There are reasons for separating the two functions, which will be discussed some other time.
While a resource can be on both Resource plan and work team, they don't necessarily have to be. A resource that is on the team doesn't necessarily have to be assigned tasks either.
Tracking WorkTasks must be assigned to a resource to track work. You may either do this via Project Professional or through PWA. This is no different than in current versions of Project. You can choose to update task status and/or log hours. If you choose to log hours, you can do it at the project level or at the task level.
Real Life ScenariosSo, let's put all of this together. In this example, I have four teams.
Team 1 SetupTo meet the needs of the SQL Server team, a project / plan with a single task would be created. The single task holds the timeline of the project. For example, for a plan like SQL Server Support 2006, I would create a task with a duration of 260d to hold the year duration. The owner of the plan would then use Teambuilder to add all of the resources from the team to the plan's resource list. Then the owner would publish the plan. Once setup is complete, the team resources can then log hours against the plan. Team 2 SetupTo meet the needs of the SharePoint team, they will need to create a project / plan for the effort. This plan starts with a single task, outlining the timeline of the effort. This is also needed as the project timeline is used by the resource plan as the planning time window. The project owner will then create a resource plan for the project / plan to reserve the resources' availability. Once this is done, the owner will use Teambulder to place the resources on the project team. Once all is complete, the plan is published. The resources' availability for other work will be reduced, their work will show that they are allocated to the project and the resources can log hours to the project. Team 3 SetupThe training team really only needs a single task project with a resource plan. The task is simply a timeline placeholder so no assignments are required. Once the training team is added to the resource plan, their availability for other work is reduced. Team 4 SetupThe SharePoint conversion team needs to be set up like Team 2. The major difference is that they have set up milestones in the plan. Therefore, resources responsible for those milestones will have to update status on those milestones, in addition to logging their hours for the project. More to ComeIn a later post, I'll cover how these scenarios can be further enhanced with the use of team assignment pools. Team assignment pools enable you to do initial work assignments to teams rather than individual resources. We'll also discuss delegation, default assignment owners and the self assignment feature and how all of these can be used together to manage work. Stay tuned.
I hope this is helpful as a conceptual walkthrough of how these features work together to solve a common problem.
project 2007 project 12 Office 2007 Office 12 Microsoft Project Management トラックバック (203 件)この記事を参照しているブログ
|
|
|
