4 ms·
Our weekly "why scrum sucks" post that's really a "why my company does scrum wrong and I don't know how to fix it". Product owners push customer value. Of cour
by tootie 8y ago
Our weekly "why scrum sucks" post that's really a "why my company does scrum wrong and I don't know how to fix it".
Product owners push customer value. Of course. You should too. Code quality and refactors have business value. Reduced maintenance cost, fewer bugs, faster future dev. If you can't explain that to your product owner then maybe it's not worth doing. I think your big missing piece is the collective ownership aspect. Product owner gets to set priorities, but it should be a collective discussion. Every dev should be allowed to express their opinion and it's the job of the product manager to referee.
- addicted 8y agoWho is the “you” here? Who is supposed to explain to the product owner that code quality and refractors are worth doing? The real issue the article brings up is that Scrum has an individual who takes ownership and responsibility for the product backlog, it has an individual who takes ownership and responsibility for the project management, but it has no individual who takes ownership and responsibility for the non visible technical aspects of the product. In an ideal world, this responsibility would be taken up by the scrum master, who would have technical expertise, but as the article points out, (a) scrum never states this, and in fact, hints in the opposite direction, and (b) this is rarely the case in the real world. The scrum masters are usually as non-technical as you can get.
- nradov 8y agoThe agile team members are supposed to write refactoring user stories and explain their value to the product owner. If the team members aren't doing that then they aren't doing their jobs and need to be trained. Going beyond Scrum, Scaled Agile Framework (SAFe) has some specific guidance on refactoring. https://www.scaledagileframework.com/refactoring/ https://www.scaledagileframework.com/refactoring/
- jameshart 8y agoThis is utterly backwards. The team owns it all - the process, the product, the technical artifacts, the code quality. If the team is looking to the PO or the Scrum Master to take responsibility for things, then they are going to fail. The product owner is there to help the team understand what value they can deliver. The scrum master is there to help the team optimize the process. The team hopefully has developers on it who are there to help the team make well engineered pieces of code Maybe there are designers to to help the team make great user experiences. The team has specialists, but the team works collectively to deliver results. If your scrum team has a bunch of engineers on it wondering how to get their voice heard over the product owner, you don’t have a scrum team building your software, you have a PO acting as a tech lead running a waterfall project.
- Cakez0r 8y ago> Who is the “you” here? The development team!
- specialist 8y agoScrum 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.
- 8y ago
- emodendroket 8y agoWhen every single failure of a methodology is explained away with "you aren't doing it right," I begin to question the methodology itself.
- jameshart 8y ago“80% of companies suck no matter what methodology they use” is an equally plausible explanation.
- s73v3r_ 8y ago"why my company does scrum wrong and I don't know how to fix it" Well, because more often than not, the answer is management, and there's really no way to fix bad management.