| Feb, 2007 | Quality Assurance - Testing User Acceptance Testing (UAT) May 20, 2008 Craig Allgood,...

| Feb, 2007 | Quality Assurance - Testing

User Acceptance Testing (UAT)

May 20, 2008

Craig Allgood, CSQECIBER – Sr. Consultant

IBM Global Services

Quality Assurance - Testing2

User Acceptance Testing (UAT)

Simply Put: UAT is the final testing performed by the User with the expectation that the User will

accept the system as fit for purpose Some say it is when:

To see how the product handles real-life scenarios To verify the solution against the business objective

We All Perform UAT – Buying a Car Fit for purpose

Size Towing No major blemishes Age of the car Warrantee Budget Gas mileage

Expectations Wheels Brakes Door handle

User Acceptance Testing - UAT

IBM Global Services


Agenda

Introductions

Types, Perspectives and Contents

UAT Tension and Being Proactive

Be Organized

Know the Risks and Priorities

Expect Issues


IBM Global Services


IntroductionsCIBER:

Systems Integration Consultancy (custom and ERP environments) Work with Public and Private sectors Outsourcing (on and off-shore) Project and strategic staffing

Craig Allgood CIBER Raleigh’s QA and Test Thought Leader Managing test efforts for various types of testing FDA, GMP, and SEC regulations Lifecycle Process Improvement


IBM Global Services


Types of UAT

Performed by User: Traditional UAT Business Analyst or Testers creates the test cases Test are performed by Users

Beta Performed by Users Mutual understanding that the product may have issues May focus on parts of the application, not the entire product Typical when releasing large, external corporation websites

Demo Performed in front of the User or Executive team Walk-through format Allows immediate, in-person feedback More control in the hands of the presenter (could easily turn into a “sales” job) Could serve as introductory training Service Readiness Testing (people, processes and tools)


IBM Global Services


Perspectives and Content of UAT

Perspectives: User/Client Business Analyst (BA) Project/Test Management IT (SW Development and Infrastructure Implementation)

Content of UAT Software and Hardware

Functions properly Look and Feel Input and output Fit for purpose Ease of Maintenance

Users Manuals and Training Aids Meaningful Accurate

User’s/Client’s Confidence (non-visible) Were they comfortable during the build process? Confidence with the build team and management


UAT is not a battle; it is a common approach where all involved must strive to achieve successful closure

IBM Global Services


UAT Tension

UAT can result in various types and levels of Tension:

Users Users are nervous about performing UAT Users are upset that their product is changing (change usually results in fear) If development is happening with little BA or User insight, they become more

apprehensive about the change Lack of confidence in the Development effort can lead to an ideal of “No Acceptance”

by the User or BA “This doesn’t meet our needs. What is this mess!”

Developers, PMs and Testers Sometimes feel that the User doesn’t know about the new product and therefore will

block out the User Can focus too much on the deadlines and divert from the User’s needs Same defects logged over and over “Well that’s what you asked for!”


IBM Global Services


Be Proactive

Desires for a Successful UAT: User involvement High confidence in the product High confidence in the development team Business knowledgeable Users No surprises No process tension

Proactively Obtain Desires Before Start of Testing Start preparing early Create scenarios/test cases with the involvement of the Users

Do not allow the development team to create these Users provide the most “real-life” input

Encourage a sense of ownership within the User Early involvement Familiarity with Business and Design Specifications

Work with and involve the User throughout the development Be accepting of User feedback in early stages Display confidence in the product and let the User know it is there to serve them Simple format to allow Users to focus on the product

Users are not typically from testing or quality backgrounds Cumbersome process = Frustration = Lack of product focus


IBM Global Services


Be Organized

Being Organized Raises User confidence in the product Raises User confidence in the development team Displays control and keeps of UAT Eases the tracking of tests and issues for both sides Reduces hostility Keep the process simple

Organization Methods Standard format of

Tests Interactions (minutes, status, reporting)

Breakdown of specifications to daily use of the product Classification of tests

Areas and functions Priorities and risk

Assigning tests Keep testing under control (individual and time basis) Discourage “free range testing” Will reduce repetition of issues logged

Classification of issues Track the status of tests and issues (reporting) Periodic meetings and effective implementation of actions from those meeting


IBM Global Services


Know the Risks and Priorities

Understanding the Risks and Priorities Simply makes life easier Allows the development team and the User to focus on key areas Gives a guideline for setting priorities on tests, issues and functional areas of the

product Raises User confidence in the development team because the understand the risks Can improve the organization of interaction and documentation

Risks During UAT Product Risks

Business risks Internal or external application Standards to adhere to (FDA, SEC)

Cost of faults Complexity of the product

UAT Risks Misinterpretation of requirements Hostility between the User/client and provider Lack of User dedication to UAT Group members moving on to the next project before UAT is complete


IBM Global Services


Expecting Issues

Issues and Defects Happen Nothing is perfect Do not get defensive Have a plan for tracking and resolving

Ensure all parties understand this plan Classify all issues (priority, area, risk) UAT is not the time to find out that the solution does not meet the business objectives

Too late at this point Should follow this along the way

Defect and Issues Tracking Keys Recreation details Actions Owners Verification Publication and constant review Ease of access to log


Submitted

ClosedVerified

ResolvedWorkingAssigned

Defect lifecycle

IBM Global Services


Conclusion

UAT is something we do everyday, whether we realize it or not

UAT can include the product, people, processes and tools

UAT sets the final lasting impression

An organized UAT will raise User confidence and ease tension

A controlled UAT will keep the focus on the product

Keep the process simple

Keep all informed throughout the process

Get the User involved early in the development cycle and keep them involved


| Feb, 2007 | Quality Assurance - Testing

Thank you

User Acceptance Testing - UATQIT - May 2008

| Feb, 2007 | Quality Assurance - Testing User Acceptance Testing (UAT) May 20, 2008 Craig Allgood,...

Documents

Transcript of | Feb, 2007 | Quality Assurance - Testing User Acceptance Testing (UAT) May 20, 2008 Craig Allgood,...