Работа с бизнес-требованиями на стадии выхода...

Software quality assurance days20 Международная конференция по вопросам качества ПОsqadays.com

Minsk. 24–26 November 2016

Nikita SyskovEPAM

User stories in UAT time

2User 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?

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

Why we have to speak about it?

User stories in UAT time

5User stories in UAT time

Why we have to speak about it?

6User stories in UAT time

Example 1 – Change size

7User 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

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

Example 2 – Add support

9User 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

10User stories in UAT time

Example 3 – Update descriptionLet’s eat, Grandma

Punctuation Saves Lives!

11User 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

12User 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

13User stories in UAT time

Can we prevent it?

14User stories in UAT time