Difference between revisions of "IS480 Team wiki: 2013T1 ThunderBolt Mid Term wiki"
Line 277: | Line 277: | ||
===Testing=== | ===Testing=== | ||
+ | '''2 User Tests conducted''' <br> | ||
+ | User Test 1 - 2 Sep 2013<br> | ||
+ | User Test 2 - 4 October 2013<br> | ||
==<div style="background: #d5a10d; padding: 15px; font-weight: bold; line-height: 0.3em"><font color= #FFFFFF>Reflection</font></div>== | ==<div style="background: #d5a10d; padding: 15px; font-weight: bold; line-height: 0.3em"><font color= #FFFFFF>Reflection</font></div>== |
Revision as of 01:13, 10 October 2013
Mid-Term Wiki | Final Wiki |
Project Progress Summary
Immediate Deliverable
Click here[1] to download our mid-term presentation slides!
Link to deployment server: http://bit.ly/is480-ss
Link to live server (using by 2013/14 Term 2 students and supervisors): http://202.161.45.168/is480-scheduling/login.jsp
Our Key Accomplishments
- 70% of the project completed |
Project timeline overview
Click here to see more detail of our iteration plan.
Project Highlights
#1 - User Testing 1 was planned on 27 August 2013 for sponsors to test only, however, our sponsors requested to invite other stakeholders to the test as, thus, we have to shift the testing to 2 September to prepare for the change
#2 - In Iteration 7, sponsor requested to deploy our system for upcoming (2013/14 Term 2) FYP teams to book their acceptance presentation, we didn't expect live deployment to come so soon, thus, extra time were put in to clean up and set up the system to prepare for live deployment.
Project Management
Click here to see description of the funtionality
Click [2] to view our full project schedule.
Project Status
Feature | Status | User Testing Status | Deployment Status |
---|---|---|---|
Single-Sign On | Completed | UT1 & UT2 | |
Role Switching | Completed | UT1 & UT2 | |
Create Schedule | Completed | UT1 & UT2 | |
View Schedule | Completed | UT1 & UT2 | |
Edit Schedule | Completed | UT2 | |
Archive Schedule | Completed | UT2 | |
Create Booking | Completed | UT1 & UT2 | |
View Booking | Completed | UT1 & UT2 | |
Edit Booking | Completed | UT1 & UT2 | |
Delete Booking | Completed | UT1 & UT2 | |
Approve/Reject Booking | Completed | UT1 & UT2 | |
Supervisor Availability | Completed | UT1 & UT2 | |
Manage Milestone Configuration | Completed | UT1 & UT2 | |
Email Notification | Completed | UT1 & UT2 | |
TA sign up for filming | Completed | UT2 | |
CSV file upload | Completed | - | |
SMS Subscription | Completed | - | |
Manage Reminder Systems | Completed | - |
|
SMS Notification | Completed | - | |
Manage User Roles | Not started | - | - |
Manage Teams - Delete team | Not started | - | - |
Export Calendar | Not started | - | - |
Report Generation | Not started | - | - |
Presentation Subscription | Not started | - | - |
Facebook Integration | Not started | - | - |
Facility Booking | Not started | - | - |
Video Server Integration | Not started | - | - |
In Summary
We have 4 more iterations to go before our final presentation. We are currently on schedule and we are confident that the project will progress as planned.
Project Schedule (Plan Vs Actual)
Iteration | Task Name | Reason for the delay/push back | Mitigation |
---|---|---|---|
5 | Manage Milestone Configuration | This back-end side of this functionality was more complex than expected | The owner of this task continue to work on it while others start new iteration to work on other functionality |
8 | - Manage User Roles - Delete team |
These two functionality were scheduled in Iteration 8, however, we pushed back to Iteration 9. The reason for that is because we plan to launch our system to allow 2013/14 Term 2 FYP teams to book their presentations. Therefore, we felt that it is necessary to ensure system readiness by doing some clean ups instead of working on new functionality. | No impact to current Iteration. Switch some of the functionality (based on their difficulty level and importance) in iteration 10 and 11 to accommodate this change. |
8 | - CSV file upload | CSV file upload function was more complex than expected | Used up 2 buffer days to complete the task |
Project Metrics
Schedule metrics
The chart below shows the overview of schedule metrics we collected over past 8 iterations.
Click here to understand how we derive our metrics and what are the action plans to each metric.
Key issues
Iteration 4 (before acceptance): There was a delay in this iteration. Planned for 10 days, but we took 12 days to complete the tasks. This is because edit schedule and edit booking task was more complex than expected, mitigation was to use buffer days we have to complete them.
Iteration 5: There was another delay in this iteration. Planned for 11 days, but actual was 14 days. The reason being manage milestone configuration back-end logic was more complicated than expected. Our action plan was that the owner of the task continue to work on the task while others continue with other tasks in next iteration.
Iteration 8: CSV file upload function was delayed because there were alot of validations required to check the format and content of the file. And also we were busy with cleaning up the system to prepare for live deployment which was on 30 September. The action we took to overcome this was to use 2 buffer days we have.
Bug metrics
Click here to find out how we calculate our bug score and what are the respective action plans for different category of score.
Figure 1 shows the distribution of bug severity
Figure 2 further elaborate figure 1 by breaking down bug severity distribution over iteration
Figure 3 shows an overall bug score for our system as of now
Highlights:
Bugs logged here were discovered during internal testing which carried out at end of each iteration based on the test cases we created.Regressive testing methodology was used to conduct internal testing.
There was a spike in the bug score in Iteration 4, this was due to more complex tasks were developed during this iteration and also more rigorous testing conducted in our system in preparation for Acceptance presentation.
Outstanding bugs:
Bug No. 1 was only discovered when we deployed our system to live server, we are currently working on it and should be solved after midterm
Bug No. 2 is a minor bug that we will be fixing it after midterm
Project Risks
Click here to see complete list of risks
Technical Complexity
Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.
Quality of product
Intermediate Deliverables
Stage | Specification | Links |
---|---|---|
Project Management | Metrics | |
Minutes | ||
Requirements | Change Requests Log | |
Prototype | ||
Analysis | Use Case | |
Design | System Architecture Diagram | |
Testing | Internal Test Plan | |
Test cases and results | ||
User Testing 1 and User Testing 2 |
Deployment
System deployed to live server on 30 September.
Link to live server:[6]
System Activity/Statistics
- 19 teams(out of 30 teams from IS480 2013/14 Term 2 ) have used our system to make their acceptance presentation booking.
- ALL supervisors have used our system to interact with their teams
- ALL 19 teams managed to confirm their acceptance presentation slot in less than 5 days
Testing
2 User Tests conducted
User Test 1 - 2 Sep 2013
User Test 2 - 4 October 2013
Reflection
In this section, describe what have the team learn? Be brief. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
Team Reflection
Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.