How to estimating the story point include QA

Previously, we estimate the story point with servers, clients, and QA were included in the together

The problem was that it was difficult to see at a glance how much developer story points were.

So we divided into QA story point is into sub-task, but I think it leads to a lot of work in ticket make,isn't there a good way?

1 answer

0 votes

You should not be putting the QA estimates on sub-tasks. QA should be part of the team, and hence part of the overall estimate for the Story.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

CLOUD

STANDARD