Difference between revisions of "IS480 Team wiki: 2016T2 Friendchise Change Management"
Jump to navigation
Jump to search
Line 56: | Line 56: | ||
<br> | <br> | ||
==<div style="background: #2E2E2E; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size: 22px"><font color=#FFFFF>Steps for Change Management</font></div>== | ==<div style="background: #2E2E2E; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size: 22px"><font color=#FFFFF>Steps for Change Management</font></div>== | ||
+ | |||
+ | The team will adopt the following approach when there is a change request: <br> | ||
+ | [[File:ChangeManagementProcess.JPG|800px|frameless|center]] | ||
+ | <br> | ||
+ | |||
1. Receive change request<br> | 1. Receive change request<br> | ||
2. Analyze feasibility of change request<br> | 2. Analyze feasibility of change request<br> |
Revision as of 18:40, 4 February 2016
Steps for Change Management
The team will adopt the following approach when there is a change request:
1. Receive change request
2. Analyze feasibility of change request
3. Evaluate the level of impact on project if change request is implemented
4. Decide the level of priority for the change request
5. Accept or reject the change request
Priority Value | Priority of Change Request | Outcome |
---|---|---|
0 | Reject | Change is rejected. Inform sponsor. |
1 | Low | Add to tertiary function. |
2 | Medium | Discuss with sponsor to rescope the project by replacing current functions to accept change. |
3 | High | Immediately update in project schedule. PM to reschedule tasks. |