Difference between revisions of "IS480 Team wiki: 2013T1 ThunderBolt Final wiki"
Line 42: | Line 42: | ||
===Project timeline overview=== | ===Project timeline overview=== | ||
[[Image:final timeline.png.PNG|1000px|center]]<br> | [[Image:final timeline.png.PNG|1000px|center]]<br> | ||
− | Click [ | + | Click [https://www.dropbox.com/s/natqomvruai2rrj/ThunderBolt%20Full%20Schedule.pdf] to view our full project schedule. |
===Project Highlights=== | ===Project Highlights=== |
Revision as of 00:11, 25 November 2013
Mid-Term Wiki | Final Wiki |
Project Progress Summary
Immediate Deliverable
Click here [1] download final presentation slides
Link to deployment server: http://bit.ly/is480-ss
Link to live server : http://202.161.45.168/is480-scheduling/login.jsp
Our Key Accomplishments
- 99% of the project completed |
Project timeline overview
Click [2] to view our full project schedule.
Project Highlights
Video Pitch
Click here to watch the video!
Project Poster
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
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
Stage | Specification | Links |
---|---|---|
Project Management | Metrics | |
Minutes | ||
Requirements | Change Requests Log | |
Prototype | ||
Analysis | Use Case | |
Design | System Architecture Diagram | |
Testing | Internal Testing Test Plan | |
Internal Testing Test cases and results | ||
User Testing 1 | ||
User Testing 2 | ||
User Testing 3 |
Deployment
System was first deployed on 26 Sept, followed by second deployment on 22 Oct and final deployment with full functionality on 21 Nov 2013
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.