Reply to thread

Message: [QUOTE="Leonid, post: 5010052"] We are using Project Professional 2007 + Project Server 2007 in our company, but now we've met too complicated way of our resource management. In order to simplify it, I would like to better understand how environment of Project Server 2007 considers the project planning cycle. Please consider own business case and confirm whether proposed implementation of resource management feature is ok. ========= Business case description Our project management is based on our own methodology (basing on PMBOK). The standart lifecycle of projects is Initiation -> Planning -> Executing -> Closing. We have 1 resource pool (~20-30 people) which we want to plan. We consider following 3 roles: - Project Manager Responsible for management of scope (define WBS), developing the basis for the schedule (define links between tasks and determine duration of tasks) - Resource Manager Responsible for leveling resources and resource utilization - Team member Make work assigned ======================== Technical solution We consider implementing following decision according to life-cycle of project: 1. Project is authorized ======== Planning ====== 2. Project Manager (PM) defines the basis of the project, including preliminary scope, and role-based resources 3. PM creates the MS Project plan. PM puts the task â€œDevelop the schedule of project XXX / Phase YYY (if applicable)â€ to the schedule of the project and save the project. PM uses role-based generic resources which must be already included in Resource Pool by Resource Manager (RM) 4. RM checks the plan, change generic resources to specific, and level the project if necessary. RM publishes the plan. This way RM approves the request of PM for resources. 5. PM with team assigned develop the project scope (WBS), evaluate the work necessary for each assignment, develop links between tasks. After this PM saves this preliminary plan in MS Project. 6. RM checks the plan, if some generic resources are still used changes them to specific, levels the resources taking into account other projects, and publishes the plan. ====== Executing (and Monitoring) ====== 7. Works are done according to the schedule published. 8. Each week (or other basis for tracking) RM republishes all projects which includes work done this week. 9. If some changes in the schedule are necessary, we need to return on planning (step 5 and 6) ====== Closing ====== 10. PM uses the custom enterprise field "Open / In archive" to mark the project as archived. 11. RM checks that all assignment are completed and republish project. [/QUOTE]

Verification