HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T2 Team Prime MidTerm Wiki"

From IS480
Jump to navigation Jump to search
Line 81: Line 81:
  
 
[[Image:Prime_Scope_BeforeAfter.png]]
 
[[Image:Prime_Scope_BeforeAfter.png]]
<br>
+
<br><br>
Type a short description here.
+
 
 +
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 +
|scope="row"  width="1100" style="text-align: left; background: #FFFFFB"|
 +
'''Version 1 (Original)'''
 +
:*Features are categorized in priority circles:
 +
::*Core, Secondary and Tertiary Features: Features which will be developed by Prime during IS480
 +
::*Good-to-have Features: Features which are of lower priority and can be implemented in future beyond this project
 +
 
 +
'''Version 2'''
 +
:*'''Manage Students’ Progress''' was re-prioritised as a Tertiary feature since it is not the main focus of the IS480 project.  
 +
:*It was further re-prioritised as a Good-to-Have feature so that we can have a more manageable scope.
 +
 
 +
'''Version 3 (Latest)'''
 +
:*'''Manage Reviews''' and '''Manage Users’ Reviews''' was replaced with '''Manage Evaluations'''
 +
::*Reason: Anonymous users may write unpleasant comments on instructor’s profile page or vice versa, which will decrease the credibility of the site. The Manage Evaluations feature not only mitigates this problem but also allows students to conveniently access evaluation form via a link sent to their registered email account on Swimix.
 +
|}
  
 
===<font color="#FC6B2A">Project Metrics</font>===
 
===<font color="#FC6B2A">Project Metrics</font>===

Revision as of 18:41, 24 February 2013

<< MAIN WIKI

PrimeLogo.png


Project Progress Summary

Project Overview

AN OVERVIEW
• Link to Midterm Presentation Slides
• Link to Swimix site
• Link to Project Description
• Link to Interview with national swimmer Tao Li

The team is confident of completing the project within the schedule as shown below.


Prime ProjectMilestones WeAreHere V0.1.png

Project Highlights

Event Highlights
Sprint 3 Highlight 1

Type here

Sprint 4 Highlight 2

Type here

Sprint 5 Highlight 3

Type here

Project Management

Project Status

Features Status Confidence Level (0 - 1) Member In-Charge
Feature 1
Feature 2
Feature 3

Schedule (Planned Vs Actual)

Prime Schedule BeforeAfter.png

Type here

Scope (Planned Vs Actual)

Prime Scope BeforeAfter.png

Version 1 (Original)

  • Features are categorized in priority circles:
  • Core, Secondary and Tertiary Features: Features which will be developed by Prime during IS480
  • Good-to-have Features: Features which are of lower priority and can be implemented in future beyond this project

Version 2

  • Manage Students’ Progress was re-prioritised as a Tertiary feature since it is not the main focus of the IS480 project.
  • It was further re-prioritised as a Good-to-Have feature so that we can have a more manageable scope.

Version 3 (Latest)

  • Manage Reviews and Manage Users’ Reviews was replaced with Manage Evaluations
  • Reason: Anonymous users may write unpleasant comments on instructor’s profile page or vice versa, which will decrease the credibility of the site. The Manage Evaluations feature not only mitigates this problem but also allows students to conveniently access evaluation form via a link sent to their registered email account on Swimix.

Project Metrics

Schedule Metric

The team has completed 5 sprints thus far, as shown in the burn down charts below.

BURNDOWN CHARTS
Sprints1to4.png

Note: Burndown chart for Sprint 5 to be uploaded.

SCHEDULE RATIO CHARTS
ScheduleRatios Sprints1234.png

Note: Schedule ratio chart for Sprint 5 to be uploaded.

KEY ISSUES

Sprint 3:

  1. During December, the team met up every Monday to Thursday to complete tasks assigned. On 21 Dec, the calculated schedule ratio indicated that the team was behind schedule. We found out that the Manage Search (Instructors) feature needed more time to be completed. To get back on schedule, the team decided to shift the Manage Reviews feature to Sprint 4.
  2. On 27 Dec, the logic for Manage Search (i) feature was working but the feature had many alignment issues. The team also realised that we were behind schedule. To get back on track, we shifted the Update feature for Manage Class Registration to Sprint 4.

Sprint 4:

  1. On 10 Jan, the team met Dr. Miles Gilman (Entrepreneur-in-Residence, SMU Institute of Innovation and Entrepreneurship) for advice on improving our business plan for the ACE Startup Grant application.
  2. On 11 Jan, we consolidated all the changes to be made and realized that there were many changes to be made. The burndown chart also indicated that we were behind schedule. Hence, for the next 4 days, we dedicated much time and effort to get back on track. We decided to put our focus on the ACE submission which was in two weeks' time, therefore we shifted two features (Manage Recruitment and Manage Swim Schools) to future sprints.
  3. Since then, the team made slow progress on the features and eventually on 17 Jan, the burndown chart indicated that we were running behind schedule. The team decided to shift another two features (Manage Instructors and Manage Users) to future sprints.
  4. On 19 Jan, the burndown chart once again indicated that we were running behind schedule. The team decided to shift the Manage Notifications feature to future sprints.
  5. On 23 Jan, the team met with our supevisor Prof Lin Mei. After taking her feedback into consideration, we decided to replace the Manage Reviews feature and Manage User Reviews feature with Manage Evaluations which will be done at a later sprint.

