Difference between revisions of "IS480 Team wiki: 2012T2 CHARIS/Final"
(→UT 5) |
(→UT 5) |
||
Line 417: | Line 417: | ||
<font size = 3>'''Participant Demographic</font> | <font size = 3>'''Participant Demographic</font> | ||
---- | ---- | ||
− | ''' Number of Participants:''' 14<br> | + | ''' Number of Participants:''' 14 (7 for each type of testing)<br> |
''' Participant: ''' Students<br> | ''' Participant: ''' Students<br> | ||
''' Persona: ''' <li> Different levels of tech-savvyness<li> Mostly condominium residents | ''' Persona: ''' <li> Different levels of tech-savvyness<li> Mostly condominium residents | ||
Line 426: | Line 426: | ||
|} | |} | ||
− | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px; width: | + | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px; width: 1000px" |
− | | [[Image:UT4Comparison.png | + | | [[Image:UT4Comparison.png]] |
|scope="row" width=500px" style="text-align: left; background: #999999"| | |scope="row" width=500px" style="text-align: left; background: #999999"| | ||
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 | 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 |
Revision as of 02:37, 17 April 2013
Project Progress Summary
Download our Final Presentation Slides
|
We are at our final(16th) iteration!
|
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
Project Challenges
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
Mobile optimization and responsive design |
---|
Closed-loop user notification strategy |
File:Charis notificationstrategy.png |
Code optimization for performance |
File:Charis Optimization.png |
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
|
|
---|
UT 2
Focus Session with Managing Agent
|
---|
UT 2 Results
View Results |
---|
Improvements Made
View Improvements Made |
---|
UT 3
User Testing with Participants from SMU
|
---|
UT 3 Student Testing Results
View Results |
---|
Improvements Made
View Improvements Made |
---|
UT 4
UT with condo residents
|
---|
UT 4 Resident Testing Results
View Results |
---|
Improvements Made
View Improvements Made |
---|
UT 5
UT with participants from SMU
|
---|
UT 5 SMU Participants Testing Results
View Results |
---|
Improvements Made
Better navigation and forum-style enquiries |
---|
Reflection
Team ReflectionBiggest Takeaway: The importance of Stakeholder Management
|
Individual Reflection
Sponsor Comments
ernest.png "I believe the team had superseded our initial expectations of the project deployment and impressed the residents on the project delivery. They managed the application deployment process very efficently and managed the enquiries of the support staff and live users"