Project Management: Monitoring Scope, Schedule, Cost Quality, Communications Professor Akhilesh Bajaj The University of Tulsa ©Akhilesh Bajaj 2013. All Rights reserved

Monitor Scope, Schedule -Get deliverable acceptance and formal sign-off for each deliverable -The scope statement, WBS, requirements documentation and requirements traceability matrix contain the inputs needed. -Need to validate the quality of each deliverable and then have it signed off. -Need to prevent scope creep. If scope changes, more resources need to be allocated. Schedule: -Salaried employees tend to work longer without it showing up as costs.. This can lead to underestimation of resources needed over time. -Scheduling tools keep track of which activities are completed ahead or behind schedule. Activities with slack may be completed behind schedule, while those on the critical path need to be on schedule. -At end of project, an analysis of why activities were behind schedule helps in learning for future projects.

Monitor Cost

Monitoring Quality, Communications Techniques: -Prevention: (look at past experiences) and have a backup -Inspection: Test deliverables qualitatively -Attribute sampling: Use quantitative measures to test -Variable sampling: See what % of target is reached -Control limits: Minimum and maximum criteria for a deliverable. Look at causes of overrun: -Expensive resources, poor estimates, vendor overrun, misinterpretation of scope. Communications: -Look at project variances and communicate to stakeholders along with proposed mitigations.