Employee body cam. Its the only way to be sure

Seriously though, If a dev has a question about a ticket, it should be raised in the daily scrum as an Impediment and answered by the Product Owner (who attends the scrum for this purpose)

If the answer is found, then the ticket should be updated with the information.

If the answer expands the scope of the ticket, the new scope should be put in the backlog, not the current sprint.

At least that's the Scrum answer.

Employee body cam. Its the only way to be sure

Seriously though, If a dev has a question about a ticket, it should be raised in the daily scrum as an Impediment and answered by the Product Owner (who attends the scrum for this purpose)

If the PO isn't able to immediately resolve the question, "check document X23!", "oh that's wrong it should be Q" then they should follow up outside of the daily scrum.

If the answer is found, then the ticket should be updated with the information.

If the answer expands the scope of the ticket, the new scope should be put in the backlog, not the current sprint.

At least that's the Scrum answer.

Employee body cam. Its the only way to be sure

Employee body cam. Its the only way to be sure

Seriously though, If a dev has a question about a ticket, it should be raised in the daily scrum as an Impediment and answered by the Product Owner (who attends the scrum for this purpose)

If the answer is found, then the ticket should be updated with the information.

If the answer expands the scope of the ticket, the new scope should be put in the backlog, not the current sprint.

At least that's the Scrum answer.