Difference between revisions of "IS480 Team wiki: 2015T1 4Sight Change Management"
Jump to navigation
Jump to search
Line 113: | Line 113: | ||
|- | |- | ||
− | | style="text-align:center" | | + | | style="text-align:center; width="3%" | 2 |
− | | style="text-align:center" | | + | | style="text-align:center; width="3%" | 4 |
− | | style="text-align:center" | | + | | style="text-align:center; width=3%" | 22/7/2015 |
− | | style="text-align:center" | | + | | style="text-align:center"; width="10%" | Sort calendar items by appointment type followed by time |
− | | style="text-align:center" | | + | | style="text-align:center"; width="20%" | It is easier to see if appointments in a particular time slot are first grouped by their appointment type followed by the time of the appointments. In addition, the admin clerks are recording appointments in this order.Therefore, keeping it the same, would minimize changes in their current process. |
− | | style="text-align:center" | | + | | style="text-align:center"; width="10%" | Simple front-end logic to do the sorting and arranging of appointment types and timings |
− | | style="text-align:center" | | + | | style="text-align:center"; width="3%" | 3 |
− | | style="text-align:center" | | + | | style="text-align:center"; width="3%" | Accept |
− | | style="text-align:center" | | + | | style="text-align:center"; width="20%" | Accepting the request would not affect the project schedule |
− | | style="text-align:center" | | + | | style="text-align:center"; width="20%" | Added a new task into the current sprint to cater to this new request. |
− | | style="text-align:center" | | + | | style="text-align:center"; width="5%" | Completed |
|} | |} | ||
</div> | </div> |
Revision as of 18:13, 1 August 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 |
ID | Sprint | Change Request Date | Change Description | Reason of Change | Change Feasibility | Priority Index | Accept/ Reject | Reason for accepting/ rejecting | Action | Status |
---|---|---|---|---|---|---|---|---|---|---|
1 | 1 | 6/6/2015 | To include a module that can send out online survey form | The clinic wants to gather feedback from patients after their eyecare service. The data collected can also help evaluate the efficiency and effectiveness of their business process as well as marketing channels respectively | To provide a google form link (tentative) | 2 | Accept | Accepting this request would not cause any delay in our project schedule.This additional requirement is also a relatively simple module which does not require much time from the team to implement it | Added a new module named survey module to project scope (secondary function) and planned to complete this module in sprint 8 of the project timeline | In Progress |
2 | 4 | 22/7/2015 | Sort calendar items by appointment type followed by time | It is easier to see if appointments in a particular time slot are first grouped by their appointment type followed by the time of the appointments. In addition, the admin clerks are recording appointments in this order.Therefore, keeping it the same, would minimize changes in their current process. | Simple front-end logic to do the sorting and arranging of appointment types and timings | 3 | Accept | Accepting the request would not affect the project schedule | Added a new task into the current sprint to cater to this new request. | Completed |