The traditional method of project management has each project working independently to produce its own specific versions of the same basic documents and supporting processes.  Worse still, they will attempt to  overcome the lack of these tools through the heroic efforts of the project manager. In this environment the overseeing management layer provides no commonality to either the production, content or implementation of individual project plans.   

The premise of defining the processes and disciplines required to ready an organization for a project is that the organization will benefit from standardized organizational-level policies, standards, management processes, and engineering assets for all projects to use and that the project will benefit from appropriate management buy in and participation. 

Key Benefits

• Leads to further organizational improvement in software practice.
• Establishes an organization that is supportive to the software process.
• Adheres to industry practice.

Availability

Description	File	Size	Price
Organizational Readiness Plan - a template identifying key items required to establish management level participation in IM/IT projects.	download	58k
Strategic Business Plan - Not really an IM/IT issue but if the business does not have a plan it cannot do justice to assessing the business case of any investment decision.	download	50k
Business Case - A template for evaluating opportunities or requirements of investing in IM/IT projects.	download	36K

Additional support or customization of these and related products or services are available on a fee for service or fix price basis from Neil Kemp and Associates.

Related Sites

Software Engineering Institute (see level 3 SW- CMM practices)

[ Home ] [ Up ] [ MS Project Template ] [ Artifacts ] [ Risk Management ] [ Tracking ] [ Program Management ] [ Organizational Readiness ]

Copyright ©  Neil Kemp and Associates Ltd