HeaderSIS.jpg

2011T1 Victorious Secrets Mid-Term Wiki Page

From IS480
Jump to navigation Jump to search

Project Progress Summary

Project Highlights

The individual workload on the project has increased substantially since the starting of the school term as we have to juggle both the project and other course subjects. We experienced short of hands when we were conducting User Acceptance Test where half of the four-person team were dedicated to design test plans, test scripts, and gather list of testers while the other half of them continued on application development, managing project progress and documenting various project artifacts. To ensure the team deliver the project with good quality and on time, we have made changes to our project management styles and constantly revised our scope, task status and interacted consistently with our client and supervisor such that we are both efficient and task-oriented!


  • Change in project management style

Part of the SCRUM methodology which was adopted by our team is to have daily stand-up meetings where members will physically meet up and brief each other on the progress of assigned tasks and highlight any issue to the team which may impede the project progress. Nonetheless, the stand-up meeting is rather time-consuming and inconvenient, so we decided to reduce the frequency of stand-up meeting to every three days, excluding our weekly formal meetings. We also developed a concept called remote daily scrum update where each member will compile up things such as work progress and issue status and email to other team members. In this way, we are able to discover new issues easily and it works cohesively with our project management portal. For meetings, we used to have two formal meetings per week, and now we learned to combine the 2nd meeting (usually happens on Friday) with our client meeting every two weeks. During the client meeting, we will first update client on our project status, show him the latest prototype with the new features and gather feedback. After that, we will work with client to gather test requirements for the modules to be developed for the next sprint. Once the client left, our team will review internally on our progress over the past sprint. Following that. we will have sprint planning meeting for the next sprint and created tasks in our project management portal in order to track our project progress.


  • Change in project requirements & technologies with better substitues

We decided to implement Facebook style comments and displays for our Group and Forum module under the client's request. We reworked our portal's theme design to have a mixed of our proposed design (white and dark themes). We implemented dynamic Google site translation first instead of static content internationalization which now supports more than 20 languages. The advantage of doing this is that the entire site content can be translated on the fly whereas the static content translation is much laborious and do not translate user posted contents. However, we are still in the process of deciding whether to remain the static translation feature as it provides better accuracy for key information but it would require cohesive effort from the community to improve on its usefulness. We have also replaced our Mibbit IRC chat which has already been customized and integrated with a new "Envolve" chat feature. The latter is much more powerful and supports more features such as creating private chat topics, invite people online to the chat group as well as public chats. The new chat also has better view design as the chat box can be minimized at the bottom of the browser window or open in a new window whereas the original IRC chat do not have such flexibility. The new chat also support cool features such as dynamic translation where a message will be auto-translated into the language detected from the browser.


  • Change in member roles & work progress

To cope with the growing workload, our team members have shifted our spectrum and learn to take up different roles in our project activities. While each of us does part of the programming, We have a niche area that each other focuses at. For example, when we develop a new functional module, the chief programmer will help to digest the requirements and sub-divided them into separate functional requirements. Similar for design and testing, the key member in the team will have to detail what are the necessaries steps needed to carry out in order to complete a certain task. One member may be gather user for UAT under the Tester's request, the other may be doing Photoshop design to help speed up the work of the designer. The chief programmer may also suggest how the site's theme can be better integrated to enjoy more vibrancy. Sometimes we will also rotate our roles and pair up, a good example will be preparing UAT documents and project artifacts which often involve two members at a given point of time.

In terms of programming, we have developed a workflow to streamline our coding practices. Since we are building our portal using Drupal, we have the flexibility that each of us can be designated to complete certain functionality by ourselves without delaying the team's progress. A member can be tasked to test out a third party module which has not been fully supported but may potentially meet our project requirement. He will first create a task ID with description in our project management portal he proceeds with testing and development of the module with our latest deployed prototype. If a bug has been found, he will have to examine the code of the contributed module in Eclipse and tries to debug the issue at the first place. If the bug has not been solved in the given time period of the sprint, the member will assign it to others who are available to continue working on the issue or and start off looking for alternative solutions. The process is similar for other project activities such as debugging, design, developing optional features etc. Once a member think that the issue has been solved, he will update issue status on project management portal as resolved, and commit any code change to subversion with the attached task-ID. One advance feature we have is that if the member writes the subversion commit log message that mentions keywords such as "Ref No: 145 by XX: Issue is RESOLVED", our project management portal will automatically update the task status since the management portal and subversion are located on the same server.


