HeaderSIS.jpg

IS480 Team wiki: 2015T1 4Sight Change Management

From IS480
Jump to navigation Jump to search
4Sight team logo.png
4Sight Home.png HOME   4Sight Team.png ABOUT US   4Sight Project overview.png PROJECT OVERVIEW   4Sight Project management.png PROJECT MANAGEMENT   4Sight Documentation.png DOCUMENTATION  
Project Schedule Software Development Methodologies Schedule Metrics Task Metrics Bug Metrics Risk Management Change Management

Change Management Process

ChangeManagement.jpg
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


Change Request from Sponsor

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 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. 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
3 4 22/7/2015 Separate Clearvision and Mount Elizabeth appointment schedule This would help facilitate viewing of respective clinic's schedule. In addition, it provides greater visibility of appointments of clinics which require collaboration. Add new tabs to separate both views 3 Accept Accepting the request would not affect the project schedule Added a new user story into the backlog. To be scheduled in subsequent sprint. In Progress
4 4 22/7/2015 Audit Trail is not an important feature for the application 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 are not sensitive or confidential information that requires high security, an audit trail is not neccessary. N.A 3 Accept 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. Move audit trail out from administrative module in the secondary function and added it as a standalone module in the tertiary function Completed