Difference between revisions of "IS480 Team wiki: 2017T2 Bunanas Change Management"
Jump to navigation
Jump to search
(8 intermediate revisions by the same user not shown) | |||
Line 51: | Line 51: | ||
<!--Buttons--> | <!--Buttons--> | ||
− | <span class="mw-ui-button {{#switch: {{{color| | + | <center> |
+ | <span class="mw-ui-button {{#switch: {{{color|green}}} | red = mw-ui-destructive | green = mw-ui-constructive | white = | blue = mw-ui-progressive}}"> | ||
+ | [[IS480_Team_wiki: 2017T2 Bunanas Change Management|{{{Clickable Button|Changelog}}}]]</span> | ||
+ | <span class="mw-ui-button {{#switch: {{{color|white}}} | red = mw-ui-destructive | green = mw-ui-constructive | white = | blue = mw-ui-progressive}}"> | ||
[[IS480_Team_wiki: 2017T2 Bunanas Change Management Process Model|{{{Clickable Button|Change Process Model}}}]]</span><noinclude> | [[IS480_Team_wiki: 2017T2 Bunanas Change Management Process Model|{{{Clickable Button|Change Process Model}}}]]</span><noinclude> | ||
+ | </center> | ||
<!--Buttons End--> | <!--Buttons End--> | ||
+ | |||
+ | <!-- | ||
+ | <br> | ||
+ | </div> | ||
+ | <center> | ||
+ | {| class="wikitable" style="font-family:Century Gothic; background-color:#FFFFFF; width: 1200px;" align="center" | ||
+ | |- | ||
+ | ! style="color:#ffffff; background-color:#aeaeae;" width="50pt" | Sprint | ||
+ | ! style="color:#ffffff; background-color:#aeaeae;" width="50pt" | Date | ||
+ | ! style="color:#ffffff; background-color:#aeaeae;" width="50pt" | Type | ||
+ | ! style="color:#ffffff; background-color:#aeaeae;" width="50pt" | Change Description | ||
+ | ! style="color:#ffffff; background-color:#aeaeae;" width="50pt" | Rationale | ||
+ | ! style="color:#ffffff; background-color:#aeaeae;" width="50pt" | Decision | ||
+ | ! style="color:#ffffff; background-color:#aeaeae;" width="50pt" | Action Taken | ||
+ | ! style="color:#ffffff; background-color:#aeaeae;" width="50pt" | Status of Request | ||
+ | |- | ||
+ | |||
+ | |style="text-align: center; background-color:#ffffff;"| 6 | ||
+ | |style="text-align: center; background-color:#ffffff;" | 20 Dec 17 | ||
+ | |style="text-align: center; background-color:#ffffff;" | Functionality | ||
+ | |style="text-align: center; background-color:#ffffff;" | Change QR Code to Barcode | ||
+ | |style="text-align: left; background-color:#ffffff;" | QR Code not scalable. | ||
+ | Barcode exists on all their inventory items. | ||
+ | It matches all of their desired requirements. | ||
+ | |style="text-align: left; background-color:#ffffff;" | Change Approved | ||
+ | |style="text-align: left; background-color:#ffffff;" | Module Changed | ||
+ | |style="text-align: center; background-color:#ffffff;" | Closed | ||
+ | |- | ||
+ | |||
+ | |style="text-align: center; background-color:#ffffff;"| 6 | ||
+ | |style="text-align: center; background-color:#ffffff;" | 24 Dec 17 | ||
+ | |style="text-align: center; background-color:#ffffff;" | Schedule | ||
+ | |style="text-align: center; background-color:#ffffff;" | Moving Disaster Recovery module to earlier date | ||
+ | |style="text-align: left; background-color:#ffffff;" | Need to backup data arise during development of inventory module. | ||
+ | Putting disaster recovery and backup in place before further development allows for more reliable development. | ||
+ | |style="text-align: left; background-color:#ffffff;" | Change Approved | ||
+ | |style="text-align: left; background-color:#ffffff;" | Project Scope & Schedule Amended | ||
+ | |style="text-align: center; background-color:#ffffff;" | Closed | ||
+ | |- | ||
+ | |||
+ | |style="text-align: center; background-color:#ffffff;"| 7 | ||
+ | |style="text-align: center; background-color:#ffffff;" | 4 Jan 18 | ||
+ | |style="text-align: center; background-color:#ffffff;" | App Platform | ||
+ | |style="text-align: center; background-color:#ffffff;" | Creation of Android App | ||
+ | |style="text-align: left; background-color:#ffffff;" | Mobile-optimised web app does not work well for a barcode use case. | ||
+ | Not realistic to use laptop webcam during the inventorising process. | ||
+ | Dedicated Android app will allow use of native camera functionality. | ||
+ | |style="text-align: left; background-color:#ffffff;" | Change Approved | ||
+ | |style="text-align: left; background-color:#ffffff;" | Project Schedule Amended | ||
+ | |style="text-align: center; background-color:#ffffff;" | Closed | ||
+ | |- | ||
+ | |||
+ | |style="text-align: center; background-color:#ffffff;"| 9 | ||
+ | |style="text-align: center; background-color:#ffffff;" | 22 Jan 18 | ||
+ | |style="text-align: center; background-color:#ffffff;" | Schedule | ||
+ | |style="text-align: center; background-color:#ffffff;" | Change User Testing timeframe from standalone major milestones into multiple smaller milestones with higher frequency | ||
+ | |style="text-align: left; background-color:#ffffff;" | The current User Testing plan worked around sponsor's process lifecycle (~2 weeks) which results in less User Testing being conducted. | ||
+ | Multiple activities are conducted within the lifecycle that should be tested and recorded. | ||
+ | It was deemed to be more beneficial to have smaller tests with higher frequency to collect more data points. | ||
+ | |style="text-align: left; background-color:#ffffff;" | Change Approved | ||
+ | |style="text-align: left; background-color:#ffffff;" | Discussions were made with Supervisor and Sponsor. It was decided that it would be better to have more specific names for User Tests (User Test 2: Admin, User Test 2: Beneficiary) and increase the frequency. This shows a better understanding of the stakeholders that are being addressed. | ||
+ | |style="text-align: center; background-color:#ffffff;" | In Progress | ||
+ | |- | ||
+ | |} | ||
+ | </center> | ||
+ | --> | ||
+ | |||
<br> | <br> | ||
[[File:BunanasChangeManagement.png|center]] | [[File:BunanasChangeManagement.png|center]] | ||
− | |||
</div> | </div> |