Hot answers tagged

25

Get the whole team to work on the problem. Given the arrangement you've discussed clearly the team needs to look at options to resolve this. The problem itself seems fairly endemic in all of the organizations I have worked with. It seems inevitable given the setup unless proactive steps are taken to address it. A frequent issue is that there is no 'one ...


7

Great Communication Brings Great Results Being last in line, QAs keep facing this repetitively. QA should proactively communicate delays and respective risks to stakeholders. I’ve never seen any agile project where every sprint came in on time. Start with finding the reason what is causing the delay. There can be multiple reasons for the delay: Estimates ...


5

We have an issue Issue for who? Sprints are a completely artificial unit of time usually set up by managers who do not do your work anyway. If you're breaking this artificial deadline but the clients and customers are happy with the product, perhaps it's time to change the way you as a team work. One problem with the way you seem to work now is that the ...


5

In the spirit of working in a multi-disciplinary team, I think developers should participate in the QA process if there's a backlog of work, (or even if there isn't). I think it's bad practise for the development and QA teams not to be closely integrated - As far as possible, they should be the same team, and that makes it easier for developers to switch ...


5

There are a few different ways to approach this problem. From a Scrum perspective, your Development Team does not have sub-teams. You may have specialists, such as people who specialize in testing, but the whole team should be involved. Rather than putting the QA specialists in a position where they must test everything at the end of the Sprint, the whole ...


4

Not Actually Agile As is common, people have taken a waterfall process and slapped an Agile label on it while being un-agile. The classical Agile model doesn't have a separate QA team at all. There is a single, small team, who report to a product owner. The product owner is responsible for acceptance, and the developers are responsible for pre-deployment ...


4

Tell your devs and management that a Backlog Item isn't "done" until it is tested. So PBI don't get "done" at the end of the sprint, they remain unfinished because the team "forgot" to schedule the necessary QA. The whole Scrum team should have a Definition of Done and QA belongs into it. If you can handle irony or sarcasm, ask ...


1

Like some other poster said: work together as a team. To make this possible ensure you speak the same language. We have adopted BDD in our team and it's made our product owner, developers and testers speak the same language and it's made it far easier. It also means us testers can start writing test scenarios at the start of the sprint! (even if there is no ...


1

The QA can push back by not accepting „new work“ in the sprint, which effectively means the testing task will be delivered in the next sprint increment. This push-back either leads to more testing and less stress, or it forces the developers to integrate the testing planning better into the development process. This is a result of a development Organisation ...


Only top voted, non community-wiki answers of a minimum length are eligible