HeaderSIS.jpg

IS480 Team wiki: 2016T2 LOCK MidTerms

From IS480
Jump to navigation Jump to search
LockLogo3.jpg


LockHouse.png   HOME LOCK-About Us.png   ABOUT US LockGraph.png   PROJECT OVERVIEW LockManage.png   PROJECT MANAGEMENT LockDocuments.png   DOCUMENTATION

 


OUR PROJECT PROGRESS

Midterm Slides
Team Lock's Mid-term slides

Summary of Project

Our project currently has 15 iterations. As of 20th February 2015, we have just completed iteration 10 of the project. Based on our team's estimates, we have completed up to 60% of our development process. In the last few months, we have completed our user testing and have successfully conducted our soft launch for our Android application on 12th Febuary 2015! Our mobile application is available on Google Play Store now!

Our Development Progress

Slide Progress.PNG

OUR PROJECT MANAGEMENT

Project Scope

Planned Actual
LOCK-Scope.png
TeamLockScope.jpg


Highlights of Changes Made in Scope

  • Movement of Social Media Module to Secondary Function
  • Movement of Career Buddy from Secondary Function to Core Function
  • Implementation of new Module called : Job Suggestion Module
  • Moved Geotagging to Good-to-have-Function


Project Schedule

TEAMLOCK Schedule.PNG

Highlights of Changes Made in Schedule

  • Re-Scheduled Career Buddy Module to Iteration 10
  • On Clients discretion , we delayed the soft launch date from 27th January to 12th February 2016 as Client was not ready for deployment


Metrics

Schedule Metric

TEAMLOC Midterms Schedule Metrics.PNG


Highlights of Schedule Metrics
Iteration Planned (Days) Actual (Days) SM Score Action Status
8 6 14 43% Team before this iteration was on schedule and estimates were fairly accurate. However, schedule was highly delayed in iteration as we had to implement a new UI/UX given to us by our client. Immediate action was to focus on pushing our the new UI in time for soft-launch and mitigation was done through usage of buffer days and rescheduling of priorities. Completed



Bug Metric

iOS Android
TEAMLOCK iOS Bug Metrics.PNG TEAMLOCK Android Bug Metrics.PNG



Highlight of Changes in Collection of Bugs

There was a huge spikes of bugs found in iteration 7 & 8 (both iOS & Android). This was largely due to the fact this was the period where our team was solely focusing on cleaning up our application(Fixing of bugs/UI) in preparation for Soft-Launch.

Iteration Bug Score Summary of Bugs and Issues Action Taken
7 65 (iOS) , 34 (Android) In this iteration, our client proposed an entire UI overhaul for our application. We responded to this with proper discussions, and agreed to the new UI based on our consensus to improve the overall usability and design of our application. This resulted in a full-scale change as we shifted away from the old UI, with the addition of new functions. And because of the immense changes, the conversion of the old UI to new UI required changes to the logic behind the UI as well. This led to the discovery and birth of many bugs during this iteration. Stop current development and resolve bugs immediately. Seek to solve all the minor bugs and issues during the allocated debugging period of the iteration. (Next iteration - 8)
8 35 (iOS) In this iteration, our team was preparing for the soft-launch of our application, making sure that our application was bug free and user friendly. As there were new several critical bugs found in our application, following our schedule all work was put on hold to ensure that these bugs was resolved before moving foward Stop current development and resolve bugs immediately. All bugs and issues were resolved during allocated debugging period of the iteration.


Full documentation of our issue tracker is available on our Test Documents which can be found here!(Android) & here!(iOS)

Project Risks

LOCK Risk 1.PNG
LOCK Risk2.PNG


LOCK Risk3.PNG

Technical Complexity

How we design our Architecture?

Android Arc.png
LOCK IOS Arc.PNG

Project Complexity

1.
LOCK Tech Spring.PNG
2.
LOCK CUS UI.PNG
3.
Tech Swift.png

OUR QUALITY ASSURANCE

Deliverables

Type Decription Documentation
Requirement Gathering Market Research Market Research
Project Management Minutes, Metrics, Risks, Change

Meeting Minutes
Metrics
Risk Management
Change Management

Analysis and Design Use Case, Architectural Diagram, ER Diagram, Technology and Tools Used Use Case, Architectural Diagram, ER Diagram, Technology and Tools Used
Testing User Test Plan

User Testing 1
User Testing 2

Testing

As at 20th February 2016, we have completed 2 User Testing. These activities are primarily conducted to ensure that the StaffOnDemand Mobile satisfies the needs of our target group as agreed upon with our Sponsors and provides confidence of its use.

User Testing 1

  • Number of Users: 30
  • Venue: SOE-SR3.1
  • Date: 3rd – 5th November 2015
  • Duration: 15 minutes per user
  • Test Platform: Android Mobile Device , iOS

Objective:User Testing is conducted to ensure that StaffOnDemands satisfies our target consumer group and meets the expectations of sponsors and users. In this User Testing, we are primarily focusing on :

  • Usability and intuitiveness of functions
  • Find bugs / defects in the application


User Testing 2

  • Number of Users: 42
  • Venue: SOE-SR-3.1 | SOE SR-2.7
  • Date: 15th January 2015
  • Duration: 15 minutes per user
  • Test Platform: Android Mobile Device , iOS

Objective:User Testing is conducted to ensure that StaffOnDemands satisfies our target consumer group and meets the expectations of sponsors and users. In this User Testing, we are primarily focusing on :

  • Gathering feedback from potential stakeholders with regards to the heuristics and design of the existing functions of the current application
  • Identify any usability issues that persist in the application
  • Improvement of our application based on the results

OUR LEARNING OUTCOMES

LOCK Reflection.PNG