Re:Developing SaaS? Forget Scrum, Check Out Kanban and Simil...
by cakeface on Monday February 19, 2018 @11:08PM
(#16417785)
These are 4 great points. I really like the 2 & 3 about heterogeneous work and resources. No work is just the same in eng and no devs or QA are even the same. Not a widget factory!
I do think that scrum and sprints are worth the bother if you have to ship the product externally on a timeline. I've worked on client contract projects where it worked well as you could give a release over to a client "on time".
Re:Developing SaaS? Forget Scrum, Check Out Kanban and Simil...
by TheCoelacanth on Tuesday February 20, 2018 @02:54PM
(#16423577)
Would you really have all of these "Requirements, product design, UX detailing, quality assurance, marketing, and sales" done by the same team? That is what your point two seems to imply and I have never seen teams structured like that before.
Re:Developing SaaS? Forget Scrum, Check Out Kanban and Simil...
by paulddraper on Tuesday February 20, 2018 @05:23PM
(#16424815)
Agile teams are supposed to be "cross-functional", meaning they can define, build, test, and operate.
Re:Developing SaaS? Forget Scrum, Check Out Kanban and Simil...
by TheCoelacanth on Tuesday February 20, 2018 @07:09PM
(#16425597)
Cross-functional doesn't mean that the entire world is part of your team. Sales and marketing are stake-holders that work with the Product Owner to define a Product Backlog. They are not part of the Development Team.
1. Ratcheting workload
Your sprint commitments are based on average past velocity. Because it is an average, half of the time, you take too much, and half the time you take too little. But no one likes schedules that are finished only 50% of the time, so teams push to reach commitments. Thus measured velocity is naturally much more prone to increasing than decreasing.
2. Heterogeneous work
Scrum was created by engineers. Scrum treats each story as pre-dev, in-dev, or post-dev, and only estimates and plans the in-dev work. In the real-world, engineering is not the only work (or even most of the work!). Requirements, product design, UX detailing, quality assurance, marketing, and sales are no less of a feature than its engineering. "Okay," you say, "include these aspects in the scrum estimation too". But....
3. Heterogeneous resources
Each story has a different composition of types of work needed. And each of these types requires a specialized skill set. Your blanket cover-all estimate will wind up with engineering-heavy, or UX-heavy, or QA-heavy sprints.
I would no sooner have an engineer market a product as a I would have a marketer engineer a product. But that's what scrum sprint estimates seem to imply.
4. Uneven cadance
On the first day of the sprint, all devs are starting stories. On the last day of the sprint, all devs are ending stories. This causes uneven sense of cadence (I need to get this in), uneven needs (lots of QA, now!), and unnecessary contention (everybody merging, conflicts, breakage).
---
To sum it up: At the end of the day, pipelines are simply a more accurate domain model.