Skip to main content

The Scrum Team creates separate tickets for testing

Last post 01:08 pm March 30, 2023 by René Gysenbergs
3 replies
01:00 pm March 29, 2023

My Scrum team regularly creates and estimates separate tickets for testing during the sprint. When I brought it up with the team and explained to them that testing effort should be included in every ticket, QA response was that they create test tickets because they test functionality in scope, so it’s more convenient for them.

Have you come across this problem? If so, what did you do? 


04:47 pm March 29, 2023

Have you come across this problem? If so, what did you do? 

The Product Owner manages the Product Backlog. In your situation, the PO is coming across this problem right now. So, have you asked them what they are doing, and how they are able to organize and order "test tickets" in meaningful relation to other work?

09:24 pm March 29, 2023

"it’s more convenient for them."

That answers the question

Scrum team is self organizing

Scrum master or Product owner don't manage the team, and don't have any power to tell team members how to act, as long as their actions fit in general Scrum framework.

01:08 pm March 30, 2023

My Scrum team regularly creates and estimates separate tickets for testing during the sprint.

First: please define what a "ticket" is? Is it a User Story or a Task?

Second: On the original Scrum Boards, the User Story stayed at the beginning of the Board, while the individual units of work were represented by tasks, each with their own weight (the combine weight of the tasks = the weight of the User Story). Development could be several tasks, testing was minimum one task, but could also be several tasks, etc...

This was and is the normal working procedure on a Scrum Board.

It was only when Scrum Teams started to use Kanban Boards, especially digital Kanban Boards that a User Story should include all tasks, testing, etc... because you have to move the User Story completely over a Kanban Board.

So use a Scrum Board instead of a Kanban Board, all digital applications (Jira, Azure, Octane) have both options.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by may have their access revoked at any time, without warning. may, but is not obliged to, monitor submissions.