I’m having to justify why our QA team doesn’t actually point stories… anyone have a good reference?

what do you mean by point stories?

@porksausages This is one of the many ceremonies that take place when utilizing the Agile methodology for software development; specifically estimating the effort required to implement a feature.

In the past there was a debate in the team between pointing bugs or not.

The argument to not do so was that it would be necessary time to investigate the bug to be able to properly point it, creating a ticket to investigate a bug was counterproductive and therefore estimating wrong was the same effect of not estimating.

Possibly that could be an argument for QA? But if the QA is for a story that has 5 points, would it be too wrong to assume that QA would be around that?

@meraklis oh effort estimates, i see. in my team, devs estimate the dev work and QA estimate the QA work, and then we add it together.

Sorry points are to measure cognitive load.

The team working on the issues should assign story points. It doesn't matter how, as long as it's consistent over time.

You'll find a magic number where the team consistently fails to reach sprint goals and you stay under that number.

This keeps people from burning out.

It's not about time or effort. Estimating time is useless.