CPMGT/300: Project Management 1 week 5

July 6, 2020

Pedersen

Project Proposal

The Parcs is an outdated apartment centered in a desirable residential area. Upgrades to the property would increase property value, revenue and provide comfortable modern living for residents. This new construction calls for the removals of current flooring, cabinetry and appliances, which will be replaced with fresh paint, hardwood flooring throughout with newly carpeted bedrooms, modern cabinetry with quartz countertops and energy efficient stainless steel appliances in each unit. Project will be funded and sponsored through lenders with the help of PG&E’s “Go Green” campaign.

Project Requirements, Risk, and Cost

Please see attached.

Project WBS and Gantt Chart

Please see attached.

Circumstances the Project Might Consider for Change

It is okay for the project manager to authorize change when having the ability to continue a project successfully without derailing it due to new changes being made or added. Change is an inevitable part of a project, so working out in advance how best to handle change requests will make the whole process much easier. Many workers want to work for a great project manager but need to be shown that the project manager has a good reputation by selling the project. Change control or change management for IT projects is different to managing operational IT change. Any change need to be analysed for its impact on the project objectives and scope. Modify your existing plans, and need to be recorded properly for a complete audit trail. If and When a change happens there steps that need to take place. A request to make a change to the project is received this means you want the person suggesting the change to be as specific as possible and to put their request in writing. Update the change log. The change log in its simplest form is a document where changes and activities to assess changes are written down. Make a note of this latest request. Assess the priority of the change request. Give the "change request" a priority. Is it critical, important or nice to have? This provides a sense of urgency for planning the impact analysis. As a team, look at the change request. It is helpful to assess all changes against the same criteria. The purpose of the assessment is to decide whether to approve or reject the change. Take the decision, and communicate the outcome to the relevant stakeholders and those affected by the change. Update the change log with the outcome and rationale behind it. If the change is approved, amend all the appropriate project documents. Once you have completed all the steps of a change management process, you will need to delegate the tasks to the right IT resource to get the change made. This could be to developers, testers, architects or anyone else who is impacted by the work

Change to Scope, Timeline, and Budget

“To help you respond quickly, a project change management plan describes what happens when deviations occur. It's not intended to prevent change; rather, its purpose is to outline a process that makes clear how change will be communicated, how decisions will be made, and how the project will adapt accordingly” Suchan (2019). To request a change to the scope of work, the project’s timeline, or the budget, a change request form must be submitted in writing; by doing that, it will help the project manager determine the priority of change, the importance of it and analyze how they will change it. On the request form, the description of the changes wanting to be made must also include the reason for the change, impact to the project, resources used to make the changes, the impact to the budget and the timeline of the project, any risks, and the changes to the quality of the deliverables.

After the change request form has been reviewed and submitted, it must be documented in a logbook stamped with either the approval to request the change from the stakeholders or as declined and deemed unnecessary. If the request is approved, the project manager must then present the request to the stakeholders for their approval and documented once again in writing and in the logbook for approval or declined. If the request has been approved by the stakeholders, then the change can begin to be made through the team leaders, the resources, and the team members needed to correct the change.

Change for Project Success

Ultimately all projects are a change in one way or another. Weather it be for a change in policy, and addition to a company, a new company, or a new system. The Project at the Parc apartments is necessary for the overall revenue of the company. With the apartments not having been updated since the 1970’s makes the apartments vintage yes; however, with the other complexes being more modern and with the trends of what the up and coming market, the parc must implement the changes for the continued success of the apartments.

The project manager, the project team, and the stakeholders need to be accepting of the changes in order for them to make the project a success. The project manager should approach the idea of the changes to the stakeholders with diligence being clear and concise. The changes to the project should have the budget benefits, timeline benefits, and why it would be crucial for the success of the project (Chittoor, 2012). “The key factors which can ensure acceptance are:

 Showing proven data of the results i.e., before and after, so that the comparison becomes easy and lucid.

 By implementing the change in a pilot environment.

 By rewarding appropriately those people who follow the desired processes.

By following a mentor –tutor relationship and not being purely authoritarian”

Chittoor (2012) (p 6).

Conclusion

References

Cobb, A. T. (2012). Leading Project Teams: The Basics of Project Management and Team Leadership (2nd ed.). Retrieved from https://phoenix.vitalsource.com/#/books/9781544302737/cfi/6/8!/4/2/4/2@0:0.Westland, J. (2015, September). 

Suchan, J. (2019). How to Evaluate Project Change Requests. Retrieved from

https://support.microsoft.com/en-us/office/how-to-evaluate-project-change-requests-fc36f2bb-5858-48fa-8fe9-fad4721fff6c