Part A
Project Documentation Aspects
There are two aspects that can be considered during project documentation. They are:
Based on your understanding of the topic, create a report in a Microsoft Word document to express your views on the following:
What are four different types of performance reporting? For each of them, describe the following:Who will be the target audience?How often you will use this type of reporting?
Part B
Design Phase Summary
This assignment is in continuation to the project discussed in Submissions Area assignment in Week 4.
All documents for the design phases from previous weeks will be resubmitted including, the project schedule, the project charter, the project budget, and the change control management plan. Changes should be made to the originals based on instructor feedback or if there were changes in the project.
In this week, you will additionally focus on preparing a report that details the end of the design phase. The report should be submitted to the CEO who will approve the beginning of the development phase.
The report should address the following:
Running head: RISK AND BUDGET MANAGEMENT
1
Project management
ITS4011
February 10, 2020
RISK AND BUDGET MANAGEMENT
2
Change Management Control Plan
One of the things project managers can do to ensure that the project meets the goals and
objectives is change management. Change management is mainly geared towards formal
protection of the project scope. Changes are inevitable but if changes are not well documented
in a control process, they can be disastrous to both the project and the organization (Paton&
McCalman, 2008). There are a wide variety of changes that can occur. For example, adoption
of a new technology, quitting or relocation of a member of the project team, reduction of
budgets, change vendors or even addition of a new feature.
All these changes must be dealt with formally because they have an impact on the
project. Although some changes may be insignificant, managers may assume but they finally
add up to be disastrous. One of the things the project manager should carefully consider is the
scope creep. Scope is usually stated at the beginning of the project but may grow continuously
over time. A well-documented change control plan makes it easy to deal with scope creep
because it assesses the change before justification based on the impact the scope will have on
the project. The change control plan dictates specific procedures for reviewing, proposing and
allowing project changes.
Changes may be reviewed in terms of costs, feasibility, impact of risks, value etc. some
organizations have a Change Control Board (CCB) to analyze all proposed changes. A detailed
change request form should be submitted to request the necessary changes and the reason why
changes will be necessary. It is now the duty of the Change Control Board to review the
suggestions and decide whether to accept or deny the changes. in other cases, changes may
have a huge impact such that the change control board may just warrant starting a new project
to accommodate changes especially when costs of change is higher than the cost of starting a
new project.
RISK AND BUDGET MANAGEMENT
3
If the change has been warranted for the continuing project, it is the work of the project
team to update the scope of the project as per the Work Breakdown Structure (WBS). The
project plan should now be updated containing the new change. This includes all changes that
have been made to the project budget, changes in quality needs, changes in the scope and
impact of risk, procurement procedures, communication, schedule changes, resources and all
other related changes based on the scope. Change is inevitable and may sometimes be difficult.
Employees and project member may resist the change or go slow in it. It is the duty of the
project manager to keep morale team member’s morale high to accomplish the change
objectives.
Website developers should demonstrate the reasons for change. This May be gaps in
new technology or shifts in organizational mission. In the second step, the developed needs to
explain the scope of change or the expected nature of change. According to Wikistaff (2018),
this defines of policies or job roles will change. This will also include departments and
components that will face the change. Thirdly, the developer needs to seek stakeholder support
by stating the specific stakeholder that may be affected.
If it concerns new technology, the developer should communicate succinctly to the
project sponsor to fund the change. Interviews are vital in stakeholder review. Change
management team is created with distinct roles for implementation. This is followed by a
communication plan that reinforces reasons and importance of change. Next, the manager
should tackle resistance by looking all grievances. Stakeholders may complain lack of inputs,
uncertainties and management failure. Lastly, addressing the roadblocks above enhances
communication and implementation of change.
RISK AND BUDGET MANAGEMENT
4
References
Flyvbjerg, B. (2013). Quality control and due diligence in project management: Getting
decisions right by taking the outside view. International Journal of Project
Management, 31(5), 760-774. Retrieved from
https://www.sciencedirect.com/science/article/pii/S026378631200138X
Galante, G. M., La Fata, C. M., & Passannanti, G. (2019). Project monitoring by dynamic
statistical control charts. The Journal of Modern Project Management, 7(3).
Paton, R. A., & McCalman, J. (2008). Change management: A guide to effective
implementation. Sage.
Wikistaff. (2018). How to Write a Change Management Plan. Retrieved 4 February 2020,
from https://m.wikihow.com/Write-a-Change-Management-Plan