HeaderSIS.jpg

Difference between revisions of "J.A.R.V.I.S Risk & ChangeManagement"

From IS480
Jump to: navigation, search
 
Line 46: Line 46:
 
[[File:JARVIS_RiskManagement.png|1000px|center]]
 
[[File:JARVIS_RiskManagement.png|1000px|center]]
 
[[File:JARVIS_RiskManagement1.png|1000px|center]]
 
[[File:JARVIS_RiskManagement1.png|1000px|center]]
 +
 +
<br>
 +
<div>
 +
<h1>Change Log</h1>
 +
{| class="wikitable" | style="padding:20px;"
 +
|-
 +
! S/N !! Sprint !! Type !! Change Request !! Rationale !! Impact !! Decision !! Priority !! Action Taken !! Status of Request
 +
 +
|-
 +
| 1. || 2 ||Project Requirements: Removal of Good-to-Have functions || Removal of Good-to-have functions from the project scope as they are non-crucial and have not been committed. || Sponsor explained that the features are good-to-have and are not crucial. The team feels that the scope of the project would be too big if the functions are added and agreed with the sponsor to focus our efforts on the primary, secondary and tertiary functions which are crucial. || Low || Accepted || Low || PM communicated with our client to discuss and confirm the removal of the good-to-have functions and focused our resources on the primary, secondary and tertiary features. || <span style="color:#ff0000">Closed</span>
 +
|-
 +
| 2. || 2 || UI/UX || Requested for student page to use a white background with black/dark words instead of a dark background. || Sponsor explained that a clean background is preferred for readability. The team discussed and agreed that a white background with dark words give a cleaner look and feel to the entire presentation. || Medium || Accepted || High || PM schedules additional tasks for development team to make the changes to the colours used in design in the next sprint. || <span style="color:#ff0000">Closed</span>
 +
|-
 +
| 3. || 4 || Project Requirements: Account Module (Student) || Requested for students to register for an account before accessing the page through token based authentication || The token based authentication is for added security as the data given by students can be confidential and thus a token based authentication is agreed by the team and the client. || Medium || Accepted || Medium || PM schedules additional tasks for development team to include this feature in the next sprint. || <span style="color:#ff0000">Closed</span>
 +
|}
 +
</div>

Latest revision as of 21:28, 11 September 2019

J.A.R.V.I.S TeamLogo.png

JARVIS Home.png   HOME

JARVIS AboutUs.png   ABOUT US

JARVIS ProjectOverview.png   PROJECT OVERVIEW

JARVIS ProjectManagement.png   PROJECT MANAGEMENT

JARVIS Documentation.png   DOCUMENTATION

Risk & Change Management
JARVIS RiskManagement.png
JARVIS RiskManagement1.png


Change Log

S/N Sprint Type Change Request Rationale Impact Decision Priority Action Taken Status of Request
1. 2 Project Requirements: Removal of Good-to-Have functions Removal of Good-to-have functions from the project scope as they are non-crucial and have not been committed. Sponsor explained that the features are good-to-have and are not crucial. The team feels that the scope of the project would be too big if the functions are added and agreed with the sponsor to focus our efforts on the primary, secondary and tertiary functions which are crucial. Low Accepted Low PM communicated with our client to discuss and confirm the removal of the good-to-have functions and focused our resources on the primary, secondary and tertiary features. Closed
2. 2 UI/UX Requested for student page to use a white background with black/dark words instead of a dark background. Sponsor explained that a clean background is preferred for readability. The team discussed and agreed that a white background with dark words give a cleaner look and feel to the entire presentation. Medium Accepted High PM schedules additional tasks for development team to make the changes to the colours used in design in the next sprint. Closed
3. 4 Project Requirements: Account Module (Student) Requested for students to register for an account before accessing the page through token based authentication The token based authentication is for added security as the data given by students can be confidential and thus a token based authentication is agreed by the team and the client. Medium Accepted Medium PM schedules additional tasks for development team to include this feature in the next sprint. Closed