Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
121 views8 pages

Edw Uat: Adding & Executing Uat Scenario - Process

The document outlines the process for adding, executing, and documenting UAT scenarios and observations using Microsoft Teams. It details how business users and product owners add scenarios and document observations, and how the EDW team triages issues, analyzes root causes, resolves defects through code or data changes, and has business users retest. Responsibilities are assigned between business users and the EDW team for scenario documentation, test execution, observation documentation, triage, root cause analysis, and retesting once an issue is resolved.

Uploaded by

sri1998
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
121 views8 pages

Edw Uat: Adding & Executing Uat Scenario - Process

The document outlines the process for adding, executing, and documenting UAT scenarios and observations using Microsoft Teams. It details how business users and product owners add scenarios and document observations, and how the EDW team triages issues, analyzes root causes, resolves defects through code or data changes, and has business users retest. Responsibilities are assigned between business users and the EDW team for scenario documentation, test execution, observation documentation, triage, root cause analysis, and retesting once an issue is resolved.

Uploaded by

sri1998
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

EDW UAT

ADDING & EXECUTING UAT SCENARIO - PROCESS


Adding & Executing UAT Scenario - Process

START
START

Execute Test Scenario Document Observations


BUSINESS USER ADD UAT SCENARIO
(Use TEAMS)
& PRODUCT (Use TEAMS)
OWNER
UAT FAILED

UAT PASSED
Mark Scenario as "Ready Triage, Prioritize, Root
EDW Team to Execute" Cause Analysis

END
COMPELTE
Adding UAT Scenarios – How to

• Log into TEAMS


• Navigate to EDW
Core4 UAT/UAT
observation
channel
• Click on EDW UAT
scenarios tab
• Click on + new
items to add a
UAT scenario.
Adding UAT Scenarios – Details in the form
Use Teams EDW UAT Scenario
Form to update:
• Test scenario
• Specific query/data
• Policy, account, claim,
submission #
• Business area/LOB
• Type of User
Adding UAT Observations – Details in the
form
• Use EDW UAT Observations form
in Team to update:
• Observation
• Steps to reproduce
• Actual result
• Expected result
Adding UAT Observations – How to

• Log into TEAMS


• Navigate to EDW
Core4 UAT/UAT
observation
channel
• Click on EDW UAT
observations tab
• Click on + new
items to add a UAT
observation.
Triage & Resolve Observation – EDW Team
• Once an observation is documented by business users/product owner
EDW team will follow the below steps:

• Discuss Observation with


ANALYZE • EDW Code Fix & Testing
business users • Upstream data/code
• Prioritize Observation • Root Cause analysis change testing.
• Defect Creation • Determine EDW code • Assign to business users
changes/upstream to retest
data/Code issue

TRIAGE RESOLVE
UAT Testing
Responsible
Task Details
  Business EDW
UAT Scenario documentation ü  
UAT Scenario Test Readiness   ü
UAT Test Execution ü  
UAT Observation Documentation ü  
UAT Observation Triage (pending decision) ü ü
UAT Root Cause analysis and subsequent code change/Data Load   ü
JIRA defect Creation   ü
Upstream Defect Creation/Followup   ü

You might also like