HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki:2017T2 Zenith Midterm Wiki"

From IS480
Jump to navigation Jump to search
Line 116: Line 116:
 
====Task metric====
 
====Task metric====
 
<div style="font-family: Verdana;">
 
<div style="font-family: Verdana;">
</div>  
+
[[File:Zenith_midterms_task_metric.png|center|600px]]
 +
 
 +
<!--Task Metric Table Start-->
 +
{| class="wikitable" style=" background-color:#FFFFFF; width: 1000px"|+ '''Cells left-aligned, table centered'''
 +
|-
 +
 
 +
! style="color:#ecf0f1; background-color:#404040;" width="50pt" | Score
 +
|style="text-align: center;" width="20%" | TM <= 50
 +
|style="text-align: center;" width="20%" | 50 < TM <= 75
 +
|style="text-align: center;" width="20%" | 75 < TM <= 125
 +
|style="text-align: center;" width="20%" | 125 < TM <= 150
 +
|style="text-align: center;" width="20%" | 150 > TM
 +
|-
 +
 
 +
! style="color:#ecf0f1; background-color:#404040;" | Action
 +
|style="text-align: left;vertical-align: top"| 1. Inform supervisor within 24 hours. <br>  2. Re-estimate tasks for future iterations. <br>  3. Consider dropping Tasks.
 +
|style="text-align: left;vertical-align: top"| 1. Re-estimate tasks for future iterations. <br> 2. Deduct number of days behind from buffer days. <br>  3. If there are no more buffer days, decide the functionalities to drop.
 +
|style="text-align: left;vertical-align: top"| 1. Our estimates are fairly accurate, and are roughly on track. <br> 2. Add/deduct number of days ahead / behind from buffer days.
 +
|style="text-align: left;vertical-align: top"| 1. Re-estimate tasks for future iterations.  <br> 2. Add number of days ahead to buffer days.
 +
|style="text-align: left;vertical-align: top"| 1. Inform supervisor within 24 hours.  <br> 2. Re-estimate tasks for future iterations.
 +
|-
 +
|}
 +
<!--Task Metric Table End-->
 +
</div>
  
 
====Bug metric====
 
====Bug metric====

Revision as of 00:52, 21 February 2018

Zenith banner.png

Home

Team

Project Overview

Project Management

Documentation

Main Wiki

Midterm Wiki Final Wiki


Zenith midterm header.PNG


Project Progress Summary

Midterm Slides

(insert link here)

Deployed site link

Zenith deployment link.jpeg

Project Highlights

Our project schedule is divided into 13 iterations.

  • We are currently on our 9th iteration (12 Feb - 25 Feb 2018).
  • Up till 20 Feb 2018, we have completed 80.56% of our development progress.
  • 1 User Acceptance Test was conducted before Midterms. The results are shown here.
  • Achieved and exceeded Midterms X-factor.


Unexpected events:

  • New team of clients.
  • Cancellation of one User Acceptance Test by clients due to busy schedules.
  • List of requirement changes after Acceptance can be viewed here.

Project Management

Iteration Progress: 9 of 13
Features Completion: 80.56% (29 out of 36 features)
Confidence Level: 100%

Project Status:

A breakdown of tasks is shown in our project scope.


Zenith midterm scope.png


Project Schedule (Plan Vs Actual):

Milestones Overview:

Planned (Acceptance) Actual (Midterms)

Zenith midterm planned timeline.png

Zenith midterm actual timeline.png

Project Schedule:

Planned Schedule (Acceptance)

Zenith midterm expected schedule.png



Changes in planned schedule (Acceptance)

Zenith midterm changed schedule.png



Actual Schedule (Midterms)

Zenith midterm actual schedule.png

Project Metrics:

Task metric

Zenith midterms task metric.png
Score TM <= 50 50 < TM <= 75 75 < TM <= 125 125 < TM <= 150 150 > TM
Action 1. Inform supervisor within 24 hours.
2. Re-estimate tasks for future iterations.
3. Consider dropping Tasks.
1. Re-estimate tasks for future iterations.
2. Deduct number of days behind from buffer days.
3. If there are no more buffer days, decide the functionalities to drop.
1. Our estimates are fairly accurate, and are roughly on track.
2. Add/deduct number of days ahead / behind from buffer days.
1. Re-estimate tasks for future iterations.
2. Add number of days ahead to buffer days.
1. Inform supervisor within 24 hours.
2. Re-estimate tasks for future iterations.

Bug metric


Project Risks:

Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.

Be sure to prioritize the risks.


Technical Complexity:

Natural Language Processing

Natural Language Processing (NLP) was used for the automated marking of open-ended questions.


Game development

Together with the NUS team, we developed a few basic game rules.


Added security features

In December 2017, our MongoDB database was compromised and held hostage by ransomware. We were instructed to pay 0.1 bitcoin (USD $1594) for the return of our data. Fortunately, we had backed up the data so there was no need for us to pay the ransom. Since this incident, we have taken additional measures to ensure that this does not happen again.

Quality of product

Intermediate Deliverables:

Stage Specification
Project Management Schedule
Minutes
Bug metrics
Task metrics
Risk management
Change management
Requirements Overview
Scope
Personas
Analysis Use case diagram
Architecture diagram
Technologies used
Design Prototypes
Testing User Acceptance Test 1 (11 - 13 Feb 2018)

Testing:

  • Creation of test cases during development.
  • Functionality testing after completion of function.
  • Regression testing at the end of every iteration.
  • We expect to complete 2 UATs by the end of the project.
  • 1 UAT has been completed before Midterms. To view the results of this UAT, click here.

Reflections

Team Reflection:

Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.

Individual Reflections:

Amelia:


Chin Rui:


Ervin:


Ming Rui:


Qimin:


Ricky: