Difference between revisions of "IS480 Team wiki: 2012T2 box.us MidTerms"
Qyang.2010 (talk | contribs) |
|||
(44 intermediate revisions by 3 users not shown) | |||
Line 69: | Line 69: | ||
=== Mid Terms Snapshots === | === Mid Terms Snapshots === | ||
<p> | <p> | ||
− | * | + | * [https://wiki.smu.edu.sg/is480/Image:Boxus_midtermslides.pdf Mid Term Slides] |
− | *'''Mid Terms Deployed Site:''' | + | *'''Mid Terms Deployed Site:''' [http://www.empact.sg/voma] |
</p> | </p> | ||
===Project Progress:=== | ===Project Progress:=== | ||
+ | [[Image:Projectprogressboxus.JPG|500px]] | ||
+ | |||
+ | We are 70% through with the functionalities of our system. | ||
===Project Highlights:=== | ===Project Highlights:=== | ||
Line 91: | Line 94: | ||
{| border="1" | {| border="1" | ||
− | |- style="background: | + | |- style="background:#810541; color:white" |
||Functions | ||Functions | ||
|align="center"|Prototyping | |align="center"|Prototyping | ||
Line 103: | Line 106: | ||
|| Registration | || Registration | ||
|| Completed <!-- Prototyping --> | || Completed <!-- Prototyping --> | ||
− | || | + | || In Progress <!-- Implemented --> |
|| User Testing 1 <!--User Tested --> | || User Testing 1 <!--User Tested --> | ||
|| Pending <!--Client Approved--> | || Pending <!--Client Approved--> | ||
| align="center"| 1 | | align="center"| 1 | ||
− | || | + | || Completed this module. |
|- | |- | ||
|| Task | || Task | ||
|| Completed <!-- Prototyping --> | || Completed <!-- Prototyping --> | ||
− | || | + | || In Progress <!-- Implemented --> |
|| User Testing 1 <!--User Tested --> | || User Testing 1 <!--User Tested --> | ||
|| Pending <!--Client Approved--> | || Pending <!--Client Approved--> | ||
|align="center"| 1 | |align="center"| 1 | ||
− | || | + | || Includes Task Review and Timesheet. |
|- | |- | ||
Line 130: | Line 133: | ||
|| Search | || Search | ||
|| Completed <!-- Prototyping --> | || Completed <!-- Prototyping --> | ||
− | || | + | || Completed <!-- Implemented --> |
|| User Testing 2 <!--User Tested --> | || User Testing 2 <!--User Tested --> | ||
|| Pending <!--Client Approved--> | || Pending <!--Client Approved--> | ||
|align="center"| 1 | |align="center"| 1 | ||
− | || | + | || |
|- | |- | ||
Line 143: | Line 146: | ||
|| Pending <!--Client Approved--> | || Pending <!--Client Approved--> | ||
|align="center"| 1 | |align="center"| 1 | ||
− | || | + | || |
|- | |- | ||
Line 156: | Line 159: | ||
|| Statistics | || Statistics | ||
− | || | + | || In Progress <!-- Prototyping --> |
|| Not started <!-- Implemented --> | || Not started <!-- Implemented --> | ||
|| User Testing 3 <!--User Tested --> | || User Testing 3 <!--User Tested --> | ||
Line 165: | Line 168: | ||
|| Notification | || Notification | ||
− | || | + | || In Progress <!-- Prototyping --> |
|| Not started <!-- Implemented --> | || Not started <!-- Implemented --> | ||
|| User Testing 3 <!--User Tested --> | || User Testing 3 <!--User Tested --> | ||
|| Pending <!--Client Approved--> | || Pending <!--Client Approved--> | ||
|align="center"| 1 | |align="center"| 1 | ||
− | || | + | || |
|- | |- | ||
Line 179: | Line 182: | ||
===Project Schedule (Plan Vs Actual):=== | ===Project Schedule (Plan Vs Actual):=== | ||
− | + | Take a look at our [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdGVRWVhPUGN5N0pwYmIwSndOWmIzQUE#gid=16 Project Schedule @ Mid Terms] | |
− | + | [[Image:Snap_2013-02-21_at_03.12.35.png]] | |
− | {| border="1" | + | <!--{| border="1" |
− | |- style="background: | + | |- style="background:#810541; color:white" |
|| Iterations | || Iterations | ||
|colspan="2" align="center"| Planned | |colspan="2" align="center"| Planned | ||
Line 217: | Line 220: | ||
|| 1 Oct 2010 | || 1 Oct 2010 | ||
|| New module proposed by sponsor | || New module proposed by sponsor | ||
− | |} | + | |} --> |
+ | |||
+ | <br/> | ||
+ | |||
+ | ===Project Scope (Acceptance Vs MidTerms):=== | ||
+ | |||
+ | |||
+ | [[Image:ScopeAtAcceptance.jpg | 500px | Schedule Ratio over Time]] | ||
+ | [[Image:ScopeAtMidterms.jpg | 500px | Schedule Ratio over Time]] | ||
+ | |||
+ | |||
+ | '''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 | ||
+ | |||
<br/> | <br/> | ||
+ | |||
===Project Metrics:=== | ===Project Metrics:=== | ||
Line 244: | Line 281: | ||
* [[IS480_Team_wiki:_2012T2_box.us_Project_Management#Risk_Management_Plan_Resources | Archived Risk Management Plans]] | * [[IS480_Team_wiki:_2012T2_box.us_Project_Management#Risk_Management_Plan_Resources | Archived Risk Management Plans]] | ||
+ | == Our Top 3 Risks== | ||
<center> | <center> | ||
{| class="wikitable sortable" style="text-align: center; width:500" | {| class="wikitable sortable" style="text-align: center; width:500" | ||
|+ | |+ | ||
|- | |- | ||
− | ! scope="col" width="10 | + | ! scope="col" width="10"| Priority |
− | ! scope="col" width="50 | + | ! scope="col" width="50" | Type |
− | ! scope="col" width="100 | + | ! scope="col" width="100" | Risk |
− | ! scope="col" width="100 | + | ! scope="col" width="100" | Consequence |
− | ! scope="col" width="80 | + | ! scope="col" width="80" | Likelihood |
− | ! scope="col" width="80 | + | ! scope="col" width="80" | Impact Level |
− | ! scope="col" width="100 | + | ! scope="col" width="100" | Risk Assessment Level |
− | ! scope="col" width="100 | + | ! scope="col" width="100" | Mitigation Strategy |
|- | |- | ||
+ | |||
! scope="row" style=" " |'''1''' | ! scope="row" style=" " |'''1''' | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"| |
Team | Team | ||
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | Underestimation of time taken to complete a module | |
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | # | + | # Delay in project schedule |
− | |||
− | |||
|style="text-align: center;"| | |style="text-align: center;"| | ||
Likely | Likely | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"| |
− | + | Moderate | |
− | |style="text-align: center;"| | + | |style="text-align: center;"| |
− | High | + | High |
− | |style="text-align: center;"| | + | |style="text-align: center;"| |
− | # | + | # Buffer at the end of every iteration |
− | # | + | # More buffer towards the end to act as contingency buffer in between iterations |
− | |||
|- | |- | ||
! scope="row" style=" " |'''2''' | ! scope="row" style=" " |'''2''' | ||
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | Project | |
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | Higher than expected number of issues raised during testing(s) | |
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | # Delay in project schedule | |
+ | # Changes may affect the system or scope" | ||
+ | |style="text-align: center;"| | ||
+ | Possible | ||
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | Moderate | |
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | Medium | |
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | # Change Management process to help evaluate whether the change is necessary | |
− | |||
− | # | ||
− | |||
− | |||
|- | |- | ||
! scope="row" style=" " |'''3''' | ! scope="row" style=" " |'''3''' | ||
+ | |style="text-align: center;"| | ||
+ | Project | ||
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | Business process of client is not clearly defined, leading to constant changes in the business process and design of the system | |
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | # Re-doing of system design that leads to unnecessary work | |
− | |style="text-align: center;"| | + | #Delay in Schedule |
− | + | |style="text-align: center;"| | |
− | + | Likely | |
− | |style="text-align: center;"| | + | |style="text-align: center;"| |
− | + | Major | |
− | |style="text-align: center;"| | + | |style="text-align: center;"| |
− | + | Extreme | |
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | # Client meeting at the start of iteration to be adopted and it would be able to include the review for the next iteration | |
− | + | # Require client to do up the business process diagram in order to allow client to think through the entire process. | |
− | + | # Prototyping process to let the client have a better idea of the end-product and what are the fields that would be necessary to capture within the system | |
− | # | ||
− | # | ||
|- | |- | ||
|} | |} | ||
+ | |||
</center> | </center> | ||
Line 323: | Line 359: | ||
# 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. | # 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. | # 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. | ||
− | |||
<br/> | <br/> | ||
Line 355: | Line 390: | ||
|| Issue Tracking | || Issue Tracking | ||
|| [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdE5FSkFZTkVULWIyMm5pUnJWX0drUnc#gid=0 Issue Tracking on Google Docs] | || [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdE5FSkFZTkVULWIyMm5pUnJWX0drUnc#gid=0 Issue Tracking on Google Docs] | ||
+ | |- | ||
+ | |||
+ | || Project Schedule | ||
+ | || [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHBHZ0ZqWEJEU19DekVSSUtuYW9IVGc#gid=16 Project Schedule on Google Docs] | ||
|- | |- | ||
Line 377: | Line 416: | ||
|- | |- | ||
− | || Testing | + | |rowspan="3"| Testing |
− | || User | + | || User Testing 1 Test Plans |
− | || [[ | + | || [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_box.us_Test_Plans#User_Test_1 Test Plans used] |
+ | |- | ||
+ | |||
+ | || Heuristic Evaluation User Scenarios | ||
+ | || [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_box.us_Test_Plans#Heuristic_Evaluation_1| User Scenarios used] | ||
+ | |- | ||
+ | |||
+ | || Integration Testings | ||
+ | || [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_box.us_Test_Plans#Integration_Testing| Integration Testings] | ||
+ | |- | ||
|} | |} | ||
Line 399: | Line 447: | ||
|width="500px" padding="20px"| | |width="500px" padding="20px"| | ||
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. <br/> | 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. <br/> | ||
− | ''' | + | |
− | # | + | '''User's feedback''' |
− | # | + | # "Log in was easy" |
− | '''Actions | + | # "More confirmation message needed" |
− | # | + | # "Question UI is good" |
− | # | + | # "It can be even more intuitive" |
− | + | '''For Further Actions''' | |
+ | # No actions taken yet! | ||
+ | # Actions will be taken after our mid terms presentation | ||
+ | |||
<br/> | <br/> | ||
Check out our [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_box.us_Test_Plans#Heuristic_Evaluation_1 Heuristics Evaluation 1 wiki] | Check out our [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_box.us_Test_Plans#Heuristic_Evaluation_1 Heuristics Evaluation 1 wiki] | ||
Line 414: | Line 465: | ||
=====Heuristics Evaluation User Scenarios===== | =====Heuristics Evaluation User Scenarios===== | ||
− | + | *[https://wiki.smu.edu.sg/is480/Image:Empact_Scenario.docx Empact Scenario] | |
− | + | *[https://wiki.smu.edu.sg/is480/Image:Volunteer_Scenario.docx Volunteer Scenario] | |
=====<h2>User Testing 1</h2>===== | =====<h2>User Testing 1</h2>===== | ||
Line 461: | Line 512: | ||
* 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 | ||
+ | |||
+ | |||
+ | ====='''Individual Reflection'''===== | ||
+ | |||
+ | <div> | ||
+ | [[Image:Kevin-Reflection.jpg|550px]] | ||
+ | [[Image:Sherrie-Reflection.jpg|550px]] | ||
+ | [[Image:BK-Reflection.jpg|550px]] | ||
+ | [[Image:Jenzus-Reflection.jpg|550px]] | ||
+ | [[Image:Waimun-Reflection.jpg|550px]] | ||
+ | [[Image:Jervenne-Reflection.jpg|550px]] | ||
+ | </div> |
Latest revision as of 13:13, 21 February 2013
HOME | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Project Progress Summary
Acceptance Snapshots
Mid Terms Snapshots
- Mid Term Slides
- Mid Terms Deployed Site: [1]
Project Progress:
We are 70% through with the functionalities of our system.
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 | In Progress | User Testing 1 | Pending | 1 | Completed this module. |
Task | Completed | In Progress | User Testing 1 | Pending | 1 | Includes Task Review and Timesheet. |
Questions | Completed | Completed | User Testing 1 | Pending | 1 | Final touchups to be done and then to subject to heuristics testing. |
Search | Completed | Completed | User Testing 2 | Pending | 1 | |
Volunteer Records | Completed | In Progress | User Testing 2 | Pending | 1 | |
Feedback Form | Completed | In Progress | User Testing 3 | Pending | 1 | Requirements gathering completed. Left implementation to complete. |
Statistics | In Progress | Not started | User Testing 3 | Pending | 1 | Includes the dashboard for volunteers, Empact and NPOs. |
Notification | In Progress | Not started | User Testing 3 | Pending | 1 |
Project Schedule (Plan Vs Actual):
Take a look at our Project Schedule @ Mid Terms
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:
Our Top 3 Risks
Priority | Type | Risk | Consequence | Likelihood | Impact Level | Risk Assessment Level | Mitigation Strategy |
---|---|---|---|---|---|---|---|
1 |
Team |
Underestimation of time taken to complete a module |
|
Likely |
Moderate |
High |
|
2 |
Project |
Higher than expected number of issues raised during testing(s) |
|
Possible |
Moderate |
Medium |
|
3 |
Project |
Business process of client is not clearly defined, leading to constant changes in the business process and design of the system |
|
Likely |
Major |
Extreme |
|
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 | |
Project Schedule | Project Schedule 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 |
Heuristic Evaluation User Scenarios | User Scenarios used | |
Integration Testings | Integration Testings |
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