business requirements analysis during production release
Post on 16-Apr-2017
200 Views
Preview:
TRANSCRIPT
Nikita SyskovEPAM
User stories in UAT time
Let me introduce myself
~10 years of software testing experience6 years of leading test activities
2
3User stories in UAT time
A bit of Agenda
1)Why we have to speak about it?
2)Example 1 – Change size
3)Example 2 – Add support
4)Example 3 – Update description
5)Can we prevent it?
4
Pre-requisites
1)Changes during UAT are reality
2)We do not question customer’s sanity
3)There is always a chance to negotiate
4)Positive thinking is professional thinking
User stories in UAT time
5
Why we have to speak about it?
User stories in UAT time
6User stories in UAT time
Why we have to speak about it?
7User stories in UAT time
Example 1 – Change size
8User stories in UAT time
Example 1 – Change size
What does it actually mean?• Code change• Design change• I18N effect• Integration• TC updates• US approves• UAT team informing
9Название темы. Может быть длинное, даже не одна строка, а две или три
Example 2 – Add support
10User stories in UAT time
Example 2 – Add support
What does it actually mean?• Code change• Design change• I18N effect• Integration• TC updates• US approves• UAT team informing
11User stories in UAT time
Example 3 – Update descriptionLet’s eat, Grandma
Punctuation Saves Lives!
12User stories in UAT time
Example 3 – Update description
You will be required to work twenty four-hour shifts
You will be required to work twenty-four hour
shifts
You will be required to work twenty-four-hour
shifts
13User stories in UAT time
Example 3 – Update description
What does it actually mean?• Code change• Design change• I18N effect• Integration• TC updates• US approves• UAT team informing
14User stories in UAT time
Can we prevent it?
15User stories in UAT time
top related