Difference between revisions of "IS480 Team wiki: 2015T1 4Sight Change Management"
Jump to navigation
Jump to search
(18 intermediate revisions by the same user not shown) | |||
Line 198: | Line 198: | ||
| width=3% align=center | 3 | | width=3% align=center | 3 | ||
| width=5% align=center | Accept | | width=5% align=center | Accept | ||
− | | width=20% align=center| | + | | width=20% align=center|Adjustment needed for project scope and timeline. However, accepting this request would not affect the overall project schedule. Proceed as planned. |
− | | width=20% align=center | To add a new user story and relevant tasks for this change request. To be scheduled in sprint 9 | + | | width=20% align=center | Re-scope the project to include block appointment time slots in the appointment module. To add a new user story and relevant tasks for this change request. To be scheduled in sprint 9. |
− | | width=5% align=center | | + | | width=5% align=center | Completed |
|- | |- | ||
| width=3% align=center |8 | | width=3% align=center |8 | ||
+ | | width=3% align=center| 6 | ||
+ | | width=5% align=center | 12/8/2015 | ||
+ | | width=10% align=center | Remove SMS notification for appointment cancellation | ||
+ | | width=25% align=center | Clearvision prefers to call patients to inform them of last minute cancellation of appointment as they require quick response/ acknowledgement from patients | ||
+ | | width=10% align=center|N.A | ||
+ | | width=3% align=center | 3 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|Sending an SMS might not be efficient as Clearvision requires almost immediate reply from patient. A SMS notification in this case might not be useful especially so when patients are not able to send back a response | ||
+ | | width=20% align=center | Re-scope the project to include the archiving of no show patient records function in the queue management module. PM added new user story and tasks in this current sprint to cater to this new change request. | ||
+ | | width=5% align=center | Completed | ||
+ | |||
+ | |- | ||
+ | | width=3% align=center |9 | ||
| width=3% align=center| 7 | | width=3% align=center| 7 | ||
| width=5% align=center | 28/8/2015 | | width=5% align=center | 28/8/2015 | ||
Line 211: | Line 224: | ||
| width=3% align=center | 3 | | width=3% align=center | 3 | ||
| width=5% align=center | Accept | | width=5% align=center | Accept | ||
− | | width=20% align=center|Accepting | + | | width=20% align=center|This new feature will help ease the workload of the admin clerk as the current process of checking for no show appointment is done manually. Hence,the addition of this feature will greatly improve on the efficiency and accuracy of the business process. Accepting this request would not affect the overall project schedule. |
− | | width=20% align=center | Re-scope the project to include the archiving of no show patient records function. PM added new tasks in this current sprint to cater to this new change request. | + | | width=20% align=center |Re-scope the project to include the archiving of no show patient records function in the queue management module. PM added new user story and tasks in this current sprint to cater to this new change request. |
+ | | width=5% align=center | Completed | ||
+ | |||
+ | |- | ||
+ | | width=3% align=center |10 | ||
+ | | width=3% align=center| 7 | ||
+ | | width=5% align=center | 28/8/2015 | ||
+ | | width=10% align=center | Remove survey results analysis dashboard | ||
+ | | width=25% align=center | Clearvision suggested to remove this feature due to the high risk and cost associated to having to change the codes each time an amendment is made to the survey questions (remove/edit or add a question). A wrong changed made to the codes might caused the survey results dashboard to crash. Hence, they would prefer to manage it separately and do their own visualization. Moreover we are using google form to do up the survey results and google does provide some basic analytics features that will be sufficient for Clearvision. | ||
+ | | width=10% align=center|N.A | ||
+ | | width=3% align=center | 3 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|As this feature might give Clearvision more problem/issue than helping them to improve on their curent business process, we have decided to accept the change request and only help push out survey links to patients. | ||
+ | | width=20% align=center | Re-scope the project to account for the removal of survey results dashboard feature in analytics module and remove it from project schedule timeline | ||
| width=5% align=center | Completed | | width=5% align=center | Completed | ||
|- | |- | ||
− | | width=3% align=center | | + | | width=3% align=center |11 |
| width=3% align=center| 7 | | width=3% align=center| 7 | ||
| width=5% align=center | 28/8/2015 | | width=5% align=center | 28/8/2015 | ||
Line 226: | Line 252: | ||
| width=20% align=center|Accepting the request would not affect the project schedule | | 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=20% align=center | To add a new user story for this change request and to be scheduled in subsequent sprint | ||
− | | width=5% align=center | | + | | width=5% align=center | Completed |
+ | |||
+ | |- | ||
+ | | width=3% align=center |12 | ||
+ | | width=3% align=center| 7 | ||
+ | | width=5% align=center | 28/8/2015 | ||
+ | | width=10% align=center | Remove SMS notification for appointment cancellation | ||
+ | | width=25% align=center | Clearvision prefers to call patients to inform them of last minute cancellation of appointment as they require quick response/ acknowledgement from patients | ||
+ | | width=10% align=center|N.A | ||
+ | | width=3% align=center | 3 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|Sending an SMS might not be efficient as Clearvision requires almost immediate reply from patient. A SMS notification in this case might not be useful especially so when patients are not able to send back a response | ||
+ | | width=20% align=center | Re-scope the project to include the archiving of no show patient records function in the queue management module. PM added new user story and tasks in this current sprint to cater to this new change request. | ||
+ | | width=5% align=center | Completed | ||
|- | |- | ||
− | | width=3% align=center | | + | | width=3% align=center |13 |
| width=3% align=center| 8 | | width=3% align=center| 8 | ||
| width=5% align=center | 16/9/2015 | | width=5% align=center | 16/9/2015 | ||
Line 239: | Line 278: | ||
| width=20% align=center|Accepting this request would not affect the project schedule. Proceed as planned. | | width=20% align=center|Accepting this request would not affect the project schedule. Proceed as planned. | ||
| width=20% align=center |Add a new task to remove datepicker from custom filter | | width=20% align=center |Add a new task to remove datepicker from custom filter | ||
− | | width=5% align=center | | + | | width=5% align=center | Completed |
|- | |- | ||
− | | width=3% align=center | | + | | width=3% align=center |14 |
| width=3% align=center| 8 | | width=3% align=center| 8 | ||
| width=5% align=center | 16/9/2015 | | width=5% align=center | 16/9/2015 | ||
Line 252: | Line 291: | ||
| width=20% align=center|Accepting this request would not affect the project schedule. Proceed as planned. | | width=20% align=center|Accepting this request would not affect the project schedule. Proceed as planned. | ||
| width=20% align=center |Add a new task to remove pending appointments from appointment scheduling dashboard | | width=20% align=center |Add a new task to remove pending appointments from appointment scheduling dashboard | ||
− | | width=5% align=center | | + | | width=5% align=center | Completed |
|- | |- | ||
− | | width=3% align=center | | + | | width=3% align=center |15 |
| width=3% align=center| 8 | | width=3% align=center| 8 | ||
| width=5% align=center | 16/9/2015 | | width=5% align=center | 16/9/2015 | ||
Line 264: | Line 303: | ||
| width=5% align=center | Accept | | width=5% align=center | Accept | ||
| width=20% align=center|Accepting this request would not affect the project schedule. Proceed as planned. | | width=20% align=center|Accepting this request would not affect the project schedule. Proceed as planned. | ||
− | | width=20% align=center |Add a new user story and relevant tasks in subsequent sprint | + | | width=20% align=center |Add a new user story and relevant tasks in subsequent sprint. This new change request is part of the marketing analysis dashboard in analytics module. Hence no change is required for project scope and timeline |
− | | width=5% align=center | | + | | width=5% align=center | Completed |
+ | |||
+ | |- | ||
+ | | width=3% align=center |16 | ||
+ | | width=3% align=center| 8 | ||
+ | | width=5% align=center | 16/9/2015 | ||
+ | | width=10% align=center |Remove dashboard summary | ||
+ | | width=25% align=center | Marketing team does not need a summary dashboard page as the current dashboards (Appointment scheduling, survey results, ROI and conversion) are sufficient. They are more interested in doing in-depth analysis than having an overview of all dashboards. Doctor will not be viewing the summary dashboard as marketing team will prepare a detailed report at the end of every month | ||
+ | | width=10% align=center|N.A | ||
+ | | width=3% align=center | 3 | ||
+ | | 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 felt that the development cost is too high since Clearvision might not use it often. Hence, our team have accepted the change request to remove this feature and re-scope project. | ||
+ | | width=20% align=center |Removed summary dashboard of Analytics Module from project scope and timeline. | ||
+ | | width=5% align=center | Completed | ||
|- | |- | ||
− | | width=3% align=center | | + | | width=3% align=center |17 |
| width=3% align=center| 9 | | width=3% align=center| 9 | ||
| width=5% align=center | 24/9/2015 | | width=5% align=center | 24/9/2015 | ||
Line 278: | Line 330: | ||
| width=20% align=center|Accepting this request would not affect the project schedule. Proceed as planned. | | width=20% align=center|Accepting this request would not affect the project schedule. Proceed as planned. | ||
| width=20% align=center |Delay in deployment due to change request. Deployment is set on 28 Sep 2015 instead of 25 Sep 2015 | | width=20% align=center |Delay in deployment due to change request. Deployment is set on 28 Sep 2015 instead of 25 Sep 2015 | ||
− | | width=5% align=center | In | + | | width=5% align=center | Completed |
+ | |||
+ | |- | ||
+ | | width=3% align=center |18 | ||
+ | | width=3% align=center| 10 | ||
+ | | width=5% align=center | 10/10/2015 | ||
+ | | width=10% align=center |Periodic appointment backup | ||
+ | | width=25% align=center |The client requested for all appointments to be backup on a periodic basis. This is to ensure that no data is lost when the application crashes or in worst case scenario, when the database is wiped out. A backup is like a safety net for the clinic so that business will not be affected and operates as per normal in such events. | ||
+ | | width=10% align=center|Setting up of SMPT server to send out emails periodically | ||
+ | | width=3% align=center | 2 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|Accepting this request would affect the project schedule. However, the sponsor confirmed that this feature is of utmost importance compared to the scaling module (see change request 19). Hence, the team has made the necessary changes to ensure that the project schedule will not be affected with the addition of this feature. | ||
+ | | width=20% align=center |Re-scoped project scope and re-scheduled project schedule. Periodic appointment backup is added as a sub module of admin module and scheduled to be completed in Sprint 11 | ||
+ | | width=5% align=center | Completed | ||
+ | |||
+ | |- | ||
+ | | width=3% align=center |19 | ||
+ | | width=3% align=center| 10 | ||
+ | | width=5% align=center | 10/10/2015 | ||
+ | | width=10% align=center |Remove mobile calendar module | ||
+ | | width=25% align=center | Good to have feature that is of no importance to the client. The chances of doctors using this feature is very slim. Hence, the development cost in implementing this feature will outweigh the value to the sponsor. As such, we have decided to drop this feature and focus on other change requests. | ||
+ | | width=10% align=center|Nil | ||
+ | | width=3% align=center | 3 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|Accepting this request would not affect the project schedule. Proceed as planned. | ||
+ | | width=20% align=center |Removed mobile calendar module from project timeline and scope | ||
+ | | width=5% align=center | Completed | ||
+ | |||
+ | |- | ||
+ | | width=3% align=center |20 | ||
+ | | width=3% align=center| 11 | ||
+ | | width=5% align=center | 24/10/2015 | ||
+ | | width=10% align=center |Remove clinic expansion sub module from admin module | ||
+ | | width=25% align=center |Client pointed out that there is no crucial need for a scaling module and it is unlikely that they will ever use it. In addition, client prefers that we focus on improving and enhancing on the current features based on users' feedback. | ||
+ | | width=10% align=center|Nil | ||
+ | | width=3% align=center | 3 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|Accepting this request will not affect the project schedule. Proceed as planned. Removing this module will save the team 2 weeks worth of development costs which can be used to make the application more intelligent and user friendly through continuous enhancement. | ||
+ | | width=20% align=center |Removed clinic expansion sub module from project timeline and scope | ||
+ | | width=5% align=center | Completed | ||
+ | |||
+ | |- | ||
+ | | width=3% align=center |21 | ||
+ | | width=3% align=center| 11 | ||
+ | | width=5% align=center | 24/10/2015 | ||
+ | | width=10% align=center |Forecast appointment slots availability based on historical data | ||
+ | | width=25% align=center |In our discussion on how to make the application more intelligent, our team proposed to improve on the existing suggestion of appointment time slot feature. Instead of just listing the next earliest available time slot, we suggested to do a forecast of appointment time slots availability based on historical data (previous months appointment schedule). This means that the availability of a particular time slot is not based on the existing number of patients in that time slot (heatmap visualization) but are inferred based on historical data of appointments that were previously scheduled on the same day, time, appointment type and doctor. | ||
+ | | width=10% align=center|Change the logic of existing suggestion of appointment time slot feature | ||
+ | | width=3% align=center | 3 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|Accepting this request will not affect the project schedule. Team will be using the 2 weeks development cost saved as mentioned in change request 20. | ||
+ | | width=20% align=center |No change to project scope. Slight modication of project schedule to include the enhancement of suggestion of appointment time slot feature. | ||
+ | | width=5% align=center | Completed | ||
+ | |||
+ | |- | ||
+ | | width=3% align=center |22 | ||
+ | | width=3% align=center| 11 | ||
+ | | width=5% align=center | 24/10/2015 | ||
+ | | width=10% align=center |Tracking of KPI | ||
+ | | width=25% align=center |Client mentioned that the tracking of monthly KPI will be useful in helping them to evaluate on the effectiveness of the marketing campaigns. This ties in with the existing conversion rates we have in our current analytics module in which users are able to track the number of conversions(surgery) for each marketing channels. | ||
+ | | width=10% align=center|Visual representations and simple manipulation of data | ||
+ | | width=3% align=center | 3 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|Accepting this request will not affect the project schedule. Team will be using the 2 weeks development cost saved as mentioned in change request 20. | ||
+ | | width=20% align=center |Added feature to project scope and timeline | ||
+ | | width=5% align=center | Completed | ||
+ | |||
+ | |- | ||
+ | | width=3% align=center |23 | ||
+ | | width=3% align=center| 11 | ||
+ | | width=5% align=center | 24/10/2015 | ||
+ | | width=10% align=center |Forecast conversions based on number of pre-evaluations scheduled | ||
+ | | width=25% align=center |Client suggested to do a forecast on the number of surgeries they can anticipate for the current month and upcoming months based on the number of scheduled pre-evaluations. With this forecasted value, users can take the neccessary action such as investing more on marketing campigns to attract more patients when forecasted number of surgeries is low (vice versa). This figure will also be a good gauge in determining if a particular month's KPI can be achieved or not. | ||
+ | | width=10% align=center|Visual representations and simple manipulation of data | ||
+ | | width=3% align=center | 3 | ||
+ | | width=5% align=center | Accept | ||
+ | | width=20% align=center|Accepting this request will not affect the project schedule. Team will be using the 2 weeks development cost saved as mentioned in change request 20. | ||
+ | | width=20% align=center |Added feature to project scope and timeline | ||
+ | | width=5% align=center | Completed | ||
+ | |||
|} | |} | ||
</div> | </div> |
Latest revision as of 20:37, 27 November 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
|
|