Page 264 - Project+
P. 264

manager, the project, and the organization at risk. Another key reason for updating the

     project documents is so that you have an accurate record of the project and can use
     these documents as a starting point on future projects that are similar in nature. You’ll
     also use these documents at the conclusion of the project when you’re performing
     lessons-learned exercises.

     Make certain to practice version control when updating project documents. This way,
     you’ll know that you are always working with the latest document. For example, if the
     schedule has undergone a change previously and now a new request is submitted that

     will impact the schedule, you’ll want to make certain you are updating the latest
     version of the schedule. Many project management software programs and document
     repository programs will automatically perform version control for you. If your
     organization has not implemented this feature, you can accomplish version control in a
     couple of ways. Include the version number in your document name, such as

     “Schedule_v1,” or the date and time, “Schedule_2018-02-16.”


     Communicating the Changes

     A component of your change process should include a communication plan. Changes
     should be communicated to the sponsor, stakeholders, and project team members.
     This can be accomplished in several ways, and one of the most effective is at the project
     status meeting.

     Project status meetings are generally kicked off during the Executing phase to keep

     stakeholders apprised of progress. Change requests should be a regular agenda item at
     these meetings. The change request log should also be reviewed to discuss changes that
     were implemented during the last reporting period and those scheduled for
     implementation in the next period.



     Types of Organizational Change


     Scope, schedule, and cost are not the only changes that may impact the project.
     Organizational changes can have a significant impact on the project. Let’s take a look at
     some of the organizational changes outlined in the CompTIA Project+ exam objectives.

     Business Merger/Acquisition Changes that come in the form of mergers or
     acquisitions can lead to project changes or sometimes project cancelations. For the
     exam, it’s important to understand the difference between a merger and an

     acquisition. A merger is when two businesses come together to perform business as
     one organization. Once the merger is complete, they are one entity. An acquisition is
     when one business takes over another. The organization performing the takeover has
     the power and authority and becomes the decision maker for both organizations.
     Mergers or acquisitions could change the overall objectives and goals of the project.

     Business Demerger/Split A demerger or split is the opposite of a merger or

     acquisition. The organizations that merged or were acquired decide to break into



                                                            264
   259   260   261   262   263   264   265   266   267   268   269