HeaderSIS.jpg

IS480 Team wiki: 2016T2 LickiLicky Change Management

From IS480
Jump to navigation Jump to search

LickiLicky Logo v2.png

HOME   ABOUT US   PROJECT OVERVIEW   PROJECT MANAGEMENT   DOCUMENTATION
Project Timeline Metrics Risks Change Management


Change Management



Steps for Change Management

1. Receive change request
2. Analyze feasibility of change request
3. Evaluate the level of impact on project if change request is implemented
4. Decide the level of priority for the change request
5. Accept or reject the change request

Priority of Change Request Outcome
Reject Change is rejected. Inform requester (Eg: mentor, supervisor, others) .
Low Add to Tertiary / Good to Have function.
Medium Discuss with mentor / supervisor to rescope the project by replacing current functions to accept change.
High Hold internal meeting to discuss functional requirement. Immediately update in project schedule. PM to reschedule tasks.


Change Log

Iteration Date Description Reason Feasibility Priority Outcome Status
3 23 Oct Added “Voice to Text” function to iteration 11 and “Cloud Backup” to iteration 13. In return, “Access Control – Freemium and Premium” is removed from iteration 13. Change implemented as both mentor and supervisor advised us that these functions may be more important to users because “Voice to Text” brings more immediate convenience to users while “Cloud Backup” offers peace of mind in the long-term which is not obvious when we demonstrate to users. Business Analyst concluded that “Access Control” may be of lesser importance as compared to these 2 functions. Project Manager concluded that “Cloud Backup” should replace “Access Control”, instead of building them concurrently, because time needs to be allocated to build on midterm feedback on top of development. High Accepted Completed
4 30 Oct Added Deployment to iteration 10. Deployment will serve as an update to the app and also, adding more interesting features. This will help us to achieve our X Factor. Fits into schedule without any expected delay as a consequence. High Accepted Completed
4 30 Oct Added UAT to iteration 14. User Test was not scheduled for functions developed after midterm. Fits into schedule without any expected delay as a consequence. High Accepted Completed
4 06 Nov Change name from "Auto Group" to "Suggest Group". “Auto group” is misleading as groups are not automatically group (requires confirmation by users) and thus we will refer to the feature as “Suggest group” instead. Fits into schedule without any expected delay as a consequence. Low Accepted Completed
4 06 Nov Move mid-term UT forward. More testing as advised by Prof. Ben Gan and Supervisor Prof. Chris Boesch. Fits into schedule without any expected delay as a consequence. High Accepted Completed
4 06 Nov Added prototyping tasks for more complex features As advised by Prof. Ben Gan for new and complex features such as business card scanning and voice to text. By doing so, we will be able to make changes to the function and design of it at lower cost. Fits into schedule without any expected delay as a consequence. High Accepted Completed
4 06 Nov Start ahead for building multi-platform UI We revise our expectations for catering to different Android devices and concluded that we should bring forward the task to lower the risk of not being able to run sufficient types of devices before Mid-Term. Fits into schedule without any expected delay as a consequence. Medium Accepted Completed
7 08 Dec GPS notes done in MPT, replace with “Google Analytics to determine active users” Function for location field ot be populated with user creates a note is completed in MPT course. Google Analytics is critical to measure our x-factor and thus is included. Fits into schedule without any expected delay as a consequence. High Accepted Completed
7 08 Dec Suggest to have "Group as you type" feature to allow users to group users quickly By making it easy to group contacts, birthday reminders and keep in touch settings can be implemented accurately on groups of contacts. Do not have strong evidence that it will be useful to replace a feature in our current scope. Low Rejected N/A
7 09 Dec Swap Google Analytics with import from social media for Iteration 7. The latter will be scheduled on Iteration 8. Team decided that Google Analytics is more critical than import from social media for the coming User Test. Fits into schedule without any expected delay as a consequence. High Accepted Completed
7 16 Dec Added "Birthday Reminders" to scope as part of Reminders Module. This will be a secondary function BA determine that this will be a useful function for users, after interviewing several Financial Consultants Fits into schedule without any expected delay as a consequence. High Accepted Completed
7 16 Dec Revised scope under "Note-Taking Module". Only CRUD Notes will remain as a function under this module. Other than CRUD Notes, the other note-taking related functions are not developed as part of IS480 scope. Fits into schedule without any expected delay as a consequence. High Accepted Completed
7 16 Dec "Monetary Module" is classified as "Good to Have Functions" BA determine that "Free / Premium Access Control" should not be the main focus of IS480. Fits into schedule without any expected delay as a consequence. High Accepted Completed
8 22 Dec User Test 2 rescheduled to be from 4 Jan 2016 to 10 Jan 2016 instead of the original 28 Dec 2015 to 1 Jan 2015. Testers recruited (consisting of full time Financial Consultants) feedback that the original date for testing is not the best period for them to fully utilise the application due to festive season. Most of them will not be working and some of the Financial Consultants that the team tried to recruit as testers mentioned that they will be overseas and thus, unable to participate. The team decided to reschedule the User Test in order to achieve more meaningful findings. PM had rescheduled this User Test and it fits into iteration 9 schedule. Fits into schedule without any expected delay as a consequence. High Accepted Completed
8 30 Dec User Test 2 further rescheduled to be from 6 Jan 2016 to 12 Jan 2016 We will be conducting User Test within SMU and decide to use 2 days (4 Jan to 5 Jan 2016) to recruit participants. Recruitment email will be send out during the 2 days period and time is needed to be catered for response. Fits into schedule without any expected delay as a consequence. High Accepted Completed
8 30 Dec Import from Social Media is dropped from scope BA determine that this is not a function that will be very useful due to the increased levels of privacy of major social platforms like Facebook & LinkedIn and thus, it is dropped from the IS480 scope. Fits into schedule without any expected delay as a consequence. High Accepted Completed
8 5 Jan Reshuffling of tasks: Attached Media to Notes shifted from Iter 10 to Iter 9. OTP Login and OTP Registration shifted from Iter 9 to Iter 13. OTP Login / Registration is shifted to be developed in the same iteration as the development for cloud backup. In turn, we can start developing Attach Media to Notes, a feature we considered more interesting for User Test 3. Fits into schedule without any expected delay as a consequence. High Accepted Completed
8 5 Jan Change of date for User Test 3 from 10 Jan 2016 to 11 Jan 2016 Having learnt from the experience of User Test 2, PM decides this change in lieu of Chinese New Year Break (8 to 9 Jan). An extra day will allow us to recruit more testers from school and also, increase the possibility of recruiting more Financial Consultant testers, who may be away from work on the original date (10 Jan). Fits into schedule without any expected delay as a consequence. High Accepted Completed
9 13 Jan Added Calendar function to scope as a secondary function Mentor suggested that having Calendar will be a useful feature for users. PM scheduled the task on Iteration 10. Fits into schedule without any expected delay as a consequence. High Accepted Completed
9 13 Jan OTP Registration / Login shifted to Good to Have functions OTP features will be remove from Iteration 13. BA determined that this function will be of lesser importance during IS480. Fits into schedule without any expected delay as a consequence. High Accepted Completed
9 18 Jan Added Best Time to Call as a tertiary function Supervisor suggested that the app can be "smarter" with some back end analytic for several meeting. During supervisor meeting, the "Best Time to Call" feature was discussed with supervisor and based on feedback given, team decided to add this function to the scope. PM scheduled the task to be on iteration 14. Fits into schedule without any expected delay as a consequence. High Accepted Completed
10 26 Jan CRUD Group Notes, CRUD Group Reminders, and Auto-Creation of first note is remove from scope Removed from scope as development of these functions are not part of IS480. Fits into schedule without any expected delay as a consequence. High Accepted Completed
10 2 Feb Data Migration. Tutorial. Added to scope These 2 functions will be added to scope and develop during Iteration 11. Data migration will ensure that user's data are back-up. In UT2, many testers feedback that a tutorial will be useful. These will be done prior to UT3 (11 Feb). Fits into schedule without any expected delay as a consequence. High Accepted Completed
12 22 Feb Swap Best Time to Call with Visualization of Statistics for Iteration 14. Best Time to Call will be shifted to Good to Have while Visualization of Statistics will be shifted back to Tertiary Function. UT3 result shows that Visualization of Statistic has better rating than Best Time to Call. Fits into schedule without any expected delay as a consequence. High Accepted Completed
13 8 Mar Drop remaining functions to be developed for Iteration 13 (Cloud Backup) and Iteration 14 (Visualisation of Statistics) Criteria to develop functions should be first validated against market needs. Supervisor, Prof Chris, advised team to conduct more User Testing to learn about market needs instead of developing functions without any market validation. PM scheduled UT 4 and UT 5 for Iteration 13 and 14 respectively instead of developing new functions to current app. UT will be conducted with actual users (Financial Consultants). Fits into schedule without any expected delay as a consequence. High Accepted Completed
14 22 Mar Suggest to transit from Google Places Webservice API to Android API Currently New Note location is populated by sending GPS data to Google Places Webservice API requesting a location of type=establishment. The establishment type will be deprecated on Feb 16, 2017. By transiting from Webservice API to Android API, it also enables other features such as typeahead for location. Changing of codes and API calls does not require high effort. However, the team sees that this change could be delayed beyond FYP scope as there is still 11 months before API is deprecated. Furthermore, there is no evidence that it will help in achieving the FYP X-Factors by finals. Medium Rejected N/A
15 8 April Suggest Group (Related Field) is shifted to Good to Have Function was developed in Iteration 3 and prior to midterm, UT2 and UT3 results show that this function is not highly rated by financial consultants. Therefore, this function will not be part of a core function in Tictacts. Fits into schedule without any expected delay as a consequence. High Accepted Completed