HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 Charlies Angels Midterm Wiki"

From IS480
Jump to navigation Jump to search
Line 247: Line 247:
 
{| class="wikitable" style="background-color:#FFFFFF; width:80%;margin-left:10%; text-align: center;"
 
{| class="wikitable" style="background-color:#FFFFFF; width:80%;margin-left:10%; text-align: center;"
 
|-
 
|-
! style="color:white; background-color:#C43235;" colspan="4" | Technical Complexities
+
! style="color:white; background-color:green;" colspan="4" | Technical Complexities
 
|-
 
|-
| style="background-color:#EBAFB0; color: #000000; font-weight: bold;" | Rank
+
| style="background-color:#98FB98; color: black; font-weight: bold;" | Rank
| style="background-color:#EBAFB0; color: #000000; font-weight: bold;" | Technical Complexity Faced
+
| style="background-color:#98FB98; color: black; font-weight: bold;" | Technical Complexity Faced
| style="background-color:#EBAFB0; color: #000000; font-weight: bold;" | Reason
+
| style="background-color:#98FB98; color: black; font-weight: bold;" | Reason
| style="background-color:#EBAFB0; color: #000000; font-weight: bold;" | How did the team overcome this complexity
+
| style="background-color:#98FB98; color: black; font-weight: bold;" | How did the team overcome this complexity
 
|-
 
|-
 
| 1
 
| 1

Revision as of 21:06, 9 September 2016


Charlies Angels Logo.png


Charlies Angels Home.png  HOME

 

Charlies Angels About Us.png  ABOUT US

 

Charlies Angels Project Overview.png  PROJECT OVERVIEW

 

Charlies Angels Project Management.png  PROJECT MANAGEMENT

 

Charlies Angels Project Documentation.png  DOCUMENTATION

 
Main Wiki Charlies Angels Current Stage.png Midterm Wiki Final Wiki

Project Summary & Highlights

Charlies Angels Project Summary.png

Mid-Terms Snapshots:

  • The team has managed to coordinate efforts across geographical bounds (India-Singapore) in the early course of the project
  • Consumed 11 new APIs in the course of development
  • Picked up Multi-Threading on our own to improve system performance
  • Realised the importance of effective communication between all stakeholders; including internal communication
  • Learned to align product development in accordance to what users desire, instead of having tunnel vision as a development team. And also to recognise the importance of feedback, and translating them into actionable items

Project Management

Project Status:

S/N FEATURE STATUS CONFIDENCE LEVEL TO COMPLETE (0 - 1.0) REMARKS
1. Account Management Fully deployed and tested 100%; On production server 1.0 Completed
2. Automated StockBook Database Fully deployed and tested 100%; On production server 1.0 Completed
3. Homepage UI Fully deployed and tested 100%; On production server 1.0 Completed
4. Search & Display Stock Information Fully deployed and tested 100%; On production server 1.0 Completed
5. iStockTrade Fully deployed and tested 100%; On production server 1.0 Completed
5. StockBook Portfolio Stocks Fully deployed and tested 100%; On production server 1.0 Completed
6. StockBook Portfolio Summary Fully deployed and tested 100%; On production server 1.0 Completed
7. StockBook Dashboard Deployed and tested. But not with 100% confidence yet. On production server 1.0 In Progress
8. Robot Advisor Deployed and tested. But not with 100% confidence yet. On production server 1.0 In Progress
9. StockBook Analysis Currently in development 1.0 In Progress
10. iStockWatchList Currently in development 1.0 In Progress
11. StockBook Div Tracker Future Development 1.0 Future Development
12. StockBook News Future Development 1.0 Future Development
13. StockBook Alert Future Development 1.0 Future Development
14. StockBook Corp Action Still in discussion N.A Still in discussion
15. StockBook CDP Import Still in discussion N.A Still in discussion

Project Schedule (Plan Vs Actual):

Original Project Timeline

Charlies Angels Original Project Timeline.png

Latest Project Timeline

Charlies Angels Project Timeline.png

Changes in Schedule
Iteration No. Date of Schedule Revision Reason Dates Changed
3 1 Jul 2016 Client requested to add Dashboard, iStockTrade, and iStockWatchList feature as it is critical for an investment portfolio management application. Adjusted to now have 11 iterations instead of the original 9.
4 10 Jul 2016 Client requested to add a Dashboard and iStockTrade as it is critical for an investment portfolio management application. Adjusted Iteration 4's ending date to the 29th July, Iteration 5 to begin on 30th July, and UAT has been set on 5th Aug.
6 22 Aug 2016 Client has requested for more information to be displayed on the Dashboard and RoboAdvisor, requiring us to place these features on top priority for changes. Hence, a schedule change is necessary. Adjusted Iteration 6's ending date to 30th Aug, and adjusted all subsequent dates accordingly to accommodate for the newly proposed scope.

Project Metrics:

Please refer to the following URL for more information on the Metrics and how it is being collected and tabulated: Charlies Angels Metrics

Charlies-Angels-Metrics.png

Project Risks:

To view past risks that the team may have/may not been affected by, please visit: Charlies Angels Risk Management

Current Risks that may affect the team:

S/N RISK TYPE RISK DESCRIPTION LIKELIHOOD SEVERITY CATEGORY MITIGATION
1. Project Management Risk Team has rudimentary understanding of CPF and Housing Loan calculations Probable Critical Unacceptable The team gathered feedback, and also performed extensive research on the subject matter.
We also approached an employee working in CPF Board to clarify details.
2. Technology Risk The recent acquisition of Yahoo by Verizon poses an imminent threat to the existence of the Yahoo API where the team utilises to call for its financial information. Probable Critical Unacceptable The team has identified that Yahoo would close the service only in 2017. However, in the event that the service is closed during the phase of development, the purchase of a paid API is absolutely necessary. In the event of this purchase, the team would propose the drop of all functions happening thereafter, and focus on the fetch of data as it is essentially what makes the application.

Technical Complexity:

Technical Complexities
Rank Technical Complexity Faced Reason How did the team overcome this complexity
1
2
3

Changes in Scope

<To be filled>

Quality of product

<To be filled>

Intermediate Deliverables:

<To be filled>

Deployment:

<To be filled>

Testing:

<To be filled>

Reflection

<To be filled>

Team Reflection:

<To be filled>

Team Member #1 Reflection:

<To be filled>