References

Chapman, J. R. Project Management Scalability Methodology Guide. Available from www.fda.gov/cder/handbook/develop.htm New Drug Development Process. 1997.

ЦШ Ш:1 h1j:1mhihiI!iw1

Chapter 6: Supporting the Methodology

Overview

Any organization that intends to support a formal project methodology should realize that it would not simply end there. Much more is needed than simply using a project methodology for your project delivery process. You need to support your methodology after you have implemented it. Key factors that your organization should consider before commencing with the implementation include:

There must be an executive commitment to the continual support.

The methodology must be accepted in totality by the organization and all required input must be received.

All project managers and support staff must be trained in the proper use and functionality of the methodology, its tools, and its processes.

All projects must be prioritized and identified in the organization.

Prioritized projects should be funneled through the project office, which, in turn, schedules the projects in accordance with the resources available.

Processes must be updated to reflect the presence of the new methodology (i.e., the financial reporting and executive reporting systems must be updated).

1кШиШ=1 1иллл1М1Ы1Д

Levels of Maintenance

A certain level of support or maintenance must be given to the newly implemented methodology. It cannot simply exist on its own it requires constant support and nurturing to fully maximize the efforts and value the organization needs. The following levels of support are necessary:

Level 1: Minor level. At this level, project templates are updated or removed and replaced by improved versions. A member of the project office team administers this level of support.

Level 2: Intermediate level. At this level of support, recommendations to change key processes are considered. A competent member of the project office team who specializes in processes and project management administers this level.

Level 3: Major level. At this level, support oversees situations such as a database supporting the framework goes down, project managers do not have access to their files, a phase is added to the methodology, or conformance to a new specification or government regulation requires that the methodology be adjusted. This level of support may generate additional work for the project office team supporting the methodology.

The following questions are frequently asked about the maintenance and support of project methodologies: When does maintenance begin for a project methodology?

Does the project office maintain the methodology or is this left to individual users?

Maintenance is a fact as business needs change; therefore, although maintenance is necessary at the end of the development process framework definition, it should be considered from the very beginning of the project. The project framework guideline document should make it explicitly clear that support will be provided to all users of the methodology.

A methodology does not ensure maintainability by itself. Maintainability and support are made possible by a combination of five factors:

Tools.