How should QA staff accurately evaluate?

Question

In my last work, I worked with a company that was going from the NO methodology to use the Scrum / Agile method. Many problems were encountered, including the fact that the Scrum expert really did not know how to effectively implement Scrum.

The plan they used was relatively simple:
1. Start Sprint planning meetings where the evaluation of QA and Dev time was one estimate - not one for QA time and one for Dev time.
2. When the time estimate reached a common value for Sprint, no more functions were added to this sprint.

The main problem was that QA doesn’t know at all HOW the developer is going to write code ... because they are not encoders! Thus, the QA teams really had no reason to form a decent assessment of the time. Conversely, 99.9% of developers do not know the difference between performance testing, functionality testing, regression testing, and UAT testing .... therefore, they could not accurately estimate what QA time is needed for certain functions.

Ultimately, I took a bullet for my QA team and took this concern to the leadership, where I was immediately fired for not being able to work in the Scrum environment, but it really is neither here nor there.

But that makes me wonder what mistake was here. Was my problem tough and wanting to put hard times on things, or was it the expectation that QA should inherently know how long something should take to encode?

Answer 1

I have been in both QA and Dev. This process is actually not so different in any world, because it comes down to a simple thing: all estimates are guesswork. They are based on experience, judgment and an assessment of the complexity and risk of a particular set of problems, but at best these are good guesses.

, . QA , : , , .. , , . 2- , , , , : ) ) , .

, . (1.5x, 2.0x, 3.0x) . , , , , .

- , . , . , . , , , .

Agile ; . , , , , , , . "-"; , , , .

, ? , , - . . , , , . Agile- , Waterfall, , QA, , , , , Agile. , , , , , ; , .

: QA , . , , , . , " " " ", , Dev QA-.

Answer 2

, , mgmt.

Answer 3

, , , QA , IDE. , -, , .. - QA.

Answer 4

What I found to work well is the dev / test loop offset. So you encode one iteration, and then QA in the next. This gives the QA team time to properly cover the work, rather than base their assessment on developer assessment.