Change Management Implementation Checklist

change-management-implementation-checklist-templates-sample-for-project-release Project Management Change Management Implementation Checklist

Birgit Kuester October 22, 2020 Project Management

The business requirements state what is required but do not specify how the deliverable will actually work. So in many projects with a tangible and technically sophisticated deliverable, it is very common to produce additional documentation about the look and feel of the end product. The functional specification describes not only how the end product will look but also how an end-user will actually use it and what the user-experience will be like. This document should contain sections that specifically relate to each of the requirements in the business requirements document so that every functional item can be tracked back to an original business need.

The next phase is the execution phase. Here the project must be monitored and managed. A schedule is derived which includes work breakdown, followed by allocation of tasks to people, allocation of resources and finally setting up deadlines for tasks. It is very important to have both a short-term goal and a long-term goal. While the long term goal is to get the product done, the short goals must be imposed by the project manager, who helps in guiding and motivating the members of the team working on the plan. Two important documents namely the issue log and the risk log which are both maintained by the project manager. The issue log keeps track of issues raised by the stakeholders and the risk log considers the vulnerabilities of a system.

With simple projects, a tool such as a Gantt chart may make over complicate the project scheduling. Unless all team members are trained in the tool then the use of the tool may itself lead to poor communication and an unsatisfactory result. A simple project such as those identified above may only require a timetable and/or an action plan. All those in the project team should be communicated with as to their tasks content and timing. Timetables can then be negotiated and agreed, actions lists or diaries/calendars can be used for recording and planning purposes.

The production and agreement of the business requirements is a substantial part of the overall project schedule and may take many iterations before it is finally approved. The project manager usually works with other departments or teams to put the document together. They will probably use Brainstorming and Interviewing techniques to help with this process and may even build a prototype