Project Progress Summary
We are at our final(16th) iteration!
Since the start of our project which started on the 28th of August, we have made several key accomplishments
- Deployed our application live with a launch event and feedback session
- Completed 4 UTs with Sponsors, Residents and SMU Students
- Managed (Still managing in fact) a 24/7 IT helpdesk
- Efficiently managed 2 code bases
- Successfully built a usable and deployed application, with minimal knowledge to frameworks such as hibernate and stripes.
- Completed our scope requirements and maximized value to sponsor
|
Project Highlights
Scope Completion
We have completed all of the functionalities as agreed upon with our client, as seen in our scope diagram below as well as our priority circle.
LivingNet Launch Events
Functionality Swap
Project Achievements
|
|
Successful Marketing Strategy
Our team has little experience in marketing, and having to market our application to real users, was initially a daunting task! We had multiple brainstorming sessions with our sponsor to devise a suitable marketing strategy.Finally, we are able to realize the strategy through a 3 week marketing campaign prior to the launch. The marketing was a success given the encouraging response shown by the residents who have unlocked their accounts.
|
|
Positive User Feedback
Through the various interaction sessions that we have had with the residents, our application has been praised for its novelty, ease of use, and impact in improving the living experience at the condominium. We have also implemented an in-app rating system, so that we can obtain quantitatively, the positive sentiments of the users. Given that this as a new good-to-have feature that we have just implemented, apart from our core functionalities, we believe that the quantitative ratings would give us a quantitative reflection of the positive feedbacks that we have so far.
|
|
|
|
Sponsor Satisfaction
Prior to starting the project, our sponsor gave us a 4 main KPIs in which they wanted to meet through the completion of the project. These KPIs include: To create an admin management system to effectively remove the need for paper based processed within the premises Enhance communication between residents at home and on-the-go To have a complete information and resource directory for residents. Fully migrate data from paper-based systems to the web-based system. To get at least 75% of the residents on board in using the application.
|
Project Challenges
Aligning deployment with sponsor's business processes
- Many levels of checks and approvals required before deployment is able to be carried out
- Logistics and training requirements was also a challenge as we needed to ensure that our key stakeholders such as the managing agent is able to use our application
- Needed to balance between increasing usage of application through marketing means agreeable with our stakeholders at the condominium
|
Project Management
Project Schedule
Project Schedule (MidTerm to Finals Plan vs Actual)
Project Metrics
Velocity Metric
Velocity Score Metric
Iteration Velocity Progress
Team Strength: represents the relative man hours available for development.
Score: represents the number of points we completed coding in the iteration.
Baseline Velocity: represents the speed of our progress, and is measured by taking the average of the previous 3 iterations.
Bug Metric
Note: No coding was done in iteration 1, 2 and 3, hence, there were no bugs reported.
Technical Complexity
Project Quality
Project Deliverables
Stage
|
Specification
|
Modules
|
Project Management
|
Minutes
|
|
Metrics
|
|
Schedule
|
|
Requirements
|
Story Cards
|
|
Research Gathering
|
|
Wireframes and Mockups
|
|
Change Log
|
|
Analysis
|
Use Case
|
|
Design
|
Deployment Diagram
|
|
Testing
|
User Test Plan
|
|
Supporting Documents
|
|
Quality
Deployment
Testing
GOALS AND OBJECTIVES OF USER TESTING
1. Be able to quantitatively and qualitatively determine the usability of our user interface so as to increase usability and aesthetics of our application
2. Identify the areas and causes of confusion so as to increase the usability and ease of using our application
3. Validate the usefulness of our functionalities so as to increase satisfaction of users needs in using our application
|
|
Data To Collect
|
Quantitative Data
|
Number of clicks needed to complete a task
|
Time taken to complete a task
|
Usability rating of each functionality
|
Qualitative Data
|
"Thinking-out-loud" feedback
|
Verbal feedback
|
|
UT 2
Focus Session with Managing Agent
Participant Demographic
Number of Participants: 1
Participant: Managing Agent, 26
Persona: Moderately tech-saavy Meticulous in handling day-to-day affairs in the condominium Oversees condominium operations
Needs: To move away from paper base system of managing facilities and residents Easier way to communicate with residents
|
|
|
UT 2 Results
Improvements Made
UT 3
User Testing with Participants from SMU
Participant Demographic
Number of Participants: 40
Participants: SMU Students
Persona: Tech-saavy Concerned with ease of use and aesthetics of application Avid users of social media and related applications
Purpose of UT: To obtain a larger sample of quantitative and qualitative feedback Validate our X-Factor
|
|
Participants from Session 3
|
Participants from Session 4
|
UT 3 Student Testing Results
Improvements Made
UT 4
UT with condo residents
Participant Demographic
Number of Participants: 5
Participant: Residents
Persona: Moderately tech-saavy
Needs: Convenient outlet to book facilities Channel for feedback to the managing agent
|
|
|
UT 4 Resident Testing Results
Improvements Made
UT 5
UT with participants from SMU
Participant Demographic
Number of Participants: 14 (7 for each type of testing)
Participant: Students
Persona: Different levels of tech-savvyness Mostly condominium residents
Needs: Convenient outlet to book facilities Channel for feedback to the managing agent
|
|
Implemented Scenario-based testing
|
|
Implemented scenario based testing based on the advice provided by Prof Richard during our midterm review. Scenario-based testing has enabled us to pick up the nuances of usability issues that would not be as noticable if we were to soley focus on task-based testing
|
UT 5 SMU Participants Testing Results
Improvements Made
Better navigation and forum-style enquiries
|
Improved Navigation
|
Shifted enquiries to become a standalone link in the navigation bar as some users had troubles finding where it was ---->
|
|
|
Made joyride activation button more obvious as some users were notice the presence of the functionality <----
|
Auto redirect admin users to the admin portal upon login, so as to reduce the number of clicks required for administrator to navigate themselves ---->
|
|
Forum Style Enquiry
|
|
Changed the style of enquiries as previously users had to submit more than 1 enquiry if after the first reply, they do not receive a satisfactory answer. Now users are able to see a conversation thread with the admin <----
|
Reflection
Team Reflection
Biggest Takeaway:
The importance of Stakeholder Management
- Each stakeholder has different needs, interests and expectations
- Experience in dealing with different stakeholder to meet their needs and ensuring that everyone is satisfied at the end of the day
- How to handle live users by providing help desk assistance as well as enquiry sessions
|
Individual Reflection
Ernest Cai, Management Associate, Maybank-Kim Eng
ernest.png "I believe the team had superseded our initial expectations of the project deployment and impressed the residents on the project delivery. They have managed the application deployment process very efficently and have also managed the enquiries of the support staff and live users professionally."
|