Difference between revisions of "IS480 Team wiki: 2015T1 4Sight Change Management"
Jump to navigation
Jump to search
Line 53: | Line 53: | ||
<!--MAIN CONTENT--> | <!--MAIN CONTENT--> | ||
+ | [[File:ChangeManagement.jpg|1000px|center]] | ||
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"> | <div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"> | ||
{| class="wikitable" width="100%" font-family="Roboto Lt" | {| class="wikitable" width="100%" font-family="Roboto Lt" |
Revision as of 10:23, 30 July 2015
HOME | ABOUT US | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Project Schedule | Software Development Methodologies | Schedule Metrics | Bug Metrics | Risk Management | Change Management |
Priority Index | Priority | Priority Description |
---|---|---|
0 | Reject | Inform sponsor reasons for rejection of request |
1 | Low | change requested can be added into tertiary function for future consideration |
2 | Medium | Discuss with sponsor to re-scope the project by reducing current functionalities, in order to cater to the change |
3 | High | Change requested is important and requires immediate attention. PM to schedule task into sprint and make the necessary adjustment to project timeline, if needed |
Sprint | Change Request Date | Change Description | Reason of Change | Change Feasibility | Priority Index | Accept/ Reject | Status |
---|---|---|---|---|---|---|---|
0 | Reject | Inform sponsor reasons for rejection of request | 0 | Reject | Inform sponsor reasons for rejection of request | Reject | Inform sponsor reasons for rejection of request |
1 | Low | change requested can be added into tertiary function for future consideration | 1 | Low | change requested can be added into tertiary function for future consideration | Low | change requested can be added into tertiary function for future consideration |