![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Project Management Software Tool Adoption20 January 2009Prepare Project Management Software Tool Adoption ScheduleIn listing all tools and performing a gap analysis on each one, the PMO team has defined all the work necessary to prepare the tools for distribution and use. In this section, the PMO team completes the Tools Execution Plan by creating a schedule for the work to be done. The following factors should be taken into account when developing the schedule: 1. The scope of work to be done. If almost all the work is small revisions, the job may take very little time. On the other hand, if many tools need to be developed or revised and tested, then the creation of tools can be a major effort. 2. Coordination with the overall PMO execution plan. The methodology, standards, and processes must be set before significant work can be done preparing tools. Also, completion and approval of tools is essential before PMO services that apply or teach those tools can be launched. 3. Available resources. The PMO staff may be sufficient to complete the work in the time available, or it may be appropriate to retain additional internal or external project management, writing, and technical expertise. Taking these factors into account, prepare the tools adoption schedule in the Tools Execution Plan. Here is a partial example:
Next StepsYou have learned how to adopt tools. Now you can:
Posted in Project Management Office
Copyright © Method123 Ltd 2000-2012 |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||