IS480 Team wiki: 2012T2 box.us MidTerms
HOME | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Contents
Project Progress Summary
Acceptance Snapshots
Mid Terms Snapshots
- Mid Terms Slides: Coming Soon
- Mid Terms Deployed Site: Coming Soon
Project Progress:
Project Highlights:
What unexpected events occurred?
- "Task" functionality took longer than expected to scope and develop
- Re-working of User Interface
- Drop of mobile functionalities
- No clear defined business process initially
Project Management
Project Status:
View the detailed Project Scope on Google Docs to have an understanding of our 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. |
Feedback Form | Completed | In Progress | User Testing 3 | Pending | 1 | Requirements gathering completed. Left implementation to complete. |
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):
Take a look at our Project Schedule @ Mid Terms
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 Scope (Acceptance Vs MidTerms):
Changes made
1) Added Interview Form
Enabled Empact to review through the information that was keyed in during the interview with the users
2) Added Feedback Form
Enabled volunteers to give inputs to Empact about whether the activity completed
3) Added Dashboard
Enabled users to access their information quickly Enabled Empact to view vital information about their system quickly
4) Dropped Mobile Functionalities
Mobile functionalities are a subset of the functionalities of the system Allows team to focus more on developing a good web application
Project Metrics:
|
|
Project Risks:
Box.us uses a risk management plan to scan and mitigate risks that can arise. Please view the following for a view of how we manage our 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.
Intermediate Deliverables
There should be some evidence of work in progress.
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | Meeting Minutes |
Iteration Reports |
The iteration reports covers the bug ratios and schedule ratios for each iteration. | |
Change Management | Change Log on Google Docs | |
Issue Tracking | Issue Tracking on Google Docs | |
Requirements | Prototyping Process | Prototyping |
Analysis | Use case | Use Case Diagram |
Business Process Diagram | Process Diagrams | |
Design | ERD Diagrams | V1,V2,V3,V4,V5 |
Testing | User Testing 1 Test plans | [| Test plans used] |
Deployment
Instructions on how to access the system
- Go to Empact's VOMA
- Log in with the provided credentials (Will be shown only during the presentation)
- Have fun!
Usability
Heuristics Evaluation 1
We conducted our 1st Heuristic Evaluation where we get our SIS experts, that is those who have taken or are currently taking Interaction Design and Prototyping (IS306) to critique and evaluate the usability issues of our web application. User's feedback
For Further Actions
| |
Heuristics Evaluation User Scenarios
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. Interesting Findings
Actions Taken
| |
Upcoming User Testings
- User Testing 2: 26 February 2013
- User Testing 3: 19 March 2013
Reflection
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