Difference between revisions of "IS480 Team wiki: 2012T2 Team Prime Final Wiki"
Line 471: | Line 471: | ||
<br> | <br> | ||
− | ==<font color="# | + | ==<font color="#794721">'''Reflections'''</font>== |
+ | ===<font color="#FC6B2A">Team</font>=== | ||
Team Reflection: | Team Reflection: | ||
− | Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here. | + | Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.<br><br> |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | ===<font color="#FC6B2A">Individual</font>=== | ||
{|class="wikitable" style="text-align: center;" | {|class="wikitable" style="text-align: center;" | ||
|+ | |+ | ||
|- | |- | ||
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Member</font> | ! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Member</font> | ||
− | ! scope="col" width=" | + | ! scope="col" width="300" style="background-color:#843A36"| <font color="#ffffff">Reflections</font> |
|- | |- | ||
− | ! scope="row" style="background-color:#ffffff"|[[Image:Prime_XC.png| | + | ! scope="row" style="background-color:#ffffff"|[[Image:Prime_XC.png|120px]]<br>Xiaochuan |
|style="text-align: left"| | |style="text-align: left"| | ||
− | + | #'''Learnt''' to be more flexible with and prioritize changes to be made, with the limited time and resources of the team | |
+ | #'''Learnt''' the importance of having good communication to make sure everyone is on the same page <br> | ||
|- | |- | ||
− | ! scope="row" style="background-color:#ffffff"|[[Image:Prime_HQ.png| | + | ! scope="row" style="background-color:#ffffff"|[[Image:Prime_HQ.png|120px]]<br>Lim Hui Qing |
|style="text-align: left"| | |style="text-align: left"| | ||
− | + | #'''Learnt''' the importance of engaging real users to test the system to ensure it is designed according to their expectations, and to propose appropriate solutions | |
+ | #'''Developed''' useful skills in video editing, coming up with a proper investor pitch and writing business plans <br> | ||
|- | |- | ||
− | ! scope="row" style="background-color:#ffffff"|[[Image:Prime_JO.png| | + | ! scope="row" style="background-color:#ffffff"|[[Image:Prime_JO.png|120px]]<br>Josephine Heng |
|style="text-align: left"| | |style="text-align: left"| | ||
− | + | #'''Learnt''' the importance of designing clear user interface mockups to make development more efficient | |
+ | #'''Learnt''' to analyze and validate business requirements, thereby creating a system that would benefit our end users <br> | ||
|- | |- | ||
− | ! scope="row" style="background-color:#ffffff"|[[Image:Prime_LR.png| | + | ! scope="row" style="background-color:#ffffff"|[[Image:Prime_LR.png|120px]]<br>Larry Ho |
|style="text-align: left"| | |style="text-align: left"| | ||
− | + | #'''Learnt''' to think from the user’s perspective rather than from a developer’s perspective when designing and developing the system <br> | |
− | |||
|} | |} |
Revision as of 05:12, 19 April 2013
Project Progress Summary
Project Overview
Final Presentation Slides
|
This is where we are on the timeline:
Project Highlights
Event | Highlights / Issue Description |
---|---|
Sprint 6 |
|
Sprint 7 |
|
Project Challenges
Project Achievements
- Secured Singapore Olympian swimmer Tao Li as our celebrity sponsor. View our interview with her HERE.
- Successfully conducted 2 rounds of USER TESTS at Yishun Swimming Complex and Sengkang Swimming Complex, with a total of 38 users and 7 swimming instructors.
- Received confirmation of investment on Swimix from investor Dr Virginia Cha, who is also one of our PROJECT ADVISORS from SMU Institute of Innovation & Entrepreneurship.
Project Management
Schedule (Planned Vs Actual)
Since the midterms, the following changes have been made to the project schedule:
|
Refer to the PROJECT TIMELINE for a full view of the current project schedule.
Scope (Planned Vs Actual)
Since the midterms, the following changes have been made to the project scope:
|
Project Metrics
Schedule Metric
The diagrams below show the burndown charts and schedule ratio charts of Sprints 6 to 8 since the midterms.
BURNDOWN CHARTS
KEY ISSUES
Sprint 6:
Sprint 7:
|
For more details:
1. Schedule Metric Calculation
2. Schedule Ratio Documentation: Sprint 1
Sprint 2
Sprint 3
Sprint 4
Sprint 5
Sprint 6
Sprint 7
Sprint 8
Bug Metric
Number of Bugs Found
|
Total Bug Score
|
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
Change Request Management
- If the priority is a MUST, we will implement the change
- If the priority is a SHOULD and the time to implement the change is VERY SHORT, SHORT, or MEDIUM, we will implement the change.
- If the priority is a COULD, and the time to implement the change is VERY SHORT, we will implement the change.
- If the priority is a WON'T, then we will not implement the request.
View our Change Request Log.
Project Risks
The top 3 risks are prioritised as follows:
Risk | Probability | Impact | Mitigation |
---|---|---|---|
Many issues might be raised during user tests; time is required to rectify these issues | High | Medium | Create a response plan document to help us decide whether to implement a change based on priority, complexity and time needed to rectify the issues. |
Project contains numerous documentation and different versions. Inefficent access to a particular document. | Low | Medium | Use a collaborative file management software (e.g. Google Documents, Dropbox) to organise respective folders of the project. Consensus amongst team members to adhere to proper version labelling. |
Putting too much focus on fixing user interface issues compared to ensuring the system logic is working properly | High | Medium | Prioritize the task according to the criteria and strike a balance between the two. |
View the full list of risks HERE.
Technical Complexity
The following technical complexities have been listed in order of complexity (highest to lowest):
Complexity | Description |
---|---|
1. Calendar |
|
2. Payment |
|
Quality of Product
Intermediate Deliverables
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | |
Metrics | ||
Requirements | Product Backlog | |
UI Mockups | ||
Analysis | Use Case | |
Process Flow Diagram | ||
Design | ER Diagram | |
System Architecture Diagram | ||
Testing | User Test 1 | |
User Test 2 |
Deployment
Environment | URL | Username / Password |
---|---|---|
Development |
|
User Test 2
Objectives
OBJECTIVES:
|
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 | Search for Class / Instructor |
✓ | N/A |
3 | Pay for Class |
✓ | N/A |
4 | Send Mass Notification to Students |
N/A | ✓ |
5 | Send Evaluation Survey to Students |
N/A | ✓ |
6 | Evaluate Instructor |
✓ | N/A |
7 | Add New Lesson Slot |
N/A | ✓ |
8 | Add Student to Lesson Slot |
N/A | ✓ |
THE SESSION
|
Testing Methodology
Collecting of Qualitative Metrics
Collecting of Quantitative Metrics
|
Registered Users
- Solution:
- Replace “Please Select” with “No Preference”, and remove the unnecessary “Zone” search option.
- Solution:
- Replace “ Use a different color for the instructor’s name and bold it.
- Solution:
- Include a popup message to inform unregistered users to login first before making payment.
POST-TEST SURVEY RESULTS:
Type here
Conclusion |
Instructors
- Solution:
- Replace the photos with useful information on how the system works.
POST-TEST SURVEY RESULTS:
Type here
Conclusion |
Reflections
Team
Team Reflection:
Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.