My team does operations tickets (incidents, support tickets) AND new feature development. We do not have any QA people - instead we depend on our production team to do QA before we deploy to prod. We also have external customers that need to do UAT testing in our UAT environment. Issue — because we are reliant on the production team or the customer to clear QA and UAT, tickets can stall at that stage for weeks. Right now the workflow looks like this: Backlog —> To Do (Assigned) —> In Progress —> In Review —> Ready for QA —> In QA —> Ready for UAT —> In UAT —> Ready for Prod —> Done (which means Deployed to Production) So, my devs do the work and the code Review then the ticket stalls at QA or UAT for weeks waiting for the other team or customer to do their part. This time adds time against the ticket that is not an accurate reflection of my team’s work. How do you handle these things? Do you break each piece of work to a separate sub-task? (Like Development ticket, QA ticket, etc?) I’ve been racking my brain and am looking for some new ideas/suggestions. Do you break off that piece to another project so that the team’s work from to do thru Code Review is what is measured?

The Scrum masters course URL is not working