HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2017T1 ISE Change Management"

From IS480
Jump to navigation Jump to search
Line 122: Line 122:
 
| style="text-align:center;width:75px" | Accept
 
| style="text-align:center;width:75px" | Accept
 
| style="text-align:center;width:75px" |Proceeded to move QA coins, marks and vote component in timeline to after acceptance in iteration 9. Shift the my Profile - Telegram Bot function in iteration 9 to 11.
 
| style="text-align:center;width:75px" |Proceeded to move QA coins, marks and vote component in timeline to after acceptance in iteration 9. Shift the my Profile - Telegram Bot function in iteration 9 to 11.
 +
| style="text-align:center;width:75px" | Closed
 +
|-
 +
| style="text-align:center;width:75px" | 02/08/2017
 +
| style="text-align:center;width:75px" | 6
 +
| style="text-align:center;width:75px" | Scope
 +
| style="text-align:center;width:75px" | Change the deployment server to AWS
 +
| style="text-align:center;width:75px" | Team
 +
| style="text-align:center;width:75px" | Users are required to connect VPN in order to access the project deployed on the Linux server. Therefore, team suggested to change the deployment server to AWS for the convenience sake.
 +
| style="text-align:center;width:75px" | Accept
 +
| style="text-align:center;width:75px" |Proceeded to deploy on AWS. PM scheduled and allocated deployment tasks.
 +
| style="text-align:center;width:75px" | Closed
 +
|-
 +
| style="text-align:center;width:75px" | 02/08/2017
 +
| style="text-align:center;width:75px" | 6
 +
| style="text-align:center;width:75px" | Schedule
 +
| style="text-align:center;width:75px" | Change the date of UT1 to 12/08/2017
 +
| style="text-align:center;width:75px" | Sponsor
 +
| style="text-align:center;width:75px" |Sponsor suggested to change the date of UT1 from  05 August to 12 August so that team has sufficient time for project deployment.
 +
| style="text-align:center;width:75px" | Accept
 +
| style="text-align:center;width:75px" | Proceeded with the development of integration between forum and CAT bot.
 
| style="text-align:center;width:75px" | Closed
 
| style="text-align:center;width:75px" | Closed
 
|-
 
|-

Revision as of 13:50, 6 August 2017

ISE.PNG

HOME

 

ABOUT US

 

PROJECT OVERVIEW

 

PROJECT MANAGEMENT

 

DOCUMENTATION

 

 

ISE Change Management Process.png



Date Iteration Type Change RequestedBy Description Decision ActionTaken Status
20/06/2017 3 Scope Prioritize the development of Discussion Forum. Replace request form and preset question function with post class summary. Add QA coins, marks and vote component in the discussion forum Sponsor Sponsor suggested to change request form and preset questions functions to post class summary. This is done to not affect the current teaching style of existing professors, and dilute away the in class interaction. Sponsor wants to prioritize the developement of discussion forum and the addition of QA coins, marks and vote component to discussion forum. By doing so, it can promotes post-class forum discussion. Accept PM reschedule the project timeline and project scope. Remove Request Form in iteration 4, and remove Preset Questions in iteration 5. Shift the schedule of Discussion Forums from iteration 9 to iteration 4. Add Discussion Forums QA coins, marks and vote component to iteration 5. Add Post Class Summary to iteration 7. Closed
20/06/2017 3 Scope Register function included to have the option of registering into our system portal without relying on IITS Login Team Team suggested to add register function of student account to telegram bot to link account ID and telegram ID. Accept PM reschedule the project timeline and project scope. Add Register Function in iteration 5. Register function will be created in telegram bot to allow students to register their user details before having access to the telegram bot. Closed
01/07/2017 3 Team Leaving of the sixth member Team Letting go of an existing team member to consolidate tasks and achieve better work efficiency. Accept PM reschedule the team roles, and assign Alvin the role of lead Front End Developer. Business Analyst tasks is reassigned to other team members. Closed
11/07/2017 4 Scope Remove QA coin component as it exceeded our original work scope and technical breath Team Remove QA coin and marks component from discussion forum because the size of change exceeded our current resources. Reject Discussion with sponsor led to QA coin component being continued. Suggest good to have Quiz function will be dropped to avoid affecting project completion. Closed
15/07/2017 4 Scope Suggest drop good to have function of Quiz functionality Team To continue with QA coin function completion, good to have function will be dropped to enable team to focus efforts to complete QA coin on discussion forums. This is because the functionality on discussion forums is prioritized for completion by our sponsor. Accept Proceeded to drop good to have function Quiz functionality from project scope and timeline. Closed
15/07/2017 4 Scope QA Coin component in Discussion Forums will be pushed after acceptance Team Owing to the scope of QA Coin component in Discussion Forums, the date of completion for the functionality will be pushed after Acceptance. This is done to ensure sufficient time and resources are allocated for completion of the functionality. Accept Proceeded to move QA coins, marks and vote component in timeline to after acceptance in iteration 9. Shift the my Profile - Telegram Bot function in iteration 9 to 11. Closed
02/08/2017 6 Scope Change the deployment server to AWS Team Users are required to connect VPN in order to access the project deployed on the Linux server. Therefore, team suggested to change the deployment server to AWS for the convenience sake. Accept Proceeded to deploy on AWS. PM scheduled and allocated deployment tasks. Closed
02/08/2017 6 Schedule Change the date of UT1 to 12/08/2017 Sponsor Sponsor suggested to change the date of UT1 from 05 August to 12 August so that team has sufficient time for project deployment. Accept Proceeded with the development of integration between forum and CAT bot. Closed