IS480 Team wiki: 2017T1 Optimus Prime Midterm Wiki
- 1 Project Progress Summary
- 2 Project Management
- 3 Quality of product
- 4 Reflection
Project Progress Summary
The project is currently in the 13th (out of 16) iteration. 75% of the project is completed, with all core and secondary functions implemented as of mid-terms (mid-iteration 13). Modules we are currently left with are 1 tertiary module and 2 good-to-have modules.
Since project acceptance, the schedule has altered at 3 points:
- Iteration 2: Session module was extended 4 days, but tasks we re-estimated accordingly for the following iterations and overall timeline was not impacted. There were still buffer days left.
- Iteration 8: Bidding module was extended for an iteration, but tasks we re-estimated accordingly for the following iterations and overall timeline was not impacted. Deducted number of days from buffer days left.
- Sales Report Module has been shifted and extended from planned iteration 9 to 10, to 10 to 12. This is done due to past experience of the pre-sales report and we felt that more time should be allocated to this module based on its complexity. Tasks were re-estimated accordingly for the following iterations and overall timeline was not impacted. Deducted number of days from buffer days left.
Project Status: Green, confident to complete.
Complexity of the report modules were underestimated. When we started on the report modules, we realised that 100% accuracy of the reports we very challenging due to the amount of data that has to be translated from various different excel mapping files. Mapping conventions and algorithms were also more tedious than we expected.
This is one major reason for dropping a portion of our Sales Report Module – the RFP Sales report.
- We replaced this module with another 2 different downloadable reports of a similar nature because we felt that this would bring a much greater value to our clients considering our limited project timeline.
- All change management has been documented accordingly and the change documents can be found here.
- This is also one of the top 3 risks for us: Technical Complexity. Although when we initially thought out the risks, technical challenges arose from the unfamiliarity with a new framework and langugages. However, as we progressed, we realised that the technical complexity involved more of the the ability to translate all the data from various sources to the report with 100% accuracy.
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
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.
|Task/function/features, etc||Status||Confident Level (0-1)||Comment|
|Customer CRUD||Fully deployed and tested 100%||1||Fiona|
|Trend Analytic||25%||0.9||Ben is researching analytic algoritms|
Project Schedule (Plan Vs Actual):
Please refer to the links on Task Metrics & Bug Metrics for more information on the Metrics and how it is being calculated.
Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.
|Sponsor want to use Joomla instead of Drupal||High||High||Team evaluating Joomla to write an impact analysis report|
|Sponsor deployment machine approval and support||High||Medium (now it is low)||Use UPL machine|
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.
|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||Here|
|Screen Shots||CRUD Customer, Trend Analysis|
|Design||ER Diagram||1, 2, 3|
|Class Diagram||1, 2, 3|
|Testing||User test plan||instructions|
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.