This paper is an update of a paper prepared for the June 2002 IPMA Conference in Berlin. It contains content from various training materials developed for the World Bank. The current paper is copyright to Robert Youker, © 2007.
Published here January 2008.

Introduction | Document #1: On-the-Job Tasks for the Project Manager 
Modules 1-3 | Modules 4-6 | Module 7 | Modules 8-9 | Modules 10-12
Document #2: The Project Manager's Duties | Document #3: Typical Elements in a Project Charter

Modules 8-9

Module 8: Getting Management Approval and Support

  • Review the proposed project implementation plan.
  • Verify resource commitments with the heads of departments where various pieces of the project work reside.
  • Determine who needs to give formal and informal approvals.
  • Develop a strategy for obtaining approval from relevant decision makers.
  • Prepare a presentation to management (project review).
  • Practice delivery of presentation.
  • Present to management and negotiate.
  • Revise plan as required.
  • Obtain sign-off (approvals).
  • Develop a strategy for maintaining support.
  • Implement the strategy for maintaining support.

Module 9: Designing Control and Reporting Systems (Time, Cost, Resources, and Scope (Performance and Quality))

  • Understand and be able to use standard tools for monitoring time, cost, and performance in relation to plan and for controlling scope.
  • Determine which management tools to use for controlling the process in terms of scope, time, performance, and cost.
  • Use the control period to determine the frequency of reporting.
  • Identify the kinds of data that need to be collected.
  • Identify who will provide the data.
  • Identify ways of making the provision of data rewarding or at least not burdensome.
  • Identify who will receive the reports.
  • Identify information processing requirements.
  • Design forms for data collection, display, and reporting.
  • Work with the information systems department as required to establish data collection, processing, and reporting systems.
  • Avoid setting up duplicate systems.
  • Design systems for simplicity.
  • Schedule routine, regular meetings for staff.
  • Separate project review sessions from detailed problem solving sessions.
  • Use appropriate technology.
  • Match the appropriate report style and content to the audience and purpose.
Module 7  Module 7

Home | Issacons | PM Glossary | Papers & Books | Max's Musings
Guest Articles | Contact Info | Search My Site | Site Map | Top of Page