Difference between revisions of "IS480 Team wiki: 2012T2 box.us MidTerms"
Qyang.2010 (talk | contribs) |
Qyang.2010 (talk | contribs) |
||
Line 441: | Line 441: | ||
* Optimizing the strengths and weakness of members - Made a change of role during the middle of the project because we realized that some roles could be better played by one person and other roles better played by another person. | * Optimizing the strengths and weakness of members - Made a change of role during the middle of the project because we realized that some roles could be better played by one person and other roles better played by another person. | ||
* Communication - This is the foremost important team that the team always seek to improve with the client | * Communication - This is the foremost important team that the team always seek to improve with the client | ||
− | |||
− | |||
− | |||
− |
Revision as of 09:48, 12 February 2013
HOME | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Project Progress Summary
Acceptance Slides:
- Mid Terms Slides: Coming Soon
- Mid Terms Deployed Site: Coming Soon
For proposal, please see Requrements at the Project Deliverables. This will help us understand your scope. Note wiki policy here.
Describe the project progress briefly here. Have the project continued as planned? If not, is the team confident to complete? This is a crossroad for the team to make a decision. Proceed with confident or file an incomplete.
Project Highlights:
What unexpected events occurred?
- "Task" functionality took longer than expected to scope and develop
- Small details that led to major changes
- Drop of mobile functionalities
- No clear defined business process initially
- Difference in understanding of coding conventions
Project Management
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
Project Status:
Functions | Prototyping | Implemented | User Tested | Client Approved | Confident Level | Comment |
Registration | Completed | Completed | User Testing 1 | Pending | 1 | Finishing up user interface for registration of Empact and NPO. Going on to do heuristics evaluation. |
Task | Completed | Completed | User Testing 1 | Pending | 1 | Left to complete the user interface for pending. Includes Task Review items. |
Questions | Completed | Completed | User Testing 1 | Pending | 1 | Final touchups to be done and then to subject to heuristics testing. |
Search | Completed | In Progress | User Testing 2 | Pending | 1 | Task search and NPO search is not yet completed. |
Volunteer Records | Completed | In Progress | User Testing 2 | Pending | 1 | Task search and NPO search is not yet completed. |
Statistics | Not started | Not started | User Testing 3 | Pending | 1 | Includes the dashboard for volunteers, Empact and NPOs. |
Notification | Not started | Not started | User Testing 3 | Pending | 1 | Includes notification |
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, 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:
Project Risks:
Priority | Type | Risk | Consequence | Likelihood | Impact Level | Risk Assessment Level | Mitigation Strategy |
---|---|---|---|---|---|---|---|
1 |
Team |
Small issues that are raised during the meeting get lost track as we go along in the iterations |
|
Likely |
Major |
High |
|
2 |
Business |
Difference in understanding of terminologies and terms used in describing the business process (e.g. task, questions, assignments) |
Confusion over terms that may lead to the wrong picture being conveyed between client and team |
Possible |
Minor |
Medium |
|
3 |
Resources |
Server is unable to cope with the capacity of the users |
|
Possible |
Moderate |
Medium |
|
Lessons Learnt from Managing Risks
Risk Management helps us to predict risk early and make necessary changes to the team even before the actual event happens.
- Issue Log has helped the team to have a systematic way of tracking the risks that can arise during the interactions between the team and between the meeting.
- Prototyping process has helped the team to visualize the end product early, but it also served as a communication tool between the different stakeholders in the project.
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 Assurance
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.
Intermediate Deliverables
There should be some evidence of work in progress.
Stage | Specification | Modules |
Project Management | Minutes | Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7 |
Metrics | Bug metrics | |
Requirements | Story cards | CRUD Customer, Trend Analytic |
Analysis | Use case | overall |
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.
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
Our testing approach focuses on 2 areas: Usability Testing and Code Quality Testing.
User Testing 1
We conducted our 1st user testing to try out the new features and at the same time to also test how would the users respond to the system. Until then, there was no information about how would the different users react to the system.
Actions Taken
| |
Heuristics Evaluation
- Heuristics Evaluation: 15 February 2013
Upcoming User Testings
- User Testing 2: 26 February 2013
- User Testing 3: 19 March 2013
Reflection
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.
Team Reflection:
Managing Change
- Change Management - A documented and ordered Change Management process to ensure that the interests of both parties are being captured.
- Issue Tracking - Tracking the many issues that are being raised by different stakeholders during the meetings
- Business Process diagram - Using these diagrams were effective in ensuring that every stakeholder is on the same page and have the same understanding
- Prototyping Process - Challenged the assumptions of all stakeholders about how the end system would look like and reduced the cost of changing the system at the start
Managing People
- Integrate with one another - Because we came from 2 very diverse groups with very different way of working and understanding of the project, there were much conflicts that had to be resolved at the start of the FYP.
- Optimizing the strengths and weakness of members - Made a change of role during the middle of the project because we realized that some roles could be better played by one person and other roles better played by another person.
- Communication - This is the foremost important team that the team always seek to improve with the client