HeaderSIS.jpg

IS480 Team wiki: 2013T1 ThunderBolt Mid Term wiki

From IS480
Jump to navigation Jump to search
Wikiprofilepic.png

Home

  Mid-Term Wiki   Final Wiki


Project Progress Summary

Immediate Deliverable

Click here 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
- Completed 8 iterations (out of 12 iterations in total)
- Conducted 2 User Testings with key users
- Live system deployed on 30 September

Project timeline overview

Midterm timeline.png.PNG


Place your Midterm slides link and deployed site link here For proposal, please see Requrements at the Project Deliverables. This will help us understand your scope. Note wiki policy here. This page should NOT be too long. It should link to other pages in the IS480 team wiki. Do not repeat the proposal or other wiki information here. However, keep a snapshot of the midterm state. Highlight changes since project acceptance. Describe the project progress briefly here. Have the project continued as planned? If not, is the team confident to complete? This is a crossroad for the team to make a decision. Proceed with confident or file an incomplete.

Project Highlights

What unexpected events occurred? Team members too busy with other work List of requirement changes CRUD items replaced with CU/Sync/Archive items Business analytics replaced with iPad client Took 8 weeks to learn Ruby on Rails etc. Be brief.

Project Management

Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.

Project Status

Project Schedule (Plan Vs Actual)

Compare the project plan during acceptance with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report. Provide a comparison of the plan and actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts.

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.

Schedule metric chart midterm.PNG
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
Bug distribution midterm.PNGBug distribution over iteration midterm.PNGBug score midterm.PNG
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:
Outstandingbugs.PNG
Bug No. 1 was only discovered when we deployed our system, we are currently working it and should be solved after midterm

Project Risks

Top3risks.PNG

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

There should be some evidence of work in progress.

Deployment

Testing

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.

Feature Status User Testing Status Deployment Status
Single-Sign On Completed UT1 & UT2
Transparent-green-checkmark.png
Role Switching Completed UT1 & UT2
Transparent-green-checkmark.png
Create Schedule Completed UT1 & UT2
Transparent-green-checkmark.png
View Schedule Completed UT1 & UT2
Transparent-green-checkmark.png
Edit Schedule Completed UT2
Transparent-green-checkmark.png
Archive Schedule Completed UT2
Transparent-green-checkmark.png
Create Booking Completed UT1 & UT2
Transparent-green-checkmark.png
View Booking Completed UT1 & UT2
Transparent-green-checkmark.png
Edit Booking Completed UT1 & UT2
Transparent-green-checkmark.png
Delete Booking Completed UT1 & UT2
Transparent-green-checkmark.png
Approve/Reject Booking Completed UT1 & UT2
Transparent-green-checkmark.png
Supervisor Availability Completed UT1 & UT2
Transparent-green-checkmark.png
Manage Milestone Configuration Completed UT1 & UT2
Transparent-green-checkmark.png
TA sign up for filming Completed UT2
Transparent-green-checkmark.png
Manage User Roles Not started UT1 & UT2
Transparent-green-checkmark.png