what is the ticket flow for a scrum team that has developers and testers on the same board?

[Ashish Srivastava]

I have a team of 3 developers and 2 testers. Everytime a ticket is marked as complete by the developer there is a need for the testers to start working on that ticket in a conveyer belt approach. 

Since testing and development may not complete in one sprint wew need to complete development in one sprint and testing in other, hence we can't add it was a workflow on the same ticket.

I tried to manage it using mentioning testing team on the tickets close to completion but the effort by testing team to prep for that ticket cannot be tracked if they start any preparation or KT on that ticket.

May I discuss how others are doing this? any links to a proper cases study would be useful.

Kind Regards,

Ashish

[Trudy Claspill]

Hello @Ashish Srivastava 

Welcome to the community.

If the development and testing work for an issue must be tracked separately then you need to create separate issues for the work. You could always manually create a "testing" issue (and optionally link it to the "development" issue). You would then need to estimate that testing work and plan for it in your sprints just like you do for your "development" work. Alternately you could automate the creation of the "testing" issue. The automation could be developed to create the testing issues as soon as a development issue is created, or when the development issue transitions to a particular Status.