Difference between revisions of "IS480 Team wiki: 2012T2 box.us Final"
Qyang.2010 (talk | contribs) |
Qyang.2010 (talk | contribs) |
||
(9 intermediate revisions by the same user not shown) | |||
Line 63: | Line 63: | ||
{|class="wikitable" style="width:1000px" | {|class="wikitable" style="width:1000px" | ||
!style="width:100%" | | !style="width:100%" | | ||
− | <center><h4>Final Presentation Slides: <small> | + | <center><h4>Final Presentation Slides: <small>[https://www.dropbox.com/s/ekd30gxh1mco2da/MASTER%20SLIDES%20V4%20%28BLACK%29.pdf Final Presentation Slides]</small></h4></center> |
<center><h3>Deployed Site: <small>[http://www.empact.sg/act Empact ACT]</small></h3></center> | <center><h3>Deployed Site: <small>[http://www.empact.sg/act Empact ACT]</small></h3></center> | ||
<center><h3>Demonstration Site: <small>[http://www.empact.sg/testact Empact ACT(Staging)]</small></h3></center> | <center><h3>Demonstration Site: <small>[http://www.empact.sg/testact Empact ACT(Staging)]</small></h3></center> | ||
Line 201: | Line 201: | ||
====SCHEDULE METRICS==== | ====SCHEDULE METRICS==== | ||
* Schedule: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdGVRWVhPUGN5N0pwYmIwSndOWmIzQUE#gid=16 Schedule on Google Docs] | * Schedule: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdGVRWVhPUGN5N0pwYmIwSndOWmIzQUE#gid=16 Schedule on Google Docs] | ||
+ | * Schedule Metric has remained within the healthy range. No further action has to be taken. | ||
[[Image:Boxus_Schedulemetricsfinals.png | 500px]] | [[Image:Boxus_Schedulemetricsfinals.png | 500px]] | ||
Line 209: | Line 210: | ||
* <b>User Acceptance Testing</b> | * <b>User Acceptance Testing</b> | ||
* <b>Technical Understudy</b> | * <b>Technical Understudy</b> | ||
− | + | <br/> | |
==== Deployment Testing ==== | ==== Deployment Testing ==== | ||
+ | * <i>Collated List of Issues from Deployment Testing</i>: [[Media:BoxusIssuesReleasees.xlsx | Deployment Issues List]] | ||
We release 5 versions of the system on the live environment before going entering the User Acceptance Test. Our purpose for deployment testing was to determine what are the issues that would arise from using the application in the actual conditions in varied browsers and system settings. Additionally, we also collected suggestions from the users in order to make further improvements to the application. In deploying the application, we followed the following process: | We release 5 versions of the system on the live environment before going entering the User Acceptance Test. Our purpose for deployment testing was to determine what are the issues that would arise from using the application in the actual conditions in varied browsers and system settings. Additionally, we also collected suggestions from the users in order to make further improvements to the application. In deploying the application, we followed the following process: | ||
Line 476: | Line 478: | ||
===Deployment Testing:=== | ===Deployment Testing:=== | ||
+ | * We did a total of 4 releases before our UAT, and 1 more after our UAT with the changes made from UAT. | ||
+ | * View our detailed [[IS480_Team_wiki:_2012T2_box.us_Test_Plans#Deployment_Testing | Deployment Testing]] in our wiki [[IS480_Team_wiki:_2012T2_box.us_Test_Plans#Deployment_Testing | here]] | ||
+ | * Here are the key changes that have been highlighted: | ||
{|class="wikitable" style="width:500px; align:center" | {|class="wikitable" style="width:500px; align:center" | ||
Line 538: | Line 543: | ||
===Testing:=== | ===Testing:=== | ||
* We conducted 3 types of testing within our system: | * We conducted 3 types of testing within our system: | ||
− | * Find out [[IS480_Team_wiki:_2012T2_box.us_Test_Plans | more]] about the testing | + | * Find out [[IS480_Team_wiki:_2012T2_box.us_Test_Plans | more]] about the testing [[IS480_Team_wiki:_2012T2_box.us_Test_Plans | here]] |
{|class="wikitable" style="width:1000px; align:center" | {|class="wikitable" style="width:1000px; align:center" | ||
!style="align:left;width:30%" | User Testing | !style="align:left;width:30%" | User Testing | ||
Line 572: | Line 577: | ||
* Learning to have fun as a team! | * Learning to have fun as a team! | ||
* Our IS modules have helped to prepare us for the demands of an IT project | * Our IS modules have helped to prepare us for the demands of an IT project | ||
+ | <br/> | ||
===Individual Reflection:=== | ===Individual Reflection:=== | ||
+ | * Detailed Individual Reflections at [[IS480_Team_wiki:_2012T2_box.us_Learning_Outcomes#Personal_Learning_Outcomes | Final Presentation Learning Outcomes]] | ||
<p>'''Kevin''' <br/> | <p>'''Kevin''' <br/> | ||
As I review through my initial learning outcomes that I set out to learn, I felt that I have managed to meet these outcomes in the following way: | As I review through my initial learning outcomes that I set out to learn, I felt that I have managed to meet these outcomes in the following way: | ||
− | * Motivating IT Project teams | + | * Motivating IT Project teams |
− | * Evaluating IT project ideas | + | * Evaluating IT project ideas |
− | * Time Management Skills | + | * Time Management Skills |
− | * Client Negotiation skills | + | * Client Negotiation skills |
− | * Applied Project Management Skills | + | * Applied Project Management Skills |
</p> | </p> | ||
<p>'''Sherrie''' <br/> | <p>'''Sherrie''' <br/> | ||
− | |||
− | |||
With regards to my education, in a bigger picture, I have been able to apply the following | With regards to my education, in a bigger picture, I have been able to apply the following | ||
− | *Understanding and improving business processes | + | *Understanding and improving business processes |
− | *Understanding how IT and business value | + | *Understanding how IT and business value |
− | *Presentation skills | + | *Presentation skills |
</p> | </p> | ||
Line 596: | Line 601: | ||
As this FYP is coming to an end, these are the few learning points that i am taking it away: | As this FYP is coming to an end, these are the few learning points that i am taking it away: | ||
− | *Time managment | + | *Time managment |
− | *Usability learning journey | + | *Usability learning journey |
</p> | </p> | ||
<p>'''Jenzus''' <br/> | <p>'''Jenzus''' <br/> | ||
− | At the start, I envisioned that IS480 is a platform that will validate my IS education and sum up my journey as an IS student. Boy! I got more than what I expected and was overwhelmed by the entire journey. | + | At the start, I envisioned that IS480 is a platform that will validate my IS education and sum up my journey as an IS student. Boy! I got more than what I expected and was overwhelmed by the entire journey. |
− | *Never stop learning | + | *Never stop learning |
− | *Understanding business requirements | + | *Understanding business requirements |
− | *Team | + | *Team Dynamic |
</p> | </p> | ||
Latest revision as of 14:41, 22 April 2013
HOME | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Project Progress Summary
Final Presentation Slides: Final Presentation SlidesDeployed Site: Empact ACTDemonstration Site: Empact ACT(Staging)Backup Demonstration Site: Backup Demo SiteInitial Proposal: Proposal |
---|
What Is This Project About?
Check out our 1 min ++ video pitch to find out what this project is about at Youtube
Project Highlights:
Managing the Great Amount of Issues being Highlighted during Deployment
|
Volunteers did not find language in the system friendly
|
Addition of 2 functionalities
|
Project Challenges:
Gathering Requirements from Empact
How we Managed
|
Dealing with Changes
|
Project Management
Project Scope:
Change | Change Description |
---|---|
1 |
Export Task and Volunteer Information
|
2 |
Notification
|
Project Schedule (Plan Vs Actual):
Project Metrics:
BUG METRICS
- Bug Score: Bug Metric on Google Docs
- Bug Log: Bug Log on Google Docs
- Explanation of Bug Tracking: Bug Metrics
Iteration | Bug Score | Any Actions Taken |
---|---|---|
11 | 28 |
Increase in Bug Score due to bugs that were recorded from User Testing 2
|
12 | 11 |
New features of the system(Statistics, Dashboard and Notifications) were being released
|
13 | 32 |
More thorough testing was being performed for the UAT
|
SCHEDULE METRICS
- Schedule: Schedule on Google Docs
- Schedule Metric has remained within the healthy range. No further action has to be taken.
Handing Over
Take a look at our Handing Over Plan: Handing Over Plan on Google Docs
We followed a methodical process to get the handing over completed. Our handing over plan spelt out the key information for the team and Empact to foresee and plan what would be happening in the final few iterations as we covered the remaining parts of the project. The entire phase consists of:
- Deployment Testing
- User Acceptance Testing
- Technical Understudy
Deployment Testing
- Collated List of Issues from Deployment Testing: Deployment Issues List
We release 5 versions of the system on the live environment before going entering the User Acceptance Test. Our purpose for deployment testing was to determine what are the issues that would arise from using the application in the actual conditions in varied browsers and system settings. Additionally, we also collected suggestions from the users in order to make further improvements to the application. In deploying the application, we followed the following process:
Date | Description | Features Released |
---|---|---|
11/03/2013 |
Release 0.1 |
|
18/03/2013 |
Release 0.2 |
|
25/03/2013 |
Release 0.3 |
|
02/04/2013 |
Release 0.4 |
|
11/04/2013 |
Release 0.5 |
|
19/04/2013 |
Release 1.0 |
|
User Acceptance Test
We conducted our User Acceptance Test on 05/04/2013 at the Empact office. A final verification was made concerning all the issues and defects that were being raised during the UAT. The final verification of all the functionalities were done on the following week at 12/04/2013.
- Instructions Scripts:We conducted the UAT by going through the business processes that the system would address and followed by the remaining functionalities. This also helps Empact to better visualize how the system has met their business requirements.
- Test Cases: We simulated 3 stakeholders in doing up the test cases.
- Test Cases (5 April 2013):
- Test Cases (12 April 2013):
- Scenario-based Instructions and Exceptional cases
Managing Defects
- Note: BA refers to the facilitators in the UAT test
- All defects are highlighted onto a separate issue list.
- The list is collated and sent to Empact to prioritise based on issues.
- Bugs are fixed immediately
Recording Issues
Issues are recorded in a separate issue list on Google Docs
Technical Understudy
- We conducted a technical understudy with Empact's technical understudy (Sophie) and our client (Peter Yang)
- Lesson Plan: Lesson Plan on Google Docs
Session 1 | Session 2 |
---|---|
29 Mar 2013, 1600hrs-1800hrs | 12 Apr 2013, 1930hrs-2145hrs |
Session Contents:
|
Session Contents:
|
Handing Over Day
- We had a handing over day to verify that all the agreed documents have been handed over to Empact.
- Handing Over Date: 20/04/2013
- Handing Over Plan: Handover Plan
- Verified that all documents have been given
Quality of product
Project Deliverables:
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | Meeting Minutes |
Metrics | Bug metrics, Schedule | |
Iteration Reports | Iteration Reports | |
Milestones | Milestones List | |
Issue Tracking | Issues List | |
Requirements | Paper Prototypes | Paper Prototypes |
Analysis | Use case | Use Case Diagram |
Business Process Diagram | Process Diagrams | |
Screen Shots | All Screenshots | |
Design | ERD Diagrams | V1,V2,V3,V4,V5 |
System Architecture | System Architecture Diagram | |
Usability Testing | User Testing 1 Test Plans | Test Plans used |
User Testing 2 Test Plans | Test Plans used | |
Heuristic Evaluation User Scenarios | User Scenarios used | |
Software Testing | Integration Testing | Integration Testings |
Deployment Testing | Deployment Testing | |
Handover | User Manuals | Empact Manual , NPO Manual , Volunteer Manual |
Design and Technical Specifications | Design and Technical Specifications |
User Testing 2
We conducted our 2nd user testing to try out our newly added features and at to see how users would respond to them. Interesting Findings
Actions Taken
| |
Deployment Testing:
- We did a total of 4 releases before our UAT, and 1 more after our UAT with the changes made from UAT.
- View our detailed Deployment Testing in our wiki here
- Here are the key changes that have been highlighted:
Release 0.1 |
---|
Key Changes
|
Release 0.2 |
---|
Key Changes
|
Release 0.3 |
---|
Key Changes
|
Release 0.4 |
---|
Key Changes
|
Release 0.5 |
---|
Key Changes
|
Testing:
User Testing | Integration Testing | Deployment Testing |
---|---|---|
Objective: To collect feedback concerning usability of our application | Objective: To test the quality of our application | Objective: To collect feedback when application is being used in live environments |
When: User Testing 1, User Testing 2 | When: At the end of every iteration | When: Before the start of every deployment |
How: Volunteers, NPOs and Empact staff would follow a given User Test cases | How: Following the integration test plan. Perform regression testing of all the functionalities | How: Following the integration test plan. |
Reflection
Team Reflection:
- Managing client expectations
- Learning to collaborate more effectively in a team
- Leveraging one another's strength and weaknesses
- Being a good team player within the team
- Learning to have fun as a team!
- Our IS modules have helped to prepare us for the demands of an IT project
Individual Reflection:
- Detailed Individual Reflections at Final Presentation Learning Outcomes
Kevin
As I review through my initial learning outcomes that I set out to learn, I felt that I have managed to meet these outcomes in the following way:
- Motivating IT Project teams
- Evaluating IT project ideas
- Time Management Skills
- Client Negotiation skills
- Applied Project Management Skills
Sherrie
With regards to my education, in a bigger picture, I have been able to apply the following
- Understanding and improving business processes
- Understanding how IT and business value
- Presentation skills
Wai Mun
As this FYP is coming to an end, these are the few learning points that i am taking it away:
- Time managment
- Usability learning journey
Jenzus
At the start, I envisioned that IS480 is a platform that will validate my IS education and sum up my journey as an IS student. Boy! I got more than what I expected and was overwhelmed by the entire journey.
- Never stop learning
- Understanding business requirements
- Team Dynamic
Boon Kheng
I think the IS480 project is a great experience for me as it is my first time implementing such a big solution in a team. Other than technical skills, I’ve seen how an organization like Empact progress together with the project, it seems like both the sponsor and the team work closely together to achieve goals for both parties.
I find that this is a great collaboration as both the sponsor and us are sharing knowledge with each other, after this project, I get to know more about how a social enterprise operates and also, the sponsor Peter did feedback that he learnt a lot of technical knowledge through the project.
I am also able to apply subjects that we‘ve learnt during curriculum put in use, such as project and process management and also see how case studies issues being showcase in real scenarios.
Jervenne
Throughout my FYP journey, I didnt expect to have learn so much by now. Initially I was expecting to learn more and hone my technical skills, and to learn to take on a big project in a bigger group.
Not only did I achieved what I was set out for, but I'm able to see clearly how applicable IS480 is in the real world and how I can apply what I've learnt in school to this project.
My other takeaways will be: managing expectations of the clients, taking feedback for usability improvements, setting priorities, and time management.
Through this FYP period, I've also see the importance of managing client relationship and to educate them on their needs and wants, and also what actually can be done so they can understand better. Last but not least, I'm able to experience the full SDLC of a project and it will be greatly useful for future real-life projects.