Laserfiche WebLink
1 <br />• If resolving the Issue will involve changing the scope of the project, close <br />the Issue and use the scope change management procedures instead to <br />manage the resolution. <br />• Document the resolution or course of action on the Issues Form. <br />• Document the Issue resolution briefly on the Issues Log. <br />• Make the appropriate adjustments to the work plan and project budget, if <br />necessary. <br />• If the resolution of an issue causes the budget, effort or duration of the <br />project to change, the current Project Definition should be updated. <br />• Communicate issue status and resolutions to project team members and <br />other appropriate stakeholders through the Manage Communication <br />process, including the Project Status Report. <br />Step 5: Manage Scope <br />• Solicit potential scope change requests from any project stakeholders, <br />Including the project team, clients, replaces, etc. <br />Enter the request into the Scope Change Log. <br />Assign the scope change to a project team member for investigation. The <br />team member will investigate the impact on budget and schedule for <br />various viable options. The team member will first determine how much <br />time it will take to investigate the scope change request. If the time required <br />to perform the analysis will cause deliverable dates to slip, the request <br />must first be taken to the Project Manager to determine whether the <br />request should be investigated or not. If the Project Manager gives the <br />initial approval to proceed, the work plan and budget may need to be <br />updated to reflect this new work. The options are documented on the <br />Scope Change Request Form. If the Project Manager does not agree to <br />investigate the change request, then the request should be placed closed <br />as 'not approved' on the Scope Change Log. <br />(Optional). If the Impact on project cost, effort and duration falls below a <br />threshold (say less than 20 hours) and the project will still be completed <br />within the agreed upon cost, effort and duration, the project manager and <br />client manager may approve the scope change request. This threshold <br />needs to be identified and approved in advance. The purpose is to keep <br />from surfacing many small changes to the Project Manager for approval. <br />See the techniques section for other ways to handle small requests. <br />• Take the scope change request, alternatives and project impact on the <br />Scope Change Request Form to the Project Manager for a resolution. <br />r DIGITAL NETWORKS <br />G• O U I. I N G <br />N <br />a <br />6 <br />0 <br />5 <br />0 <br />8 <br />0 <br />`0 <br />U <br />0 <br />0 <br />www.diglialnetworksgroup.com <br />