Project Management

Project Status

Functional Module Task Status Confidence Level (0-1) Comment
Account Registration & Login Completed 100% & Tested in UAT 1.0 Account registration is only enabled for member role
Portal Forum Completed 100% & Tested in UAT 0.9 Minor bug fix
Portal Event Organizer Completed 100% & Tested in UAT 1.0 Plan to research more websites for external event aggregation
School & Course Review Completed 100% 1.0 Implemented activity stream to feature latest posts
School Search Completed 80% 0.9 Plan to improve on the usability of school filter by changing layout
Social Networking Features Completed 100% & Tested in UAT 1.0 This feature includes personalize profile, join groups, add friends, upload documents, live-chat & in-site message
Multi-language Support Completed 100% 1.0 Implemented Google translate API which now supports more than 20 languages
Content Personalization Completed 20% 0.7 This module has the highest technical complexity in our portal & will be our key forum in the coming sprint
Publishing Workflow Completed 50% 0.8 Implemented for event creation and internally tested. The remaining work is to implement for advertisement submission
Mapping Not Started 0.5 Plan to research more into Google Map API
Social Media Integration Completed 100% 1.0 Supports Facebook, Twitter, Digg and other 40+ social media tools to share site contents
E-mail Notifications Completed 100% 0.8 Supports account activation, in-site message notification & site invitations
Advertisements Not Started 0.6 Improving on the design and layout of page columns to dedicate to advertisements


Project Schedule (Plan VS Actual)

Sprint Iterations Planned Completion Date Actual Completion Date Comment
Sprint 5 Develop social networking module 26th August 2011 26th August 2011 Completed as planned
Implement Mibbit IRC Chat 26th August 2011 Replaced Mibbit IRC Chat with Envolve Chat 2nd September 2011 Postponed to Sprint 6
Develop publishing workflow 2nd September 2011 30th September Postponed to Sprint 7
Sprint 6 Continued development for forum and implemented Envolve Chat system 2nd September 2011 Code revision for UAT
Develop internationalization for multi-language support 2nd September 2011 Implemented multi-language support using Google translate API 2nd September 2011 Swapped technology and completed as planned
UAT 1 Prepare UAT Test Plan & Test Script 5th September 2011 7th September 2011 Revised test scripts after internal testings
Conduct off-site UAT with volunteers 9th September 2011 11th September 2011 Some volunteers did not return completed test scripts on time
Code & UI revision 16th September 2011 16th September 2011 Managed to fixed bugs found as planned and postponed to UI revision to UAT II
Sprint 7 Develop Mapping & Advertisement 30th September 2011 Added in publishing workflow 30th September 2011 Currently in Progress
Prepare for Mid-term Presentation & mid-term wiki section 26th September 2011 The content of presentation and wiki will be liable to the overall progress of the project


Project Metrics

As a Scrum team, we implemented a few metrics measurements to assist us in managing the project in terms of predictability, quality, predictability and value. Our team believes that a good metric will be something that can effective gauge and reflect our team's progress as well as providing useful insights for us to improve on our performance and regulate our scope of project such that a good final product can be delivered on schedule.


Sprint Completion Bar (Productivity Metric) - measuring sprint points using a stacked bar with 3 elements of Open (lighter Green) and Closed (Darker Green) and white (issue created but not started). Each element is presented in a separate color. The stacked bar shows work sprint over sprint. Longer Done bars is a good indicator. Longer Not started or Open is a poor indicator. By end of the sprint, open tasks will be shifted to the following sprint and any tasks which is deemed unfeasible will be treated as waste - as defined by work that was subsequently removed due to not needed. If there are too many wastes, it represents a poor indicator of our task planning. If there are too often or many open tasks which are shifted to later sprints, it indicate that we are falling behind schedule or the scope is to big. This serves as a warning for us to reduce the scope the project with client and reschedule our project task sprints. [Sprint Completion Bar]


