HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T2 Nan Bo Wang FinalWiki"

From IS480
Jump to navigation Jump to search
Line 162: Line 162:
 
<br>
 
<br>
  
In total, there were <b>23 change request </b> made. Out of the 23, the team has successfully implemented 16 change request and rejected 7 change request.  
+
In total, there were <b>29 change request </b> made. Out of the 29, the team has successfully implemented 22 change request and rejected 7 change request.  
 
<br><br>3 Notable changes made were:<br>
 
<br><br>3 Notable changes made were:<br>
 
:*<b> Implementation of Interactive Dashboard </b><br>
 
:*<b> Implementation of Interactive Dashboard </b><br>

Revision as of 04:56, 21 April 2016


Colour5.jpg

HOME

 

ABOUT US

 

PROJECT OVERVIEW

 

PROJECT MANAGEMENT

 

DOCUMENTATION

 
Team Nan Bo Wang HomeIcon.jpg Main Wiki Midterm Wiki Final Wiki

Project Progress Summary


Team Nan Bo Wang ProjectSummaryDashboard.jpg

Wheels4Food Web Application Play Store App Store
Team Nan Bo Wang Wheels4FoodLogo.jpg NBW Android Logo.jpg NBW AppleStore.png


Project Materials


Presentation Slides Poster Video Pitch
NBW Slides.png NBW Poster.png NBW Video.png


Project Highlights


Functionalities

Primary Secondary Tertiary & Good-to-Have
Team Nan Bo Wang ProjectHighlightsCore.jpg Team Nan Bo Wang ProjectHighlightsSecondary.jpg Team Nan Bo Wang ProjectHighlightsTerGTH.jpg

Testing

NBW UTSummary.jpg

Project Challenges / Risk


Challenge Faced Mitigation Plan Outcome
Challenge in getting FFTH’s Partner VWO to come onboard and use the application Our team organized user trainings to introduce FFTH's Partners to the application and to coach them on how to use the application. Mitigated
Team is not proficient in Mobile Development technologies. The team was expected to develop the mobile application on both platform. Technologies like Hybrid Framework was entirely new to the team. Our team research on relevant technologies and decided that Hybrid Framework would pose a lower learning curve. The team took 3 weeks to be familarize with the framework and other mobile technologies that is required for the development. Mitigated
Client’s requirement of the system might change overtime.i.e Change in Business Process after Midterms which required the team to change the backend logic and database. The team sat down to discuss and identify the affected areas and came up with a progressive plan to include this change without affecting the other planned functionalities. Mitigated


Achievements


NBW XFactor.jpg

Project Management



NBW ProjectScope.jpg

Project Schedule

You can view our detailed Project Schedule here!

Planned!

Team Nan Bo Wang AcceptanceSchedule.jpg

Actual!

NBW ActualSchedule.jpg

Metrics

Task Metrics

You can view our Task Metrics here! Team Nan Bo Wang ScheduleMetricFinals.PNG


The team has adopted burndown charts to better understand and predict when all of the work will be completed.
You can view our Burndown Charts here!


Bug Metrics

NBW BugMetric.JPG

Remarks
We launched our application to go live in this iteration.
Bug reported by users mainly consist of cosmetic problems of low priority.

Change Management


In total, there were 29 change request made. Out of the 29, the team has successfully implemented 22 change request and rejected 7 change request.

3 Notable changes made were:

  • Implementation of Interactive Dashboard
  • Multiple Food Item in a Single Request
NBW ChangeOverview.PNG

Technical Complexity


Business Logic Complexity

Team Nan Bo Wang TechnicalComplexity.png

  • The web application has to cater to multiple stakeholder’s decision and each decision would affect the outcome of request made by the requester.

Different Libraries have different versions

Team Nan Bo Wang LibTechCom1.png Team Nan Bo Wang LibTechCom1.png

Multiple Frontend Validation

NBW TechComplex3.JPG

Web Service Security

NBW TechComplex4.JPG

Calculate & Displaying direction between delivery locations

NBW TechComplex5.JPG

Quality of Product




Stage Specification Modules
Project Requirements Story boards Story board
Project Management Minutes Meeting Minutes
Project Management Risk, Metrics, Change Management

Bug Metrics
Schedule Metrics
Risk Management
Change Management

Analysis and Design Use Case, Architecture Model, As-Is, To-Be Processes, Logical Diagram Use Case, Architecture Model, As-Is, To-Be Processes, Logical Diagram
Design Prototype Persona

Prototype

Testing User Test Plan

User Testing 1
User Testing 2
User Testing 3
User Testing 4
User Testing 5
User Testing 6
User Testing 7
UAT

Client & Sponsor Testimonial

Testimonial by DHL: NBW Midterm Testimonial.png
Testimonial by FFTHTestimonial.JPG

Learning Outcome

  • Valerie: I better understood the purpose of conducting user testing. User testing in essence allows us to identify any changes required to improve user performance and satisfaction and by analysing and incorporating user feedback into our application.
  • Andrew: I became more familiar with commercial and industrial backend web technologies. Integrating with the front end has also proven to be a challenging task to ensure both front and back end validations integrate seamlessly.
  • Wei Fa: I learnt to manage client requirements and change. I gained valuable exposure to new technologies such as Ionic framework and AngularJS for mobile development.
  • Wei Xiang: I've learnt that if the backend services are not thought out fully and implemented carefully, it will heavily impact the upcoming functions that are dependent on it. Which in turn, it will affect the whole project schedule as we have to revisit and change that service
  • Samantha: I have learnt to be comfortable with changes and to better manage the various stakeholders and their expectation. In addition, I have learnt to motivate and maintain the team synergies