Feature development in my company is not 100% agile but does follow two weeks sprint which consists of development (by developers), testing (by QA) and UAT (Product/Stakeholder). I have noticed most of the times, Development and QA activities take majority of the sprint and push stories to UAT towards the end - not leaving enough time for UAT to complete in respective sprint. It either creates chaos at the end or delays the release. Would changing the team composition help? Looking for suggestions on how to avoid such bottlenecks? #agile #delivery #tech
Can perfectly relate
It's not agile it's a small waterfall
UAT(Product/Stakeholders) usually falls outside of the Sprint.
What is the QA actually doing? Why aren't the developers doing this as part of the development process? Ideally, as a feature is completed, you release once it's accepted. Are you doing multiple releases a sprint?
If you're doing releases every two weeks following this process, run not walk to your next job.
Already running. Still being tanked.