Difference between revisions of "IS480 Team wiki: 2015T1 4Sight Change Management"
Jump to navigation
Jump to search
Line 122: | Line 122: | ||
| width=5% align=center | Accept | | width=5% align=center | Accept | ||
| width=20% align=center| Accepting this request would not affect the project schedule.This additional requirement is also a relatively simple module which does not require much time from the team to implement it. | | width=20% align=center| Accepting this request would not affect the project schedule.This additional requirement is also a relatively simple module which does not require much time from the team to implement it. | ||
− | | width=20% align=center | Added a new module | + | | width=20% align=center | Added a new task under the notification module and planned to complete this task in sprint 7 of the project timeline |
| width=5% align=center | In Progress | | width=5% align=center | In Progress | ||
Line 156: | Line 156: | ||
| width=5% align=center | 22/7/2015 | | width=5% align=center | 22/7/2015 | ||
| width=10% align=center | Audit Trail is not an important feature for the application | | width=10% align=center | Audit Trail is not an important feature for the application | ||
− | | width=25% align=center | More priority and emphasis to be placed in the more important features such as the analytics dashboard as well as the calendar to manage appointments. In addition, since the appointment data captured | + | | width=25% align=center | More priority and emphasis to be placed in the more important features such as the analytics dashboard as well as the calendar to manage appointments. In addition, since the appointment data captured is not sensitive or confidential information that requires high security, an audit trail is not neccessary. |
| width=10% align=center| N.A | | width=10% align=center| N.A | ||
| width=3% align=center | 3 | | width=3% align=center | 3 | ||
| width=5% align=center | Accept | | width=5% align=center | Accept | ||
| width=20% align=center| As this feature does not provide much value to Clearvision's current business process, our team have accepted the change request to re-scope project. | | width=20% align=center| As this feature does not provide much value to Clearvision's current business process, our team have accepted the change request to re-scope project. | ||
− | | width=20% align=center | | + | | width=20% align=center | Remove audit trail from project scope and timeline. Check if project timeline needs to be adjusted |
| width=5% align=center | Completed | | width=5% align=center | Completed | ||
+ | |||
+ | |- | ||
+ | | width=3% align=center |5 | ||
+ | | width=3% align=center| 6 | ||
+ | | width=5% align=center | 12/8/2015 | ||
+ | | width=10% align=center | Allow for the edit of patient name and contact in the "edit appointment" form | ||
+ | | width=25% align=center | There are situations in which a patient wants to change their contact number. This happens most often when an appointment is made on behalf of someone (eg: parent booking an appointment for their children). If that is the case, the information captured might not belong to the patient but their parent. To capture patient's data accurately, these fields have to be editable. | ||
+ | | width=10% align=center|Enable patient name and contact number to be editable | ||
+ | | width=3% align=center | 3 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|Accepting the request would not affect the project schedule | ||
+ | | width=20% align=center | Added tasks to fulfill the change request in current sprint | ||
+ | | width=5% align=center | Completed | ||
+ | |||
+ | |- | ||
+ | | width=3% align=center |6 | ||
+ | | width=3% align=center| 6 | ||
+ | | width=5% align=center | 12/8/2015 | ||
+ | | width=10% align=center | Validate for international phone number | ||
+ | | width=25% align=center | Clearvision has patient from abroad. Check if patient number is a valid overseas contact | ||
+ | | width=10% align=center|Add validations for overseas number | ||
+ | | width=3% align=center | 3 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|Accepting the request would not affect the project schedule | ||
+ | | width=20% align=center | Added a new tasks to fulfill the change request in sprint 7 | ||
+ | | width=5% align=center | In Progress | ||
+ | |||
+ | |- | ||
+ | | width=3% align=center |7 | ||
+ | | width=3% align=center| 6 | ||
+ | | width=5% align=center | 12/8/2015 | ||
+ | | width=10% align=center | Block time slots in calendar | ||
+ | | width=25% align=center | Enable the blocking of time slots to prevent Admin Clerk from booking an appointment on time slots/ days when the doctors are on MC/ leave/ at a seminars etc. | ||
+ | | width=10% align=center|Create a form to allow admin clerk to block out time slots | ||
+ | | width=3% align=center | 3 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|Accepting the request would not affect the project schedule | ||
+ | | width=20% align=center | To add a new user story for this change request and to be scheduled in subsequent sprint | ||
+ | | width=5% align=center | In Progress | ||
|} | |} | ||
</div> | </div> |
Revision as of 00:44, 22 August 2015
HOME | ABOUT US | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Project Schedule | Software Development Methodologies | Schedule Metrics | Task Metrics | Bug Metrics | Risk Management | Change Management |
Change Management Process
|
|