Difference between revisions of "IS480 Team wiki: 2015T1 4Sight Change Management"
Jump to navigation
Jump to search
(9 intermediate revisions by the same user not shown) | |||
Line 252: | 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 |
|- | |- | ||
Line 291: | 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 |
|- | |- | ||
Line 304: | Line 304: | ||
| 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. 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=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 |
|- | |- | ||
Line 341: | Line 341: | ||
| width=3% align=center | 2 | | width=3% align=center | 2 | ||
| width=5% align=center | Accept | | 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 | + | | 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=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 |In | + | | 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
|
|