Difference between revisions of "IS480 Team wiki:2017T2 Zenith Midterm Wiki"
|Line 60:||Line 60:|
Revision as of 18:39, 3 February 2018
|Midterm Wiki||Final Wiki|
- 1 Project Progress Summary
- 2 Project Management
- 3 Quality of product
- 4 Reflection
Project Progress Summary
(insert link here)
(insert link here)
Our project schedule is divided into 13 iterations.
- We are currently on our 9th iteration.
- Up till (date), we have completed (percentage)% of our development progress.
- 1 user testing was conducted before midterms. The results are shown here.
- New team of clients
- List of requirement changes can be viewed here.
Project Schedule (Plan Vs Actual):
- Removal of UAT 1 at client's request. Client is unable to get NUS medical students for the user testing as it coincides with their exam period.
View our detailed schedule here!
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.
Be sure to prioritize the risks.
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.
There should be some evidence of work in progress.
Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.
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 user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.
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.
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.
Benjamin Gan Reflection:
You may include individual reflection if that make sense at this point. The team is uncooperative and did not follow my instructions.