HeaderSIS.jpg

IS480 Final Wiki

From IS480
Revision as of 21:46, 4 October 2010 by Benjamingan (talk | contribs) (New page: ==Project Progress Summary== The intent of the final is to compile the artifacts produced in this project and reflect on things that happened, what worked well, what failed and what you w...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Project Progress Summary

The intent of the final is to compile the artifacts produced in this project and reflect on things that happened, what worked well, what failed and what you would do next time. This page should NOT be too long. It can link to other pages (appendixes) 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?

Project Highlights:

What unexpected events occurred and how were they handled? For example, a team member left. 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

Project Challenges:

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.

Project Achievements:

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.

Project Management

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

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! Or everything has changed and the team is working on a new project with new sponsors and the supervisor is away. A good source for this section comes from the project weekly report.

Provide a comparison of the proposal schedule and the actual schedule up till now. Have all the milestones, deliverables, signoffs, iterations proceeded as planed? If not provide the updated schedule. Did the project reduce scope?

Planned Actual
Customer CRUD - 1 Sept 2010 25 Aug 2010
Trend Analytic - 1 Sept 2010 15 Sept 2010

Project Metrics:

Summary of analysis for the metrics collected.

Technical Complexity:

Describe the technical complexity of your project. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, etc.

Quality of product

Provide more details about the quality of your work.

Project Deliverables:

List the artifacts produced for this project, describe the complexity and scope. In this report, be brief (provide 1 or 2 example of diagrams/description/artifacts). Supplement the report with references to the entire deliverables. The entire deliverable can be submitted in a separate thumb drive, web repository or place in the IS480 team wiki.

The artifacts should include the different phases of your project • Analysis (use cases, story cards, functions/features), • Design (class diagram, ER diagram, etc), • Implementation (code, documentation) • Deployment (test plan, UAT, etc).

Quality:

Explain the quality of your project deliverables. Have you designed the architecture, use a pattern, etc? Be brief and supplement with project deliverables (if needed).

Deployment:

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 to supplement the architecture diagrams.

Testing:

Describe the testing done on your system. For example, the number of UAT, tester profile, test cases, survey results, issue tracker, bug reports, etc. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included here.

Reflection

Compile common lessons and reflection for the team and for each team member. Each member should provide a subsection reflection of the project.

Team Reflection:

Key lessons learned – these should be as specific as possible indicating where the team improved, or would do things differently next time. This report may refer the learning outcome summary in the IS480 team wiki. A very short checklist style will suffice.

Benjamin Gan Reflection:

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.