Development Velocity / Sprint Burn-down Chart (Predictability Metric) - Velocity is measured by the number of story points (we assigned story points to tasks depending on the expected number of man-hours / complexity of the task) completed per sprint against the planned story points to be completed. It helps us to gauge the consistency in the productivity throughout the sprint. Most of the time, we will use the velocity together with the sprint burn-down chart which measures both velocity and scope change throughout a sprint as a measure of meeting a set goal. The number of remaining story points serve as a basis for us to predict if we will be able to complete assigned tasks with the given time frame. If the story points is not completed as fast as we expected or when the actual production line falls far off from the planned production line, the team will respond immediately by relocating man-power as well as reschedule tasks to be completed in the following sprint to allow buffer time for amendments.

The chart is plotted based on the number of story points which has not been resolved as well as the number of remaining hours. The ideal is the burn rate which is optimal for the team and the team shall aim to achieve this burn rate throughout all the sprint development cycles.The horizontal axis is the number of days in a planned sprint (excluding weekends) and the number of remaining hours is calculated based on the remaining days in each sprint. The story points to be completed in each sprint is calculated by subtracting the story points at the top left corner with the story points at the top right corner.

BurnDown Chart


Team Satisfaction Metric (Value Metric) - The satisfaction is introduced to gauge the quality of team's work completed by the end of every sprint development. Each member of the team is asked to give a rating on his evaluation of the team's work done over the past sprint on a scale of 1 to 7 from extremely dissatisfied to extremely satisfied. The average score from all members will be evaluated and actions will be taken by the project manager. The goal of the metric is to encourage each member to work hard as well as providing an alert signal to the team on the quantity and quality of work completed during each sprint. Since the score will be normalized across the sprints and average has been taken from all the members, it shall serve an useful indicator for monitoring the team's over performance and raise the team's morale when everyone is generally satisfied with the team work.


Project Risks


Technical Complexity


Quality of Product

Intermediate Deliverables

Category Description Deliverable
Project Management Team Meeting Minutes [Team Meeting Minutes]
Client Meeting Minutes [Client Meeting Minutes]
Supervisor Meeting Minutes [Supervisor Meeting Minutes]
Sprint Progression Bar [Sprint Completion Bar]
Sprint Burn Down Chart / Velocity Points Sprint Burndown Charts
Team Satisfaction Metrics
User Requirements and Analysis Use Case Diagram [Use Case Diagrams]
User Stories [User Stories]
UI Mock-ups UI Mock-ups
Design Application Architecture Design Application Architecture Diagram
Portal Theme Design

Theme A, Theme B

Testing Portal User Manual User Manual
UAT 1 Test Plan UAT Test Plan
UAT 1 Test Script UAT Test Script
UAT Bug Tracker Bug Tracker


Deployment

Live Portal


Testing

UAT I

UAT I Test Plan

Currently, our team has several functionalities completed, including Register, Login, Forum, Social Networking and Events. In order to simulate the test response as close to the final end users as possible, we have approached our project sponsor to help gather testers for our UAT 1. Due to certain sponsor constraints, we have decided to hold an offline UAT this time round. We plan to conduct an onsite testing for the next UAT, UATII.

Functionality Tested:

  1. Login
    1. Successful Kogin
    2. Warning Messages for Login Failure
  2. Social Networking
    1. Create Group
    2. Request & Accept Group Membership
    3. Post Content on Group Wall
    4. View and Edit User Profiles
    5. Add Friend & Accept Friend Request
    6. View Friends list
    7. Send and Receive Private Message
  3. Events
    1. View List of Event Details
    2. Sign-up for Event
    3. Create Event
    4. Event Invitation
  4. Forum
    1. Post Thread
    2. Reply Thread

Testing Period: 0000hr Wednesday 7th September to 2359hr Saturday 10th September
Time required: 1 to 2 hours
Total Number of Testers: 10

