HeaderSIS.jpg

IS480 Team wiki: 2017T1 Ctrl Alt Del Mid-Term Wiki

From IS480
Jump to navigation Jump to search
Ctrlaltdel-logo.png
HOME ABOUT US PROJECT OVERVIEW PROJECT MANAGEMENT DOCUMENTATION
MAIN WIKI MID-TERM WIKI FINAL WIKI


Ctrlaltdel-midterm.jpg


Project Progress Summary

Ctrlaltdel-midtermsummary.jpg
Midterm Slides Deployed Site
Ctrlaltdel-midtermslides.jpg Ctrlaltdel-deployment.jpg


Project Highlights
  • Took a total of 3 weeks to familiarize ourselves the Spring Boot framework for development
  • Took a total of 3 weeks to redesign and develop a working location based pricing function
  • Took 1 week to familiarize and deploy our site on our sponsor’s server (which is a server with have no experience with and has a different mode of deployment) with their development team
  • Retrieving the list of products to be uploaded and uploading it on our website
  • Hitting the target of 70 registered accounts
  • Completed User Testing:
    • User Testing 1 - Sponsor Level: Testers mentioned points of improvement for “Information Display”, confirmation messages for action, adding place holder images and pointed out a few bugs detected but they were generally happy with the website.
    • User Testing 2 - Customer Level: Testers pointed out a bug in the form validation on birthday and search bar. But complimented the design and UI.
    • User Testing 3 - Supplier Level: Testers pointed out the possibility of adding a location based pricing function that is suitable for the locations in Philippines and the display of prices in Filipino currency.
    • User Testing 4 - Customer Level: Testers who were less tech-savvy pointed out areas that are less intuitive for them but the idea and design was well-received.

Project Management

Project Status


Ctrlaltdel-projstatus.jpg
Ctrlaltdel-projstatus-modules.jpg
Project Schedule (Planned vs Actual)


Planned Project Timeline
Before timeline.png


Actual Project Timeline
After timeline.png


Project Metrics


Task Metric
Ctrlaltdel-midterm-metrics-tm.jpg
Bug Metric
Ctrlaltdel-metrics-bm.jpg
Project Risks
Ctrlaltdel-midterm-risks.jpg
Click here to see the full list of project risks: Risk Management
S/N Description Likelihood Impact Risk Type Risk Level Mitigation Learning points and Action
1 Uncertainty in getting actual suppliers (third party partners) to upload actual products on marketplace. Low High Business High Use dummy data and work out usability with OFWs in Singapore. Pitch to potential third-party suppliers with core functions of web application and acceptance by OFWs through survey. Eg: Our team can market our web application to potential sponsors by showing a working prototype and also responses from our surveys, showing the high demand for its purpose. Our initial idea of engaging suppliers to use our product did not include mom and pop shops and smaller companies. Thus with our focus on establised MNCs such as Watsons and Allianz, we learnt that it reduces the opportunity for potential suppliers we can work with. In addition, some of these MNCs require a longer amount of time to reach an agreement and utilize our website. Therefore, they may not be the most viable choices as our FYP has a time limit to work within.

To mitigate this risk, we decided to reach out to mom and pop shop and smaller local businesses. Firstly, this gives us more choices to work with and since they do not go through long processes to get approval to use our website to list their products, they are more suitable for our project schedule. Secondly, OFWs expressed they are agreeable with such idea since it supports the local market and businesses and some of their products are targeted and are more suitable for the locals.

2 Uncertainty in getting actual customers to make purchases in our marketplace. Medium Medium Business Medium Group to constantly engage with the people whom we have surveyed and update them on our progress. This can increase the chances of the OFW community using our web application when it is done. Eg: Our team has created a Facebook page which we use to put updates on our web development progress. During the survey taking, we have passed the link of the page to some to surveyees. Although we have yet to reach the stage of recruitment of customers to use our website, we have put in place outreach methods in order to increase the potential numbers of sign ups and make the idea of Pamilya Support(PS) more appealing to our customers. These methods include setting up a Facebook page which explains the function of PS and this page already has 70 likes. The reason for doing so is due to the fact that Filipinos are one of the most active users in Facebook, thus reaching to them through Facebook is an effective manner. Another method entails giving out flyers and getting sign ups in Lucky Plaza. This is essential as Lucky Plaza is a common hang out place for OFWs in Singapore and getting sign ups directly from there increases our chances of getting more registration.
3 Updating of codes and improvements results to change of original codes from time to time. High High Code Medium Agile development/ coding methods to enable our codes to be more adaptive if changes are required. This risk's impact is changed to High, as the new requirements takes up a lot of resources and time from the developers. Certain functions are more complicated and debugging sessions often require long hours. Although our development uses an aglie method, the complexity of the newly added and complicated functions often results to a bottleneck in our development process. For example, after the UAT with suppliers, we received feedbacks on our pricing structure for products thus we had to make improvements on our codes to make it more suitable for the Filipino market.

We seek to mitigate this by prioirtising the more relevent functions(to our suppliers and customers) over other functions we have previously considered doing. For instance, the entertainment module has been removed for the development of the location based pricing function in our website. Not only does this enable us to focus on more relevant functions, it prevents us from over running and ensure quality in our codes.

4 Client has ideas of having multiple functionalities that our web application can have. May result to it being too overwhelming for our group as we may lose our focus and scope for project. High Medium Client Medium Team to ensure that we have a clear understanding of what our priorities for the functionalities are. Eg: Our team grouped the functionalities mentioned into Core, Secondary, Tertiary and Good-To-Have functions which reflects how we prioritize them. We learnt that the mitigation for this risk has been rather effective as we have been prioritising functionalities in order to keep within our time frame and ensure quality of our codes. After receiving feedback from UAT with Suppliers our group had to implement new functions which we not discussed about previously. However, we decided to implement the newly suggested functions as they are more relevant to our target market. This shows an application of our mitigation.
Technical Complexity
Ctrlaltdel-midterm-complexity.jpg

Quality of Product

Intermediate Deliverables
Stage Link
Project Management Project Timeline
Metrics
Risk Management
Change Management
Project Overview Description & Motivation
Project Scope
Project Documentation Diagrams
Prototype
Meeting Minutes
Testing User Testing
Testing


Ctrlaltdel-midterm-testing.jpg

Click below to view our user tests in detail:
Ctrlaltdel-testing-1.jpg       Ctrlaltdel-testing-2.jpg       Ctrlaltdel-testing-3.jpg       Ctrlaltdel-testing-4.jpg

Reflection

Team Reflection


Ctrlaltdel-midterm-team-reflections.jpg
Individual Reflections
Ctrlaltdel-midterm-reflections.jpg
Sponsor's Comments


Ctrlaltdel-midterm-sponsor-reflection.jpg