Difference between revisions of "IS480 Team wiki: 2012T2 box.us Final"
Qyang.2010 (talk | contribs) |
|||
Line 308: | Line 308: | ||
==== Technical Understudy ==== | ==== Technical Understudy ==== | ||
+ | * We conducted a technical understudy with Empact's technical understudy (Sophie) and our client (Peter Yang) | ||
+ | * <i>Lesson Plan</i>: [https://docs.google.com/document/d/1ThTnpcv1w_yNPwfVDFWglSYk3OpaI4CAzRl5OenLk8Y/edit?pli=1 Lesson Plan on Google Docs] | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |+ | ||
+ | |- | ||
+ | ! scope="col" width="300" style="background:#810541; color:#ffffff"|Session 1 | ||
+ | ! scope="col" width="300" style="background:#810541; color:#ffffff"| Session 2 | ||
+ | |- | ||
+ | |||
+ | || 29 Mar 2013, 1600hrs-1800hrs | ||
+ | || 12 Apr 2013, 1930hrs-2145hrs | ||
+ | |- | ||
+ | |||
+ | || Session Contents: | ||
+ | * Application Structure | ||
+ | * Database Structure | ||
+ | * Flow of Login/Logout Process | ||
+ | || Session Contents: | ||
+ | * Code walkthrough of Specific Scenarios that Empact requested | ||
+ | * Question and Answer | ||
+ | * Clarification on Session 1 | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |} | ||
==== Handing Over Day ==== | ==== Handing Over Day ==== |
Revision as of 15:09, 21 April 2013
HOME | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Contents
Project Progress Summary
What Is This Project About?
Check out our 1 min ++ video pitch to find out what this project is about at Youtube
Quick Links
Final Presentation Slides: coming soonDeployed Site: Empact ACTDemonstration Site: Empact ACT(Staging)Initial Proposal: Proposal |
---|
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 |
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 | 31 |
Increase in Bug Score due to bugs that were recorded from User Testing 2
|
12 | 16 |
New features of the system(Statistics, Dashboard and Notifications) were being released
|
13 | 58 |
More thorough testing was being performed for the UAT
|
SCHEDULE METRICS
- Schedule: Schedule on Google Docs
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
We release 4 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 |
|
04/04/2013 |
Release 0.4 |
|
04/04/2013 |
Release 0.5 |
|
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.
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
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 | |
Design and Technical Specifications | ||
Code | ||
Deployment Diagram | instructions |
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:
Release 0.1 |
---|
Key Changes
|
Feedback Collected
|
Release 0.2 |
---|
Key Changes
|
Feedback Collected
|
Release 0.3 |
---|
Key Changes
|
Feedback Collected
|
Release 0.4 |
---|
Key Changes
|
Feedback Collected
|
Release 0.5 |
---|
Key Changes
|
Feedback Collected
|
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:
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: Bringing together people from different walks of life together to work on an IT project has sharpened my skills in handling with people and being more cognisant of people management issues and how to deal with group cultures and team norms
- Evaluating IT project ideas: FYP has taught me how to be aware of what are the current issues facing IT projects. It has taught me how to evaluate these and adopt a T-model by being able to think about what are the broad issues that are going to affect IT decisions and what are the deep issues that are specific to the issue being raised.
- Time Management Skills: FYP has taught me to be aware of the time that I spend managing the team, managing my own workload within the team and juggling my workload with my other modules that I was taking in school.
- Client Negotiation skills: I was able to apply the negotiation skills that I learnt from a module to achieve integrative outcomes for the client and the team, and what are the tactics that are readily available to deal with such situations.
- Applied Project Management Skills: The FYP experience has been an extension of what I have learnt in Software Engineering and I was able to refine my skills in scope management, schedule management and further extend the practicality of metrics being used within a project.
Sherrie
I started with a very simple learning outcomes - to learn life skills that were above and beyond exams/textbook as well as to apply what my education in SMU has taught me so far.
In my opinion, i have achieved that. However, the most valuable lesson for me was learning to deal with changes. In SMU, all our projects has a clear defined scope that stays constant from beginning till the end. But through this FYP, changes was probably the only constant (on top of dedicated team mates who were always there to go through each storm). Managing never ending changes was certainly not just about a "can or cannot" mindset. It really required me to understand the fundamental reasoning behind the changes requested and understanding it from a business view point.
With regards to my education, in a bigger picture, I have been able to apply the following
- Understanding and improving business processes: i was able to leverage on the knowledge I've acquired in Process Modelling and Solution Blueprinting (PMSB) to help out in understanding the business process of our client. In addition, I was able to give opinions on how the process could be more efficient.
- Understanding how IT and business value - As I had just completed Advanced Information Systems Management (AISM) I was able to apply the concepts of how IT can be an enabler and contribute in adding business value to an organisation.
- Presentation skills - In Management Communication (MC) we were taught how clear communication is essential be it verbal or presentation. I was able to apply skills I learnt from that module when communicating with clients, team mates or presentation.
Wai Mun
As this FYP is coming to an end, these are the few learning points that i am taking it away:
- Time managment : Time management is very important as usually FYP work takes up a bulk of my time. Hence, it is very important for me to plan my time well for my other activities and my studies.
- Usability learning journey : My usability learning journey is interesting and exciting as i get to know more knowledge on usability through Interaction Design and Prototyping. It is definitely a good module to take as it complements very well with FYP.
Sponsor Comment:
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.