Plan

  1. Test Preparation
    1. Prepare UAT test script (test scenarios covering functionalities to be tested)
    2. Prepare user feedback form
    3. Prepare user manual for testers’ reference
    4. Prepare test instructions
    5. Prepare test accounts
  2. Internal testing
    1. Internal testing by all team members
    2. Amend and edit test cases
    3. Fix minor bugs/UI
  3. Test Execution
    1. Send test instructions, test script and user manual to testers
    2. Test execution by testers
    3. Send completed test scripts and user feedback form back to project team
  4. Results Collection
    1. Collate all test results and identify Failed test cases
  5. Review and Code Fix Planning
    1. Review failed test cases and identify bugs
    2. Review priority and assign bug fix schedule
    3. Code fixing

UAT Schedule - Planned vs Actual

Sprint Iterations Planned Completion Date Actual Completion Date Comment
UAT 1 Prepare UAT Test Plan & Test Script 5th September 2011 7th September 2011 Revised test scripts after internal testings
Conduct off-site UAT with volunteers 9th September 2011 11th September 2011 Some volunteers did not return completed test scripts on time
Code & UI revision 16th September 2011 16th September 2011 Managed to fixed bugs found as planned and postponed to UI revision to UAT II


UAT Bug Tracker

Program bugs will be recorded and reviewed periodically. Urgent bug reviewing meeting will be scheduled depending on the number of bugs and the urgency of bug to be resolved

UAT I Actual Test Details

Testers' Profiles
As mentioned, we aimed to keep the test environment as close to actual usage in Production. As seen in the table of testers' profile below, 60% of testers are international students, the actual intended user group.

S/N Tester Name Age Nationality Occupation
1 Myint 24 Burmese Student
2 Vyshnavi 18 Indian Student
3 Wen Wen 19 PRC Chinese Student
4 Suphasit 18 Thai Student
5 Nirma 17 Nepalese Student
6 Gerard 27 Filipino IT Executive
7 Esther 26 Singaporean Co-sponsor
8 Jonathan 32 Singaporean Project Sponsor
9 Leng Ruo Wei 24 PRC Chinese Student
10 Victor Lau 22 Singaporean Student


Test Accounts Allocation

Test Accounts have been created for each tester individually to stream-flow the test execution process. Every user has been given three sets of accounts with different roles and preassigned group name and event name to complete the all planned test cases.

