HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T1 Hexa Midterm Wiki"

From IS480
Jump to navigation Jump to search
Line 82: Line 82:
 
===Project Status:===
 
===Project Status:===
  
[[File:2015T1 TEAMHEXA Project Status MIDTERMS.png|700px|frameless|center]]
+
[[File:2015T1 TEAMHEXA Project Status MIDTERMS.png|800px|frameless|center]]
  
 
===Project Schedule (Plan Vs Actual):===
 
===Project Schedule (Plan Vs Actual):===

Revision as of 09:47, 6 October 2015

Cheng logo.png

HOME   ABOUT US   PROJECT OVERVIEW   PROJECT MANAGEMENT   DOCUMENTATION
Main Wiki Midterm Wiki Final Wiki

Project Progress Summary

View our deployed I-Wealth Web Application here
View our midterms presentation slides here!

Project Proposal
To understand more about our scope of, click here to read about our project description!

Current Iteration 9: 21 Sept 2015 to 9 Oct 2015

  • Till date 2 Oct 2015, we have completed 90% of our project
  • Next iteration starts on 12 Oct 2015
  • Completed all core modules to be available for Web Beta Release
  • All core modules except Social Module to be available for Mobile Beta Release

Project Highlights:

  • Steep learning curve
  • More use-cases identified during development phase.
  • Team members too busy with other work
  • List of requirement changes
    • Change in data visualization libraries after acceptance for some functions. i.e Chart.js to d3.js to display stacked graphs for loan calculator comparisons.
    • Financial Education Module added
    • Retirement Planning Calculator added under Manage Personal Finance Module
  • Completed 3 UT tests with a total of 50 users.

Milestones Completed

  • Proposal Submission
  • User Test 1
  • User Test 2
  • User Test 3
  • Web Release 1
  • Mobile Release 1
  • Sponsor Seminar event

Milestones Remaining

  • Midterms
  • Web Release 2
  • Mobile Release 2
  • User Test 4
  • Final Web and Mobile Release
  • Final Presentation
  • Poster day


Project Management

Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.

Project Status:

2015T1 TEAMHEXA Project Status MIDTERMS.png

Project Schedule (Plan Vs Actual):

Summary of Planned vs Actual Schedule

2015T1 TEAMHEXA Schedule Planned vs Actual.png


Schedule Changes

2015T1 TEAMHEXA Schedule Changes Summary.png
  • Change 1: Admin Module (CRUD Users) shifted from Iteration 6 to Iteration 7 due to lack of time as we identified more use-cases than planned.
  • Change 2: Manage Personal Finance Module (CRUD Insurances) shifted from Iteration 7 to Iteration 8 as there were too many tasks in Iteration 7.
  • Change 3: Admin Module (Statistics of Community) and User Profile Module (Export PDF Report) shifted from Iteration 8 to Iteration 10. This was because of new additions of tasks in Iteration 8.
  • Change 4: User Test 3 was pushed earlier to Iteration 9 from Iteration 10. This is to test our application once more before Mid-terms presentation.
  • Change 5: Financial Health Module (Predictive Analysis of Credit Worthiness) shifted from Iteration 9 to Iteration 11. This is an Optional function. As new higher priority features were added, this optional task was pushed to a later iteration.

Scope Changes

2015T1 TEAMHEXA Midterm Scope.png

Project Metrics:

Schedule Metrics

Click here for details on how we calculate our schedule metrics and what are the respective plans of action to take when necessary.

2015T1 TEAMHEXA Schedule Metrics Iter8.png

Task Metrics

Click here for details on how we calculate our task metrics and what are the respective plans of action to take when necessary.

2015T1 TEAMHEXA Task Metrics Iter8.png

Bug Metrics

Click here for details on how we calculate our bug metrics and what are the respective plans of action to take when necessary.

2015T1 TEAMHEXA Bug Metrics MidTerm.png

Iteration 8

  • 3 high severity bugs – new users were not able to update database when they navigate from the homepage
  • Due to changes made to the database

