CSSE 37214.Oct.2008

Change control and problem escalation

Chapter 10, pages 343-356

OutlineProblem escalationReport level of detailManaging change

Authority principlesAuthority always exists… somewhereA person granted authority as a part of their job

MUST use it, or it will move.

Authority through negotiationPM does not have unilateral authority in the projectPM leads when and what of project activitiesFM determines how support will be givenCreate support with an understanding of CSP

3 levels of escalationProject managerResource managerCustomer

CotD

Overcoming obstaclesWhat is your understanding of the objective?What is your part in delivering this objective?What’s in the way of you doing your part?

And how can I help?

“Nickel/Dime”OpinionPhilosophy

Other techniques

Communication matrix example

Legend

I – As Created/UpdatedM – MonthlyW – WeeklyQ – Quarterly

Managing changeProject change requestProject impact statement

Outcomes of a change request It can be accommodated within the project resources and timelines It can be accommodated but will require an extension of the

deliverable schedule It can be accommodated within the current deliverable schedule,

but additional resources will be needed It can be accommodated, but additional resources and an extension

of the deliverable schedule will be required It can be accommodated with a multiple release strategy and

prioritizing of the deliverables across the release date It cannot be accommodated without a significant change to the

project

Change control process

Change control form

DiscussionHow does change affect the adaptive and extreme

project management approaches?

Questions?