Unproven product at the end of Sprint in Scrum methodology

Here is the problem. Developers have some kind of task (development of a certain function) that takes up the length of a sprint. So, towards the end of the sprint, the developers are happy as they just finished their work.

BUT. The product is not a QAd, therefore it cannot be distinguished as "potentially shippable", as it will most likely contain some errors.

So the question is: if there are no automation tests, only QA engineers for people, what is the best way to plan our sprints? To have one delay sprint (QA checks the elements that were developed in the previous sprint)?

What can help us in this situation? What should developers do during the QA procedure?

+3
source share
6

Scrum , "" , . , , .

, . . .

, . QA . QA, , "" , . , , , , . QA, - QA . QA , . QA " ". , , " ", - . , , , , , , , . , , , .

, . , , , . " ", . ; . - part2 part1, , QA , "" .

!

+5

, . ; aka scrum-fall.

1) QA . , "" . , .

2) , , . 1-2 ( , ). , , , .

3) Scrum . , . , , , .

4) , "" , , , , . , , .

5) "". , , , .

6) "" . , "", , .

, , , , .

+3

, , QA, .

, , .

, , , , done.

, , /. , - QA. , , , .

+2

. ( ), ( ). , , QA .

, Sprint, Sprint.

, Agile, QA , . .

QA?

Scrum, , , . , , , QA, QA, Sprints...

+1

QA Sprint, . Sprint , , Dev. QA, Release . "" Dev.

/ . , QA, , , , .

, . , - , QA .

0

( ). . , ( ). , A, , , , - , . , , . , ( ), .

0

Source: https://habr.com/ru/post/1716621/


All Articles