IS480 final wiki: 2011T1 Discover Linkage
- 1 Project Progress Summary
- 2 Project Management
- 3 Quality of product
- 4 Reflection
Project Progress Summary
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, midterm or other wiki information here. Highlight changes since midterm.
Describe the project progress briefly here. Is the project completed? Link to the final presentation slides and videos.
What unexpected events occurred and how were they handled?
- A team member left the project and dropped the course
- 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
Be brief. A couple of sentences on the event and another couple on what was done is sufficient. Do not repeat the next sub sections. If there are no highlights, remove this section
Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section.
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
Project Schedule (Plan Vs Actual):
Compare the project plan during midterm 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.
|1||Customer CRUD||1 Sept 2010||25 Aug 2010||Fiona took the Sales CRUD as well.|
|Trend Analytic||1 Sept 2010||15 Sept 2010||Ben is too busy and pushed iteration 1 back|
|2||User tutorial||1 Oct 2010||Removed proposed by Ben|
|Psycho analysis||1 Oct 2010||New module proposed by sponsor|
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
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
Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.
List the artifacts produced for this project. The entire deliverable can be submitted in a separate thumb drive, web repository or place in the IS480 team wiki.
|Project Management||Minutes||Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7|
|Requirements||Story cards||CRUD Customer, Trend Analytic|
|System Sequence Diagram||client, server|
|Business Process Diagram|
|Screen Shots||CRUD Customer, Trend Analysis|
|Design||ER Diagram||1, 2, 3|
|Class Diagram||1, 2, 3|
|Handover||Manuals||User tutorial, Developer manual, Setup manual|
Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.
Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.
In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.
Describe the testing done on your system. For example, the number of UAT, tester profile, test cases, survey results, issue tracker, bug reports, etc.
Compile common lessons and reflection for the team and for each team member. Be brief.
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.
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.
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.