Доклад Никиты Сыскова на конференции SQA Days-20. 24-26 ноября 2016. Минск www.sqadays.com

1. Software quality assurance days
20 Международная конференция
по вопросам качества ПО
sqadays.com
Minsk. 24–26 November 2016
Nikita Syskov
EPAM
User stories in UAT time

2. User stories in UAT time
2
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?

3. 3
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

4. 4
Why we have to speak about it?
User stories in UAT time

5. User stories in UAT time
5
Why we have to speak about it?

6. User stories in UAT time
6
Example 1 – Change size

7. User stories in UAT time
7
Example 1 – Change size
What does it actually mean?
• Code change
• Design change
• I18N effect
• Integration
• TC updates
• US approves
• UAT team informing

8. Название темы. Может быть длинное, даже не одна строка, а две или три
8
Example 2 – Add support

9. User stories in UAT time
9
Example 2 – Add support
What does it actually mean?
• Code change
• Design change
• I18N effect
• Integration
• TC updates
• US approves
• UAT team informing

10. User stories in UAT time
10
Example 3 – Update description
Let’s eat, Grandma
Punctuation Saves Lives!

11. User stories in UAT time
11
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

12. User stories in UAT time
12
Example 3 – Update description
What does it actually mean?
• Code change
• Design change
• I18N effect
• Integration
• TC updates
• US approves
• UAT team informing

13. User stories in UAT time
13
Can we prevent it?

14. User stories in UAT time
14