Sprint 5:

  1. From User Test 1, the team collected much valuable feedback from the participants and wanted to implement as much feedback as we could. Hence, we put much focus into doing this at the start of the sprint.
  2. On 11 Feb, the team finalized the storyboarding based on the user test feedback, and realized that we needed more time to make changes. Since then, the team started moving away from the ideal progress line.
  3. On 17 Feb, the burndown chart indicated that the team was behind schedule. The team had an urgent meeting on 18 Feb to discuss our possible options. The outcome of the meeting was to prioritize the changes to be made from the user test feedback. We also managed our expectations for the remaining features before midterm.


For more details:
1. Schedule Metric Calculation
2. Schedule Ratio Documentation: Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5

Bug Metric

Prime NoOfBugsFound V2.png
Prime BugMetricSeverityChart V2.png





Number of Bugs Found

  1. The chart on the left show the number of bugs found in each sprint.
  2. In Sprint 3, there was a spike in the number of bugs found, due to the fact that more rigorous testing was conducted on the application to prepare for User Test 1 in the Sprint 4.



Total Bug Score

  1. The chart on the left shows the corresponding bug severity score with the number of bugs found in each sprint.
  2. The bug severity score in Sprint 3 was the highest out of all sprints due to the testing for User Test 1 as mentioned above.
Total Bug Score Action to be Taken
< 5 Developers resolve issues within the sprint.
5 - 9 Resolve the bugs during the planned debugging time.
≥ 10 Stop current development and resolve the bugs immediately.

For more details:
1. Bug Metric Calculation
2. Bug Log

Project Risks

The top 3 risks are prioritised as follows::

Risk Probability Impact Mitigation
Risk 1
Risk 2
Risk 3

View the full list of risks here.

Technical Complexity

Type here

Quality of Product

Intermediate Deliverables

Stage Specification Modules
Project Management Minutes
  • Team Minutes
  • Supervisor Minutes
Metrics
  • Schedule Metric
  • Bug Metric
Requirements Product Backlog
  • Product Backlog
Metrics
  • UI Mockups
Analysis Use Case
  • Use Case Diagram
Process Flow Diagram?
  • Process Flow Diagram
Design ER Diagram
  • ER Diagram
System Architecture Diagram
  • System Architecture Diagram
Testing User Test Plan
  • Execution Plan
  • Supporting Documents

Deployment

INSERT LINK TO SWIMIX WEBSITE

Instructions to access the system. If necessary, provide a deployment diagram link.

Testing

Objectives

OBJECTIVES:

  1. To obtain feedback from our users with regards to the features in the application
  2. To improve the usability of the application


Scope

The table below shows a list of features that were tested for our first user test. The features target parents (representing registered users of Swimix) and swimming instructors.

No. Features Reg. User Instructor
1 Register / Log in / Log out
2 Change Password
3 Update User Profile
4 Update Instructor Profile
5 Search for Class
6 Search for Instructor
7 Create and Remove Lesson Slot
8 Create and Remove Student Details

Insert relevant PICTURE.

THE SESSION
User Test 1 was conducted successfully on 27 Jan 2013 at Yishun Swimming Complex.

  1. A total of 8 parents participated in the user test in the role of a Registered User.
  2. A total of 2 swimming instructors participated in the user test in the role of an Instructor.


View the Supporting Documents for the user test HERE.


Testing Methodology

Collecting of Qualitative Metrics

  1. Participants are encouraged to think aloud their thought process as they are performing each task. For example, we would encourage them to say whatever they are looking at, thinking, doing, and feeling as they go about the task. This enables us as the observer to better understand each participant’s thought processs and see first-hand the process of him/her completing the task.
  2. Facilitators will observe for usability issues during the testing procedure by recording down what participants say. The test sessions will also be video-recorded on Screen Flow so that we can go back and refer to what participants did and how they reacted.
  3. In addition, after participants have completed the user test, they will be asked to do a satisfaction level survey that will aid in the collection of qualitative metrics.

Collecting of Quantitative Metrics

  1. The amount of time taken to complete each task
  2. The number of clicks taken for each task


Registered Users

MOST COMMON FEEDBACK:
Insert SCREEN SHOTS accompanied by a brief solution.


POST-TEST SURVEY RESULTS:
Insert RELEVANT CHART(S)
Insert RELEVANT SHORT CLIPS

Conclusion

Type here


Instructors

MOST COMMON FEEDBACK:
Insert SCREEN SHOTS accompanied by a brief solution.

POST-TEST SURVEY RESULTS:
Insert RELEVANT CHART(S)
Insert RELEVANT SHORT CLIPS

Conclusion

Type here


Reflections

Member Reflections
Prime XC.png
Shen Xiaochuan
  • Type here
Prime HQ.png
Lim Hui Qing
  • Type here
Prime JO.png
Josephine Heng
  • Type here
Prime LR.png
Larry Ho
  • Type here