Business requirements analysis during Production release

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


5

Why we have to speak about it?



Why we have to speak about it?


Example 1 – Change size


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


Example 2 – Add support



Example 3 – Update descriptionLet’s eat, Grandma

Punctuation Saves Lives!


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


Example 3 – Update description



Can we prevent it?

Business requirements analysis during Production release

Technology

Transcript of Business requirements analysis during Production release