Project Risks:

Click here to see how we identify risks, decide on the risk levels and action plans to take when necessary.

These are our top 3 risks:

Risk Type Risk Description Impact Likelihood Impact Category Mitigation Plan Status
Project Management Risk Most team members are doing internship and are only free to meet outside office hours with clients and supervisors. Delay in settling important decisions that require sponsor/supervisors' briefing. High High A PM to keep steady communication with our sponsor through emails so that the whole team can be in the loop. Also, could call the client as we realised that the client prefers calls however this would lead to difficulty in conveying full information to members as sometimes there might be too many information to recall in one phone conversation. Mitigated
Project Requirement Risk Sponsor adding new functionality on ad-hoc basis Project schedule will be affected and team has to brainstorm on solution to achieve end goal of Sponsor's request High Medium A Communicate and discuss with sponsor to negotiate scope, timeline and resources. Mitigated
Project Development Risk New use-cases that were only realized during development and not in planning phase. Change in development schedule. High Medium A Lead developer to discuss with PM immediately when situation arises. PM to re-schedule development and use buffer days if needed. Mitigated

Technical Complexity:

Backend has many different dependencies


Social Module

  • Many different use-cases to consider.
  • Complexity occurs when different permutations occurs for each case.


Linking data fields from across different Modules

  • Complexity occurs when user wants to manipulate his data. System has to be robust to be able to handle different scenarios.

Quality of product

Intermediate Deliverables:

Stage Specification Links
Project Management Minutes Meeting Minutes for Internal, Sponsor, Supervisor Meetings
Metrics Schedule Metrics

Task Metrics
Bug Metrics

Requirements Story cards Project Motivation, Scenario Storyboard
Analysis Use case Use Case Diagram
Architecture Diagram Architecture Diagram
Prototype Designs Prototype Designs
Testing Heuristic Evaluation Tests HE1, HE2
User Tests UT1, UT2, UT3
Internal Testing Internal Test Documents

Deployment:

Click here to enter our Beta Web Application

Testing:

User Test Date of User Test Objectives No of Participants Link
User Test 1
13/08/2014 to 14/08/2014
  • Gather feedback regarding user interface of developed functions from existing users
  • How easy is it for user to use
  • Which features is of importance to user
  • How good is the user experience
  • Detect usability issues based on user behavior
  • To use UT results to improve our web application
10 (Age range 18 - 35) User Test 1
User Test 2
17/09/15 3:00 pm - 20/09/15 11:59 pm
  • Gather feedback regarding user interface of developed functions
  • Detect usability issues based on user behavior
  • Find out if user interface is intuitive
  • Test success rate of users completing assigned tasks
  • Discover any usability issues
  • To use UT results to improve our web application for Beta Release
20 User Test 2

Reflection

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.

Chen Shiqi:

“I learnt the usefulness of proper review of past iterations can help in the success in planning for future iterations.”

Muhammad Izzuddin Bin Yushuff:

“ I learnt new technologies i.e. node and how to implement best practices in developing a something application.”

Peh Zu Cheng:

“I learn how the design of an application , no matter how much preparation and effort put in, can only be proven to be successful after going through tests with users themselves.”

Siranjeeviyan S/O Gopal

"Since acceptance, i've learnt that time management is very critical in order to deliver functions required by the client. Furthermore, i've become more efficient in conducting internal testing of functions and resolving bugs found, which is a result of my improved ability to code in Javascript (AngularJs). I hope to further improve my coding ability and subsequently contribute to providing a robust application for client."

Winnie Liew

“Having to juggle with FYP and other modules challenges me to plan ahead and utilizes every minutes well. A task list to keep me moving forward and tracking of my progress. I hope that the end product of this project will bring values to all the PMETS.”

Aung Swemon

“learnt new technical skills such as ionic framework in order to deliver the features required. I also learnt how to adapt to changes required in a limited time efficiently.”