S/N Tester Name Tester ID Login Set Username Password Primary Role Secondary Role Group Name Event Name Remarks
1 Myint Tester 1 Set 1 user1001 user1001 Member Group Owner UATGROUP11 UATEVENT11 Group Owner of UATGROUP11
2 Myint Tester 1 Set 2 user1011 user1011 Member UATGROUP11 UATEVENT11 Request membership to UATGROUP11
3 Myint Tester 1 Set 3 user1021 user1021 Member UATGROUP11 UATEVENT11
4 Vyshnavi Tester 2 Set 1 user1002 user1002 Member Group Owner UATGROUP12 UATEVENT12 Group Owner of UATGROUP12
5 Vyshnavi Tester 2 Set 2 user1012 user1012 Member UATGROUP12 UATEVENT12 Request membership to UATGROUP12
6 Vyshnavi Tester 2 Set 3 user1022 user1022 Member UATGROUP12 UATEVENT12
7 Wen Wen Tester 3 Set 1 user1003 user1003 Member Group Owner UATGROUP13 UATEVENT13 Group Owner of UATGROUP13
8 Wen Wen Tester 3 Set 2 user1013 user1013 Member UATGROUP13 UATEVENT13 Request membership to UATGROUP13
9 Wen Wen Tester 3 Set 3 user1023 user1023 Member UATGROUP13 UATEVENT13
10 Suphasit Tester 4 Set 1 user1004 user1004 Member Group Owner UATGROUP14 UATEVENT14 Group Owner of UATGROUP14
11 Suphasit Tester 4 Set 2 user1014 user1014 Member UATGROUP14 UATEVENT14 Request membership to UATGROUP14
12 Suphasit Tester 4 Set 3 user1024 user1024 Member UATGROUP14 UATEVENT14
13 Nirma Tester 5 Set 1 user1005 user1005 Member Group Owner UATGROUP15 UATEVENT15 Group Owner of UATGROUP15
14 Nirma Tester 5 Set 2 user1015 user1015 Member UATGROUP15 UATEVENT15 Request membership to UATGROUP15
15 Nirma Tester 5 Set 3 user1025 user1025 Member UATGROUP15 UATEVENT15
16 Gerard Tester 6 Set 1 user1006 user1006 Member Group Owner UATGROUP16 UATEVENT16 Group Owner of UATGROUP16
17 Gerard Tester 6 Set 2 user1016 user1016 Member UATGROUP16 UATEVENT16 Request membership to UATGROUP16
18 Gerard Tester 6 Set 3 user1026 user1026 Member UATGROUP16 UATEVENT16
19 Esther Tester 7 Set 1 user1007 user1007 Member Group Owner UATGROUP17 UATEVENT17 Group Owner of UATGROUP17
20 Esther Tester 7 Set 2 user1017 user1017 Member UATGROUP17 UATEVENT17 Request membership to UATGROUP17
21 Esther Tester 7 Set 3 user1027 user1027 Member UATGROUP17 UATEVENT17
22 Jonathan Tester 8 Set 1 user1008 user1008 Member Group Owner UATGROUP18 UATEVENT18 Group Owner of UATGROUP18
23 Jonathan Tester 8 Set 2 user1018 user1018 Member UATGROUP18 UATEVENT18 Request membership to UATGROUP18
24 Jonathan Tester 8 Set 3 user1028 user1028 Member UATGROUP18 UATEVENT18
25 Leng Ruo Wei Tester 9 Set 1 user1009 user1009 Member Group Owner UATGROUP19 UATEVENT19 Group Owner of UATGROUP19
26 Leng Ruo Wei Tester 9 Set 2 user1019 user1019 Member UATGROUP19 UATEVENT19 Request membership to UATGROUP19
27 Leng Ruo Wei Tester 9 Set 3 user1029 user1029 Member UATGROUP19 UATEVENT19
28 Victor Lau Tester 10 Set 1 user1010 user1010 Member Group Owner UATGROUP20 UATEVENT20 Group Owner of UATGROUP20
29 Victor Lau Tester 10 Set 2 user1020 user1020 Member UATGROUP20 UATEVENT20 Request membership to UATGROUP20
30 Victor Lau Tester 10 Set 3 user1030 user1030 Member UATGROUP20 UATEVENT20


UAT I Test Cases

S/N Functionality Feature Test Steps Expected Results
1 Login Login Unsuccessful 1) Click on "Login".

2) Enter Set 1 Username, without Password.
3) Click "Login" button.

Error message will appear after re-load: "Password field is required."
2 Login Login Unsuccessful 1) Click on "Login".

2) Enter Set 1 Username, with Password: wrong123
3) Click "Login" button.

Error message will appear after re-load: "Sorry, unrecognized username or password."
3 Login Login Successful 1) Click on "Login".

2) Enter Set 1 Username and Password.
3) Click "Login" button.

Log in is successful and Set 1 username appears on top panel
4 Social Network Create Group 1)Hover mouse over "Community".

2) Click on "Groups".
3) Click on "Create group".
4) Enter "UATGROUPXX" in Name field, where UATGROUPXX = assigned group name.
5) Enter "UATGROUPXX" in Description field, where UATGROUPXX = assigned group name.
6) In the Group Options, select "Moderated" radio button under Membership Requests.
7) Click on "Save" button.
8) Click on "Log Out".

7) Confirmation message will appear after re-load: "UATGROUPXX has been created.", where UATGROUPXX = given group name.

Group homepage will be displayed.

5 Social Networking Request Group Membership 1) Log in with Set 2 user account and password

2) Hover mouse over "Community".
3) Click on "Groups".
4) Locate assigned group name and click on "Request Membership".
5) Enter "I want to join the group!" in Additional Details textbox.
6) Click on "Join" button.
7) Click on "Log Out".

