5 ms·
Scrum is antithetical to quality. We're 20 years into this experiment? I have yet to even hear someone tell a compelling narrative about doing QA/test in an "ag
by specialist 8y ago
Scrum is antithetical to quality. We're 20 years into this experiment? I have yet to even hear someone tell a compelling narrative about doing QA/test in an "agile" context.
- regularfry 8y agohttps://continuousdelivery.com/implementing/patterns/ https://continuousdelivery.com/implementing/patterns/ and https://continuousdelivery.com/foundations/test-automation/ https://continuousdelivery.com/foundations/test-automation/ would be your starting point there.
- specialist 8y agoYaya. Thanks for the links. Will review. FWIW, I'm desperately trying to bring "TEST in PROD" style continuous delivery whozeewhatsit to my current team. When in Rome, join the third millennium, old dog new tricks. I still can't imagine I can get back to the 90s (quality wise). But if there's a way, I'm gonna find it.
- nradov 8y agoI'm not sure where you got that mistaken idea. The Scrum values explicitly call for "shippable quality" by the end of every sprint. Other than that, Scrum doesn't explicitly define testing practices so do it however you like. But I would note that you can't test quality into a product.
- specialist 8y agoAgree about futility of testing towards quality. Source: Former QA/Test manager.
- Clubber 8y agoShippable quality to me is a full regression test. That's awful hard to do in the few days a 2 week sprint allows.
- nradov 8y agoYour full regression test suite needs to be 100% automated and fast enough to execute within a couple days. If you don't have that then you have a bigger problem that goes beyond any particular development methodology. A proper Scrum definition of done requires full test automation for every user story. You can't merge code to the release branch or accept the user story until all the automated tests (unit, functional, integration, system, performance, etc) are working.
- Clubber 8y agoI assume you don't mean unit tests, which should never be a replacement for full regression testing. Ya since that is essentially a deal breaker, I wonder why all the scrum consultants fail to mention that. Automated full regression is very expensive to develop and maintain. I think a lot of people who implement scrum don't realize that they are sacrificing significant levels of testing when they implement it without a testing automation team. To me, that's just another reason to ditch scrum.
- nradov 8y agoI mean all tests — unit, functional, performance, everything — necessary to verify that a particular product build meets your customer's quality standards. Automated full regression testing is far cheaper than manual testing. If it seems too expensive then you're probably doing it wrong or failing to account for full lifecycle costs. This is absolutely not a reason to ditch Scrum. In fact Scrum is conducive to good quality practices.
- tootie 8y agoScrum does not require automation at all. Generally speaking, it should, but full automation is folly and dependence on automation is an anti-pattern. You simply can't test everything without eyes. Usually when you automate as soon as something is built, you tend to automate what it does instead of what it's supposed to do. You're also trying to hit a moving target and will end up spending a lot of time maintaining your tests instead of actually testing. There needs to be a balance of automation and manual testing.
- tootie 8y agoI've never seen QA not be part of the agile process. One of the hallmarks is quality-first. Stories are not done until they've passed all quality gates.
- specialist 8y agoThen I need to work on your teams. I have yet to be on an agile team that did triage, acceptance testing, go/nogo. No True Scotsman and all that, but it really was different, back in the day.