Difference between revisions of "IS480 Team wiki: 2012T2 box.us Final"
Qyang.2010 (talk | contribs) |
Qyang.2010 (talk | contribs) |
||
Line 97: | Line 97: | ||
===Project Achievements:=== | ===Project Achievements:=== | ||
− | + | * Issue Tracker - Implementing the issue tracker has helped us in a few ways: | |
− | + | ** Systematic way of keeping track of issues being raised up along the way | |
+ | ** A good way for the team of keep track of what had been completed and track back again | ||
==<p><div class="NavHead" style="background-color:#810541;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 12pt;"><span style="color: White"> '''Project Management''' </span></div></p>== | ==<p><div class="NavHead" style="background-color:#810541;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 12pt;"><span style="color: White"> '''Project Management''' </span></div></p>== |
Revision as of 22:15, 3 April 2013
HOME | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Contents
Project Progress Summary
What Is This Project About?
Check out our 1 min ++ video pitch to find out what this project is about at Youtube
Quick Links
Final Presentation Slides: coming soonDeployed Site: Empact ACT]Initial Proposal: Proposal |
---|
Project Highlights:
What unexpected events occurred and how were they handled?
- Change of User Testing to Deployment
- Managing the Great Amount of Issues Being Highlighted
- Refining the Quality of the Application
- Technical Challenges faced with the Statistics
- Took longer than expected to work it out
- Notifications requirements gathering took longer than expected
Project Challenges:
- Gathering requirements
- Dealing with constant changes
- Meeting the needs of the client and balancing with the workload of the individual team members
Project Achievements:
- Issue Tracker - Implementing the issue tracker has helped us in a few ways:
- Systematic way of keeping track of issues being raised up along the way
- A good way for the team of keep track of what had been completed and track back again
Project Management
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.
Iterations | Planned | Actual | Comments | ||
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 |
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.
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
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.
Project Deliverables:
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.
Stage | Specification | Modules |
Project Management | Minutes | Meeting Minutes |
Metrics | Bug metrics | |
Requirements | Story cards | CRUD Customer, Trend Analytic |
Analysis | Use case | Use Case Diagram |
System Sequence Diagram | client, server | |
Business Process Diagram | Process Diagrams | |
Screen Shots | CRUD Customer, Trend Analysis | |
Design | ERD Diagrams | V1,V2,V3,V4,V5 |
Class Diagram | 1, 2, 3 | |
Testing | User Testing 1 Test Plans | Test Plans used |
User Testing 2 Test Plans | Test Plans used | |
Heuristic Evaluation User Scenarios | User Scenarios used | |
Integration Testings | Integration Testings | |
Handover | Manuals | User tutorial, Developer manual, Setup manual |
Code | client server | |
Deployment Diagram | instructions |
Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.
Quality:
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.
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 link.
Testing:
Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.
Reflection
Compile common lessons and reflection for the team and for each team member. Be brief.
Team Reflection:
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.
Individual 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 or member roles. Link if necessary.
Sponsor Comment:
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.