HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2013T1 ThunderBolt Mid Term wiki"

From IS480
Jump to navigation Jump to search
Line 64: Line 64:
 
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.
 
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===
 
===Project Metrics===
 +
Schedule metric
 +
[[Image:schedule metric chart.PNG|660px|left]]
 
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
 
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
 +
 
===Project Risks===
 
===Project Risks===
 
Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.
 
Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.

Revision as of 01:57, 9 October 2013

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

Highlight changes to modules, the completion status (implemented, user testing done, client approved, deployed, etc), the confidence level (0-1 where 0 is no confident of getting it done, 1 is 100% confident in getting it done) and comments (who has been assigned to do it, new scope, removed scoped, etc). Please use a table format to summarize with links to function details.

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 metric

Schedule metric chart.PNG

Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.

Project Risks

Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.

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.