Confirmation message will appear after re-load: "Membership request to the UATGROUPXX awaits approval by an administrator.", where UATGROUPXX = given group name.
6 Social Networking Accept Group Membership Request 1) Log in with Set 1 Username and Password.

2) Hover mouse over "My Stuff".
3) Click on "My Groups".
4) Click on group name. (notice notification message on top of the screen)
5) Click on "here" in notification message on top of the screen.
6) Click on "Approve" for Set 2 username's membership request.
7) Click on "Log Out".

4) Notification message will be seen: "There are currently 1 pending membership requests. Click here to view them.".

5) Tester should see a membership request by Set 1 username.
6) Confirmation message should be displayed after re-load: "Membership request approved."

7 Social Networking Post Content on Group Wall 1) Log in with Set 2 username and password

2) Hover mouse over "My Stuff".
3) Click on "My Groups".
4) Click on group name.
5) Enter "Singapore is a beautiful country" in textbox.
6) Click "Share".
7) Click on "Log Out".

3) Tester should see assigned group in the list of groups

6) Set 2 username will be shown to have posted "Singapore is a beautiful country", "a moment ago". It will be the latest post on the group wall, appearing right on the top of the list.

8 Social Networking View own user profile 1) Log in with Set 1 Username and Password.

2) Click on "My Account".

Tester should be able to see the list of most recent activity of Set 1 user.
9 Social Networking Edit own user profile 1) Click on "My Account".

2) Click on "Edit my profile" on left-side panel
3) Click on "Personal Information" tab
4) Enter "Singapore" in Location field.
5) Enter "Study" under My Interests field.
6) Click on "Save".
7) Click on "My Account" link on top panel
8) Click on "About" tab

6) Confirmation message should be displayed after re-load: "The changes have been saved."

8) Tester should be able to see the following details:
Name: <userXXXX>
Location: Singapore
My Interests: Study

10 Social Networking View other users' profile details 1) Hover over "Community".

2) Click on "Members".
3) Select Set 2 username.
4) Click on "About" tab to view profile.

Tester should be able to see the name of the user, <userXXXX>, where userXXXX = Set 2 username
11 Social Networking Add friend 1) Hover over "Community".

2) Click on "Members".
3) Select Set 2 username.
4) Click on "Become <userXXXX>'s Friend".
5) Enter "International Student Convention" under Elaboration.
6) Click "Send". (take note of confirmation message)
7) Click "Log Out".

Confirmation message should appear after re-loading: "Your Friend request has been sent to <userXXX>."
12 Social Networking Accept Friend Request 1) Log in with Set 2 Username and Password.

2) Hover mouse over "My Stuff".
3) Click on "My Profile".
4) Click on "Friend Requests".
5) Click "Approve" for friend request from Set 1 username.
6) Click on "Yes" on loaded form.

Tester should see a "(1) behind "Friend Requests".

Confirmation message should appear after re-loading: "<userXXXX>'s Friend request has been approved."

13 Social Networking View friends 1) Hover mouse over "My Stuff".

2) Click on "My Friends".

Set 1 user should appear as a friend.
14 Social Networking Send private message 1) Hover mouse over "Community".

2) Click on "Members".
3) Locate and click on Set 3 username.
4) Click on "Send Message".
5) Enter "Hello" in Subject textbox.
6) Enter "How are you?" in message textbox.
7) Click on "Send Message".
8) Click on "Log Out".

Confirmation message should appear after re-loading: "A message has been sent to <userXXXX>."
15 Social Networking Receive private message 1) Log in with Set 3 Username and Password.

2) Click on Notification message on top panel.
3) Click on Subject "Hello".
4) Click on "Log Out".

1) Notification message appears on top panel: "You have a new message! Click here to read it."

2) Message inbox will show private message from Set 2 user.
3) Message "How are you?" should be displayed.

16 Events View List of Events 1) Log out of Set 2 user account

2) Log in with Set 1 username and password
3) Hover mouse over "Community"
4) Click on "Events"

