My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
25H - AGMT - AV EQUIPMENT
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2017
>
08/15/2017
>
25H - AGMT - AV EQUIPMENT
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/10/2017 6:43:50 PM
Creation date
8/10/2017 6:38:34 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Parks, Recreation, & Community Services
Item #
25H
Date
8/15/2017
Destruction Year
2022
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
34
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
• 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 />25H-19 <br />DIGITAL NETWORKS <br />G k b ll 4 I N C <br />1. aq+.r .a rnry+. ucr u,x1 .un.. <br />www.digitcilnetworksgroup.com <br />I© <br />
The URL can be used to link to this page
Your browser does not support the video tag.