IT Business Edge takes the areas of project and change management seriously. We've developed some templates of our own to help us through these processes and have posted them in our Knowledge Network to share them with our readers.
Here's a look at three of our templates.
As identified in this document, the purpose of this plan is to ensure that all changes to the project are reviewed and approved in advance; all changes are coordinated across the entire project; and all stakeholders are notified of approved changes to the project. Also, the goals of this document are to give due consideration to all requests for change; identify, define, evaluate, approve and track changes through to completion; modify project plans to reflect the impact of the changes requested; bring the appropriate parties (depending on the nature of the requested change) into the discussion; and negotiate changes and communicate them to all affected parties.
The purpose of this document is to lay out the process for development of all IT projects within IT Business Edge. Projects include initial application development, enhancements and maintenance. These procedures can be modified over time as the company and its projects change. In the event that outside development teams (onshore and offshore contractors) are used for a particular project, these procedures will be presented to these teams for buy-in prior to the project kickoff.
This simple, three-page template covers the basics of top-level project justification. For larger projects, it should be accompanied or followed by more intensive financial projections, but for smaller projects, these key points will prepare a prioritization committee or group of managers to green-light a proposed project for formal business requirements and functional specs.