Tester should see a list of events on the Events homepage.
17 Events View event details 1) Click on "The Lion King" Tester should be able to see "The Lion King" event details in the event page.
18 Events Sign-up for event 1) Click on "Sign up for The Lion King" at the bottom of the page

2) Do not change any information in the text fields, click on the "Sign up" button.

1) Tester should see a default email in the Email Address field, and their given Set 1 username in the Name field.<>br

2) Confirmation message should be displayed after re-load: "Signup to The Lion King confirmed. A confirmation email will be sent shortly containing further information about this Event."

19 Events Create Event 1) Select "Event" from dropdown list on right panel.

2) Click on "Create" button
3) Enter provided Event name into Title textbox
4) Enter "Exciting updates soon" in Description textbox
5) Select "Education" from Events list
6) Click on "Event Details" from Selection panel
7) From date: Select 19th September 2011 from Calendar, 12:00PM
8) To date: Select 20th September 2011 from Calendar, 12:00PM
6) Click on "Save" button
7) Click on "Log Out"

2) New event creation page should load

6) Confirmation message should be displayed after re-load: "Event XXX has been created." where XXX = given event name
Tester should see the event page with the event details previously entered.

20 Forum Create thread 1) Log in with Set 1 Username and Password.

2) Hover mouse over "Communities".
3) Click on "Forums".
4) Click on sub-forum "Accomodation".
5) Click on "new topic".
6) Enter "<userXXXX> thread" in Subject text field, where userXXXX = Set 1 username
7) Enter "Hello I am in Singapore" in message body text field.
8) Click on "Submit".

Tester should see a new thread with Thread Title "<userXXXX> thread" and message "Hello I am in Singapore", where userXXXX = Set 1 username.
21 Forum Reply thread 1) Log out of Set 1 user account

2) Log in with Set 2 Username and Password
3) Hover mouse over "Communities".
4) Click on "Forums".
5) Click on sub-forum "Accomodation".
6) Click on Set 1 username's thread
7) Click on "Post reply".
8) Enter "<userXXXX> reply" in message body text field.
9) Click on "Submit".

Tester should see the thread with 1 new reply with message "<userXXXX> reply", where userXXXX = Set 2 username.
UAT I Test Results

Out of 21 test cases, only 1 test case had testers indicating failure. This give a 95% UAT pass rate. This high pass rate provide our team encouragement on our good work done till date. However, we are aware that a high pass rate does not necessary indicate a successful UAT. We encountered several problems in the course of conducting our UAT I. The problems encountered serve as lessons learnt and room for improvement in our next UAT.

Firstly, we did not plan well enough for our UAT preparation. We spent more time than expected in doing up all the test cases, and at the same time ensuring that our site is "fit" for UAT. There were the existence of minor bugs which were discovered in the course of constructing the test cases, therefore delaying our time spent on UAT preparation.

Secondly, an offline UAT presented to us some limitations. We found it difficult to coordinate with our testers. First of all, because it was an offline UAT, we had to thoroughly make sure that the test script is clear and coherent enough for all testers to understand and follow. We also faced the issue of getting testers to complete the UAT within the 3 days allocated test duration. We finally received 80% of our test scripts back after approximately 1 week. We were unable to get results from all testers who volunteered their help at the end of the day.

Thirdly, we were unable to witness for ourselves how the testers went through their test scripts and therefore our observations were only limited to the test scripts they sent back.

Last but not least, due to the unforeseen circumstances, our team felt that we should have requested for more testers instead of limiting ourselves to only 10. The sample size of our test results now remain small, and we would have benefited much greatly with more user feedback and suggestion.

On a positive note, our team did well in ensuring that all test instructions, including the test script, was written clearly and coherently. Most of our testers feedback that the test instructions were clear and easily understood.

Improvements to UAT

With the lessons learnt as mentioned above, we will be including the following improvements and changes in our next UAT, UAT II.

  1. Conduct an onsite UAT 2 to allow us to observe testers
  2. Allocate more time for UAT Preparation
  3. Gather a bigger pool of UAT testers


Reflection

Team Reflection

Individual Reflections

Return to Wiki Home Page

[Return to Wiki Home Page]