Difference between revisions of "IS480 Team wiki: 2012T2 Team Prime Final Wiki"
m |
|||
Line 3: | Line 3: | ||
<br> | <br> | ||
[[Image:PrimeLogo.png|880px|right]]<br> | [[Image:PrimeLogo.png|880px|right]]<br> | ||
− | + | ||
==<font color="#843A36">'''Project Progress Summary'''</font>== | ==<font color="#843A36">'''Project Progress Summary'''</font>== | ||
+ | <!-- | ||
===<font color="#FC6B2A">Project Overview</font>=== | ===<font color="#FC6B2A">Project Overview</font>=== | ||
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px" | {| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px" | ||
Line 17: | Line 18: | ||
The team is confident of completing the project within the schedule as shown below. | The team is confident of completing the project within the schedule as shown below. | ||
|} | |} | ||
+ | --> | ||
− | [[Image:Prime_ProjectMilestones_WeAreHere_V0. | + | [[Image:Prime_ProjectMilestones_WeAreHere_V0.2.png]]<br> |
===<font color="#FC6B2A">Project Highlights</font>=== | ===<font color="#FC6B2A">Project Highlights</font>=== | ||
Line 25: | Line 27: | ||
'''Highlight 2''': Manage Reviews and Manage Users’ Reviews was replaced with Manage Evaluations<br> | '''Highlight 2''': Manage Reviews and Manage Users’ Reviews was replaced with Manage Evaluations<br> | ||
'''Highlight 3''': 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. <br> | '''Highlight 3''': 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. <br> | ||
+ | |||
+ | ===<font color="#FC6B2A">Project Challenges</font>=== | ||
+ | <br> | ||
+ | |||
+ | ===<font color="#FC6B2A">Project Achievements</font>=== | ||
+ | <br> | ||
==<font color="#843A36">'''Project Management'''</font>== | ==<font color="#843A36">'''Project Management'''</font>== | ||
Line 602: | Line 610: | ||
|} | |} | ||
− |
Revision as of 01:56, 18 April 2013
Project Progress Summary
Project Highlights
Highlight 1: Confirmation of endorsement from Tao Li who has represented Singapore in many international swimming competitions including the Beijing and London Olympics.
Highlight 2: Manage Reviews and Manage Users’ Reviews was replaced with Manage Evaluations
Highlight 3: 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.
Project Challenges
Project Achievements
Project Management
Schedule (Planned Vs Actual)
Note:
No significant changes have been made to the schedule with regards to the proposal and acceptance milestones.
However, significant changes have been made to the project schedule in the subsequent four milestones as shown below.
Changes Made
|
Refer to the PROJECT TIMELINE for a full view of the current project schedule.
Scope (Planned Vs Actual)
Version 1 (Original)
Version 2
Version 3 (Latest)
|
Project Metrics
Schedule Metric
The team has completed 5 sprints thus far, as shown in the burn down charts below.
BURNDOWN CHARTS
KEY ISSUES
Sprint 3:
Sprint 4:
Sprint 5:
|
For more details:
1. Schedule Metric Calculation
2. Schedule Ratio Documentation: Sprint 1
Sprint 2
Sprint 3
Sprint 4
Sprint 5
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
- PHP CodeIgniter 2.1.3
- a. Understand the framework
- b. Apply the framework
- c. Customize the code
- d. Debug the application
- Balance between the UI and code reusability
- Upload image
- Payment
- Shopping cart
- Calendar
- Scope too big for us to handle
Quality of Product
Intermediate Deliverables
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | |
Metrics | ||
Requirements | Product Backlog | |
Metrics | ||
Analysis | Use Case | |
Process Flow Diagram | ||
Design | ER Diagram | |
System Architecture Diagram | ||
Testing | User Test Plan |
Deployment
Area | Description |
---|---|
Development Environment |
|
Database |
|
Web Links |
Testing
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 | 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
|
Testing Methodology
Collecting of Qualitative Metrics
Collecting of Quantitative Metrics
|
Registered Users
- Solution: Place Login and Register in the same area and allow switching by tabs.
- Solution: Change the View link to a button so users know that they can click on it to view the instructor’s profile
POST-TEST SURVEY RESULTS:
SN | Functions | Very Unlikely | Unlikely | Undecided | Likely | Very Likely |
---|---|---|---|---|---|---|
1 | Search for Class/Instructor |
0 | 0 | 0 | 5 | 3 |
2 | Online Class Registration |
0 | 1 | 2 | 3 | 2 |
3 | Online Payment |
0 | 1 | 0 | 4 | 3 |
4 | Instructor Review |
0 | 2 | 1 | 4 | 1 |
5 | Instructor Rating |
0 | 0 | 2 | 5 | 1 |
6 | Receive Notification |
0 | 0 | 1 | 3 | 4 |
Conclusion The top 2 favourite functions identified by the users were the Manage Search function and the Manage Notification function. They commented that the search function was easy to use and could be very useful to them. The notification function is also something they felt is lacking in the industry now. This is because they have made wasted trips to the swimming complex on the lesson day only to find out the lesson was cancelled. The function that had the highest amount of users indicating that they are unlikely to use is the Instructor Review feature. They explained that they would not want to go through the trouble to register an account just to write a review for the instructors. However, they would not mind writing if given the option of a simpler and more convenient alternative. A user also commented that he preferred to register classes with the instructor in person instead of registering online because he could infer the instructor’s character and personality through the former. A possible solution is to include a short introduction video clip of each instructor so that users are able to gauge the instructor for themselves through the video. |
Instructors
- Solution:
- Use radio buttons instead of dropdown list.
- Solution:
- Display only the student name and contact number.
- Instructors can choose to click on the student's name to view the rest of their information.
POST-TEST SURVEY RESULTS:
SN | Functions | Very Unlikely | Unlikely | Undecided | Likely | Very Likely |
---|---|---|---|---|---|---|
1 | Adding lesson slots to calendar |
0 | 0 | 1 | 1 | 0 |
2 | Selling available class slots |
0 | 0 | 0 | 1 | 1 |
3 | Sending mass notification |
0 | 0 | 0 | 0 | 2 |
4 | Online payment system |
0 | 0 | 2 | 0 | 0 |
Conclusion |
Reflections
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.
Individual Reflection: Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.
Sponsor Comment: Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
Member | Reflections |
---|---|
Shen Xiaochuan |
|
Lim Hui Qing |
|
Josephine Heng |
|
Larry Ho |
|