17 ms·
You don't need Scrum, you just need to do Kanban right (2022)
- moomoo11 4y agoAnyone ever noticed how it’s almost always the worst bot tier software engineers on the team who push for scrum over kanban?
- WillPostForFood 4y agoKanban vs Scrum reminds me of: https://ychef.files.bbci.co.uk/976x549/p040p8j0.jpg https://ychef.files.bbci.co.uk/976x549/p040p8j0.jpg
- DanHulton 4y agoEvery team I've worked on that has switched from Kanban to Scrum has slowed down and never regained the previous velocity. Further, many of the promised benefits of Scrum (things like better insight and predictability about delivery rates) never materialized. Every team that I've worked on that has switched from Scrum to Kanban saw an immediate improvement in speed that never disappeared. Once, just once, I was lucky enough to work on a team that switched from Kanban to Scrum, and then, mercifully, blissfully, back again. To be fair, I think we actually worked quicker after the return, though I don't know if that could be attributed to having actually learned some lessons from Scrum, or out of a fear that we'd one day return to it.
- cjbgkagh 4y ago“The process is the punishment”
- leetharris 4y agoYes but raw velocity is not the only thing that matters. For some projects it is, but for many the accountability of Scrum + the grouping helps with dependency management across an organization.
- deleted 4y ago[deleted]
- emeraldd 4y agoScrum does not provide accountability. It creates the illusion of accountability while creating artificial touch points that effectively become the only time anyone thinks about what's going on. At least that's how I've seen it operate in almost every instance I've ever worked with it. Of course, the counter to that is that we're not doing scrum right. The question in my mind then is if I haven't seen a single team do Scrum correctly there's something wrong that makes the methodology so difficult it can't be applied ...
- irjustin 4y ago> It creates the illusion of accountability while creating artificial touch points I'm surprised at the conclusion because this statement can be said of any framework. It's up to the people to actually make it accountable. Doesn't matter if it's Scrum/Kanban or another one. If your org treats accountability as "an illusion" then it's doomed to fail regardless. > The question in my mind then is if I haven't seen a single team do Scrum correctly there's something wrong that makes the methodology so difficult it can't be applied ... This I 100% agree with. I've come to look at these frameworks (kanban, scrum etc) as I look at the Bible... no church gets it right and never will. It's not possible.
- paulmooreparks 4y ago> This I 100% agree with. I've come to look at these frameworks (kanban, scrum etc) as I look at the Bible... no church gets it right and never will. It's not possible. It's interesting that you use this analogy. I've always compared Scrum to Communism or faith healing: If it doesn't work for you, you either didn't implement it correctly or you didn't believe in it enough.
- enraged_camel 4y agoRight, exactly. In other words, the claims it makes are unfalsifiable, because if they don't come to fruition then clearly there must be some other factor in play.
- bedobi 4y agoWhat you're describing has been my experience as well across multiple teams and workplaces.
- crazygringo 4y agoBut velocity of code written is not the same as velocity of value delivered. In Scrum, estimation meetings usually result in follow-ups with stakeholders that can (and often do) radically change the stories themselves. Totally different code winds up getting delivered that increases actual value delivered, even if "lines of code written" slows. That's the whole point of agile, to deliver value rather than code.
- rqtwteye 4y agoTo be honest I have never seen this materialize. Usually you get some input from product management, the devs estimate it and then do it. I have never seen feedback from estimation to requirements.
- irjustin 4y agoIsn't that because the product manager is gathering requirements from other orgs/users? > I have never seen feedback from estimation to requirements. Perhaps you work with perfect pms! jokes aside, usually all it takes is an estimation of 8 or 13 and something changes real fast.
- lazyasciiart 4y agoYea, they tell you that they don't believe your estimates and stop asking for them before setting the deadline.
- crazygringo 4y agoThen that's not agile. The entire point of agile is that a PM can't do that. Large estimates force a PM to go back to stakeholders and revise the desired features to something that engineers have consensus that should be deliverable within the next sprint given their historical velocity. If you're not doing that, then you're not even in any conversation about agile/scrum.
- kqr 4y ago
- deleted 4y ago[deleted]
- whitemary 4y ago> Every team I've worked on that has switched from Kanban to Scrum has slowed down and never regained the previous velocity. As an engineer on a team using scrum, this is my favorite part.
- esafak 4y agoIf I am being generous, Scrum is for service teams, which can benefit from some of Scrum to temper unreasonable requests of senior stakeholders by providing a social contract on what is going to be worked on. More autonomous teams don't need it.
- Tagbert 4y agoI’ve always considered Kanban’s lack of sprints to be well suited to service teams where individual requests are not naturally tied to each other and there is no benefit of delaying delivery into sprints.
- esafak 4y agoEverybody wants their ticket serviced ASAP. Scrum helps manage that expectation. If a sprint is underway, new requests have to wait for the next sprint unless an agreement is reached to drop an existing ticket.
- 1123581321 4y agoCycle time on a board gets you that as well.
- esafak 4y agoThis provides more visibility and granularity, increasing confidence and satisfaction of customers.
- DangitBobby 4y agoHow? How is pulling 10 points of work into every two week sprint "more visible" or "granular" than pulling anything as it comes up at a velocity of 5 points per week? I'm not even being contrarian, I truly don't understand how sprints could be better than knocking down a work queue.
- gre 4y agoI did scrum once and we were literally always sprinting. The daily standup consisted of trying to think of excuses why the multiweek task wasn't completed (like they expected) and one dude who "zereo'd his inbox" every day.
- ptmcc 4y agoThat the iteration unit of scrum/agile is called a sprint is a huuuuge pet peeve of mine. Sprinting is definitionally an unsustainable pace. I know, I know, it's just a label applied to the cycle time of the process but labels matter and I think it subtly and subconsciously poisons the whole thing. Especially when managers and PMs start making sprint cycles into hard deadlines.
- seniorThrowaway 4y ago>making sprint cycles into hard deadlines One of the tipoffs that you are working under fake agile not real agile. I have the same problem with using the word "sprint" as well, but I think the true issue is that most orgs claim to be "agile" when they are actually doing some variety of waterfall with agile verbiage thrown in. The best test for fake agile is if you can't cancel the daily standup, even for a couple of days, via the retro.
- detaro 4y agowho is "they" here?
- josephg 4y agoI think the "problem" is that Scrum orients more to the needs of people outside the team. So, (in theory) you get clearer reporting and more visibility into whats going on. People expect that extra reporting to be free, but its not free. The time taken to do team task estimation, update jira tickets and have retrospectives is time spent not programming. The sad truth is that most management teams would prefer their employees to be predictable and observable (ie, under control) than be efficient. Especially if nobody can actually quantitatively measure the loss of efficiency.
- ptmcc 4y agoI agree. In my experience that outside visibility is mostly a mirage. Velocity metrics, burndown charts, point estimations, and all of that have been at best aspirational white lies and at worst outright falsehoods on almost every scrum/agile team I've ever worked on in the past fifteen years. In actuality many scrum teams are doing something closer to kanban day-to-day under the fake veneer of scrum/agile sprints on top to satisfy management and/or external parties.
- rightbyte 4y agoYe padding estimates and report time according to the estimate to make the burn down chart straight was what I learned to do when Scrum was forced on my team for no good reason at all. -"It is impossible to do accurate estimates" -"You will get better at it" I wonder if the Scrum Master knew that in the end "get better" is "starting to cheat". Do anyone else share this experience?
- emodendroket 4y agoEstimation often is way off for construction projects, but would you hire a contractor who refused to hazard a guess of how long a job would take or how much it would cost?
- gilbetron 4y agoConstructions remains a terrible analogy for software development, as it always has been.
- tysam_and 4y agoI've seen Kanban work well on smaller scales, and Scrum work well on larger scales. I cannot for the life of me work in the churn and development pace of a Scrum team, so Kanban (and the culture around it) is best fit for me. I think it also depends upon the type and culture of people working in the team as well. Some teams work really, really well with the predictable cadence, others do not. It's a case by case kind of situation, I think. That said I highly prefer Kanban personally for an number of reasons.
- Double_a_92 4y agoThe commitment to sprints was literally the first thing that got dropped in our company. It's so nonsensical to create completely arbitrary deadlines without any real urgency. We now have long sprints (~1 months) for reviews and retrospectives. Which are usually well received. You get to see what all the other teams have been doing, and you also get a formal chance to talk about any problems.
- kqr 4y agoSprints and timeboxing more generally is not about enforcing deadlines. That's such a common misconception and I wish it would die. Timeboxing is about committing only a small amount of time and money at a time, so you can choose to double down on winners and stop investing in losers, rather than suddenly finding yourself having sunk 3 months of time into something that turns out wasn't that good after all. The question is not "How much can we definitely complete in two weeks?"; it's "What things are promising enough that we are willing to dump two weeks into them, with no promise of ever making a profit?" If one month counts as a small amount of time and money for your organisation, then you're doing it right!
- 988747 4y ago[dead]
- seniorThrowaway 4y agoIt's not a misconception when it's what many organizations are actually doing. Any that implement SAFe, for instance.
- fnordpiglet 4y agoI have the software engineering uncertainty principle. The more you try to measure and estimate and predict software velocity and delivery the more you slow it down. I think this is probably true of any largely creative and problem solving task, but compounds because most of the uncertainty derives from dependencies requiring those dependencies to likewise measure and slow down. The more complex and interconnected an effort is the more scrum hurts it.
- hnick 4y agoThis sounds a lot like the coastline paradox. The more precisely you try to measure a coastline, the harder it gets due to its fractal nature. Software estimation, similarly, is fractal in nature - you can always drill down deeper to measure but it gets increasingly complex and at some point you have to ask, is it worth it being "accurate"? Or do we just do it? Org charts require the former while developers desire the latter.
- moring 4y agoI think that analogy is broken. Measuring a coastline more precisely doesn't just become more complex (measuring precisely often does), but actually increases the measured length towards infinity. Unless you wanted to say that the same is true for software estimation, e.g. due to the measurements taking up more and more time.
- hnick 4y agoYes, I meant the time taken estimating. The act of measuring estimated hours becomes more complex because the closer you look, the more you see, you could do it forever and have to stop somewhere. But maybe instead of infinity, it's better to say estimation can take longer than the work itself which has been the case a few times for me.
- throwawaysleep 4y agoThe only way better insight would happen is if the devs behaved like product managers/owners. We don’t want it. I can actually see predictability improving, but mostly because we will ship whatever at the end of the sprint and let any issues come back as bugs later. We always ship on time at one Scrum job, but the quality is very low.
- BillyTheKing 4y agoI think one key issue here is that Scrum without Extreme Programming and rigorous iteration can become a shallow process. Often, products that don't undergo much iteration are broken into arbitrary two-week windows under the guise of iteration. However, Scrum doesn't make much sense if you don't continuously iterate. Another symptom of this is people measuring velocity instead of value created. To properly implement Scrum, you actually need to measure the impact of the work completed in the past two weeks. Unfortunately, most teams don't do this, instead they focus on measuring velocity since it's easier and within their control. It's worth noting that it's completely fine for teams not to constantly iterate and change direction (including high-performing teams), and in those cases, Scrum simply isn't the best tool for the job imo. I must admit that I personally prefer Kanban for almost all workloads.
- jrockway 4y agoIs Scrum supposed to increase velocity? I always view these processes as a consistency enhancer. "What can we accurately promise 6 months out" vs. "how can we get the most done possible?" This is important because the big risk is that you do 80% of 10 projects, rather than 100% of 1 project, especially if you have a team and not just a couple of individuals. Lots of stuff pushes organizations in the direction of doing 80% of 10 separate projects, and it's a killer. This is good reading in this domain: https://apenwarr.ca/log/20171213 https://apenwarr.ca/log/20171213
- Gareth321 4y agoAs a Product Owner I am biased, but sympathetic. The ceremonies and oversight certainly can slow down velocity. But there are many benefits, and they are not immediately apparent to developers. Alignment is so important, and it's rare that I've found a team not using scrum which is working harmoniously. In reality, some members of the team aren't pulling their weight and it's causing animosity. Or they're working at odds and not communicating the pieces they're developing. A huge one for me is stakeholder alignment. Without scrum it's awfully common for developers to build things the stakeholder doesn't want. Scrum forces regular check-in and demonstration which otherwise rarely happens organically. A big part of scrum is accountability. As I touched on, when people aren't pulling their weight, it hurts everyone. Unfortunately developers are rarely extroverts, and they often don't have the skills or desire to have tough conversations with each other. Sometimes it's just agreeing on what they find acceptable behaviour and work. Sometimes it's adapting to different ways of work, or neurological issues with a team member. You might be surprised to learn that a lot of developers are on the spectrum. Scrum forces these conversations to the fore and provides a tested framework for conflict resolution. We also gain transparency. This is really important so that all the other supporting business functions can operate. Sales can communicate with customers about important updates and new features. Marketing can plan campaigns. Support can prepare. Finance can ensure adequate budget for new infrastructure and FTEs. Sure it's annoying, but this planning is essential for a business. It just doesn't happen organically. Scrum forces developers to work to some kind of schedule, offering short-term (but flexible) estimates on what can be delivered, when. In a perfect world, none of this is a problem, and all of it happens organically. I've just never seen that happen. The sacrifice in velocity is worth the increase in value output to the stakeholders.
- re-thc 4y agoYou make it all sound like a factory and blame developers for going rogue. That’s not how it works. It’s as though developers are dumb and can only execute if you tell them to do exactly as needed. Rather where’s the leadership and direction? Perhaps that’s not clear or the developers don’t even agree with what’s going on. You statement is so 1-sided. If someone is not performing you shouldn’t need scrum to work that out otherwise you have bigger problems. I’d argue alignment is useless as most of the time developers are told to implement useless features. Perhaps with some guidance and direction what the developers come up with is better than product. It’s sad but product is like a theory machine that’s often impractical. So what would you prefer? Developers without scrum delivering in 4 months or with scrum and taking a year? Even if they do go off for a few months on their own it’s more than worth it. The problems aren’t accountability or alignment. If people aren’t following a plan, that is if there is 1 then it’s a leadership problem.
- michaelcampbell 4y ago> Every team I've worked on that has switched from Kanban to Scrum has slowed down and never regained the previous velocity. Further, many of the promised benefits of Scrum (things like better insight and predictability about delivery rates) never materialized. This has been my experience. I've seen more than once management teams happier with numbers and estimates that weren't met than actually getting software out quicker at an unanticipated rate. They'd rather have estimates that they could yell about than revenue generating software through (presumably) happy customers. <shrug>
- perfectritone 4y agoI've heard over and over from managers that scrum is better at anticipating delivery dates. Even when the dates are consistently missed. They'd rather slow teams down with process so they can have a date to give their stakeholders, regardless of its accuracy.
- brezelgoring 4y agoManaging the confidence of your benefactors is a big deal in business, I'd say you can make a career out of it alone, no other skills required. So in a sense you could say that Scrum is the businessman's brainbaby to handle engineering types.
- theshrike79 4y agoYou can calculate the team velocity pretty easily in Scrum (amount of story points completed per sprint) and from that you can estimate what gets done in what time. BUT it needs the exact same team to be together on the same codebase. You add or remove people, the velocity changes. You change projects, velocity changes. People also need to be honest when estimating tasks, don't be a 10x cowboy and say something is a half-day task when you know it'll take two days. It's always better to pick too few tasks for a sprint than it is to take too many. You can always grab more stuff off the project backlog if the sprint backlog runs out mid-sprint.
- przemo_li 4y agoIn Kanban you multiply cycle time by tasks and do some modeling on that value. Only difference is that in SCRUM whole team does produce raw value upfront of work, while in Kanban manager computes raw value downward of work. Raw value here refers to lack of statistical analysis.
- csours 4y agoThere are different problems, depending on your role 1. Communication and Funding - Does your VP know how they are spending money? How is that money allocated? This is why you have agile-fall or SAFE. 2. Planning - Can you deliver the solution your architect drew on the napkin? Does the PM know enough to schedule things. 3. Work handling in the team. This is the one that I think people most want to talk about, and anything that works for the team will work. You don't need anything fancy.
- ptato 4y agoWhat is Kanban?
- theshrike79 4y agohttps://en.wikipedia.org/wiki/Kanban https://en.wikipedia.org/wiki/Kanban
- nittanymount 4y ago- PM/PO loves scrum, that gives them an illusion of controlling the dev speed/progress... - the estimate is a joke... - the standup is useful to know who is pretending work. but no need a daily standup for sure. and a non-technical PM with scrum makes things worse.
- leetharris 4y agoSounds like you have a very poorly run and dysfunctional team. When applied correctly, good project management ends up better for everyone.
- nittanymount 4y agohaha, we started by following the scrum rules, some folks didn't think it is the way to go, sadly not everyone spoke out, because PM/PO thought it is useful from their perspective... fortunately, over time, no sub team continued the way, it has mutated back to the kanban style more or less...
- rqtwteye 4y ago"When applied correctly, good project management ends up better for everyone." With good project management you can make any process work, be it waterfall, scrum, kanban or others. All dysfunction comes from people perpetuating processes that don't work. That's what agile was about originally.
- rightbyte 4y ago> All dysfunction comes from people perpetuating processes that don't work. That's what agile was about originally. Agile is far worse than anything I experienced earlier. It was pushed as some sort of dogma where you are a cranky non-teamplayer person for arguing it is a bad idea. A counter-revolutionary blocking utopia. Giving non-programmers insight into every small tasks is a big mistake.
- WJW 4y agoI hope you are correct. Finding companies with good project management has so far been quite elusive though. In my career I've had about eight project managers so far, six of which were in a scrum environment. Without exception the scrum PMs have not been effective at all. I don't doubt that effective scrum management is theoretically possible, but based on personal experience and also by reading through the rest of this thread it seems that scrum is too difficult to do correctly for the vast majority of project managers.
- beoberha 4y agoIs “doing Kanban” just having tasks on a board without any sort of sprint structure? I feel like it’s a bit of a false equivalence. While I won’t ever defend all the cruft that comes with Scrum, the article seems like a bit of a straw man.
- TobyTheDog123 4y agoI also don't fully understand what "doing Kanban" means - like you, I see Kanban as a type of board rather than a method of going through said board (maybe because of a lack of understanding of process & an over-indulgence in Trello's marketing). That being said, I would say that having a Kanban board without any sprint structure (or any attached micromeetings) would skyrocket my productivity. The two-week sprint thing is meaningless to me - in my org tickets overflow from one sprint to the next all the time, tickets get added mid-sprint, it's an utterly meaningless distinction.
- baby 4y agoKanban is about organizing the work to be done and periodically revisiting the board to understand the work done and what’s next (which involves reprioritizing, pivoting, etc.) Some people might debate on how active a kanban board should be.
- beoberha 4y agoThis goes back to my original post. Is this “doing Kanban” or is this just another process using a Kanban board?
- IshKebab 4y agoThat sounds identical to how companies I've worked for "do agile". A kanban board. Every two weeks you revisit the board, see what got done, prioritise what to do next (usually by dragging it from the "backlog" to "todo" column).
- baby 4y ago
- somat 4y agoI am probably missing something but is kanban even the correct metaphor for creative work(like software development). Kanban is a back pressure mechanism that can get your factory logistics system running smoothly. However the logistics of creative work is very different than the logistics of assembly work. There are almost no parts needed, why is a backpressure system for part delivery even useful?
- riffraff 4y agoIt's not, it's one of those cases where IT took some vague ideas related to a concept (e.g. visualizing/minimizing WIP and having a continuous flow) and decided that those meant we're doing the same thing. See also "lean manufacturing/software development" and obviously "software engineering".
- theshrike79 4y agoIt's about limiting the amount stuff under construction. You got a list of shit that needs to get done. You have 5 people in the team. On the Kanban board you can see how long each item has been in each column and you can see who's working on it. You can also limit the amount of items each person can be working on simultaneously. It should be exactly one or you're multitasking, which isn't good for anything. You have a single task you work on, when it's done you move it forward. If you get stuck you move it backward and comment on it why it's stuck and pick a new one.
- zerbinxx 4y agoI’m not a huge scrum defender - I’ve seen it done right and wrong. Same with Kanban. The only real problems I have with Kanban is that without those annoying team planning/documentation meetings, work will get duplicated, done hastily, done with no discussion or thought toward testing, architecture, maintainability. And that’s not exclusively true of Kanban. But I feel like the lack of organization can turn it from less of a “flow state agile” and more into an insane command economy/death march/spaghetti factory. I usually feel Scrum teams are happier, more close-knit and aware of the impacts of teammates work, and more excited about “doing agile right” than in Kanban - which often feels very siloed and “heads down”. Different strokes, I guess.
- Yhippa 4y agoThose same problems still happen in Scrum and it's very hard to get out of duplication hell once the backlog gets sufficiently large. I personally think Scrum is theoretically great if done right and with smart people, but that is rarely the case.
- zerbinxx 4y agoDuplication hell is the current bane of my existence - I think we would agree that it’s more of an inter-team coordination issue than it is the type of thing that you and the four other people on your team can fix with Kanban/Scrum. But I do feel like Scrum is better at the very least at stopping this from happening because that longer ramp up time from “customer wants X” gives people a chance to say “wait so and so already did that for their turn”
- paulmooreparks 4y ago> without those annoying team planning/documentation meetings, work will get duplicated, done hastily, done with no discussion or thought toward testing, architecture, maintainability I don't see why that is necessarily the case. It certainly didn't happen on the Kanban teams I've led. Maintaining the backlog and reviewing the work in progress is just as important in Kanban as in any other process.
- readthenotes1 4y agoAt some point, the wizard may realize that process is secondary to people, and they can write: You don't need that process. You just need to do this process right. And then fill that post with all of the obstacles that doing anything right entails.
- lmm 4y ago> This demand for estimations leads to unproductive and unnecessary estimation meetings. These meetings are unproductive because they cause developers to spend time debating whether something is worth two or three story points instead of actually writing code. They’re also unnecessary because if you feed the system with more work as soon as software comes out, estimations don’t matter. Only if all tasks are of equal priority, which is rare. Otherwise you need some (very basic) cost estimation in order to prioritize. > Retrospective sessions are also fundamental for a team to continuously improve the way it works. The problem with these sessions in Scrum is that they either happen too early or late. Although it’s good for teams to discuss their practices and look for ways to improve them, it may not be necessary to hold a retrospective session if everything is going fantastically well. Conversely, it may be harmful to wait for two or more weeks to discuss systemic problems impacting the current pieces of work or the overall goal the team is working towards. > In Kanban, there’s nothing preventing teams from scheduling regular meetings. Yet, teams have the flexibility to schedule meetings whenever they’re necessary. But unfortunately this means they also have the flexibility to not hold a meeting when it's necessary. I don't think this article is exactly wrong - Scrum is to a certain extent a crutch, just as any process is to a certain extent a crutch - but I think it overestimates the average manager/team. In my experience teams that pick Kanban over Scrum tend to have issues with stalled, overly-large, and poorly-prioritised tasks (e.g. an undesirable task can sit indefinitely in the "ready for work" column which is usually not what you want), too little process refinement (in particular, retrospectives end up being rare) and take too long to recognise issues. Scrum is prescriptive and restrictive, but it's like that because it works. After all, if your team was perfect you wouldn't need Kanban either. Just do the right thing and don't do the wrong thing bro.
- JenrHywy 4y agoPicking up on > They’re also unnecessary because if you feed the system with more work as soon as software comes out, estimations don’t matter. The question is: estimations don't matter to who? As much as I'd like a constant stream of quality features to be good enough, in reality senior managers and clients want to know what they're getting for their money, and when they'll get it (at least roughly). If your software is doing something important, it's likely that people will be depending on it and when a new feature ships can have a significant impact on how they work, and in turn, what they can deliver.
- KingOfCoders 4y agoStart with the "Why". Why would you use Scrum? I'm with Simon Wardley [1]. Agile, Lean and waterfall are not the same thing and are not exchangeable. Agile is for building new things, it's optimized for learning and navigating in a space you don't know about (say before/around PMF) - though most people do Scrum wrong, E.g with the roadmap-anti-pattern. Lean is for optimizing a product, after PMF, E.g. when Scaling. Waterfall and Six Sigma is when you do the same thing over an over again and you have a lot of knowledge in the space, when you outsource commodity development, E.g. customizing a CRM. [1] https://twitter.com/swardley/status/1215020984278888451 https://twitter.com/swardley/status/1215020984278888451
- irjustin 4y agoI appreciate the article but I worry that Scrum implemented too rigidly is the reason why it gets a bad reputation. A lot of the arguments being made are really difficult to generalize and say "this works for every org!". One example: > When that happens, instead of designing features by committee, which demands a significant amount of back-and-forth discussions, decisions happen locally, and thus are easier to make. This works really well when the engineers themselves have all the knowledge+ability to tackle the problem. Smaller startups are perfect! and teams that are pure technical. But once a key portion of the requirements lives outside the team, this is no longer effective because then you're building without that feedback. The danger is trying to measure things purely on developer velocity. I'm not saying kanban is wrong or scrum is wrong, just do what's best for your org by building what's important to your business.
- ajmurmann 4y ago"This works really well when the engineers themselves have all the knowledge+ability to tackle the problem." This reminds me of a similar situation almost a decade ago where someone watched a talk on how GitHub uses GitHub to build GitHub. The people who watched the talk all tried to convince me that we should adopt similar process that puts less emphasis on PMs. However, this worked for GitHub because their engineers had such a strong similarity to their customer base. For us that wasn't the case at all and we typically needed PMs to have lots of customer conversations and explain to us how customers used our product because we were building Enterprise software for people whose day-to-day we didn't understand easily.
- colonwqbang 4y ago> But once a key portion of the requirements lives outside the team, this is no longer effective because then you're building without that feedback. But how does Scrum help out here?
- irjustin 4y agoScrum has prescriptive method of who is supposed to gather requirements, the meeting for requirements gathering, estimation for "understanding of requirements", and demo... well for demo'ing the feature back to "the powers that be". Kanban doesn't prescribe any stakeholder methodology. It's not that it's not important, it's just up to the organization. This is definitely a point of contention in Scrum because "oh this is so slow", "there are too many stakeholders", "why do we have to do it this way". I'm at the belief - some way is better than no way. If you don't like Scrum, cool! Go build your own, but if you don't mind it, Scrum is good-enough^tm.
- deleted 4y ago[deleted]
- haxiel 4y agoBackground reading: Defining Kanban and Scrum (since the author skips over it in the article). https://www.atlassian.com/agile/kanban/kanban-vs-scrum https://www.atlassian.com/agile/kanban/kanban-vs-scrum
- ShadowBanThis01 4y agoThanks. I found it annoying that the author never says what kanban is. By leading the title with scrum, you can argue that it’s for those familiar with it. But then the article neglects to describe the alternative it claims is better. It’s akin to saying, “You don’t need yoga; just do twiddlebop right,” and never saying what twiddlebop is. It’s also rife with meaningless declarations, like the one about “pushing decisions to the edge of the team.” WTF is that supposed to mean?
- varelse 4y ago[dead]
- nxpnsv 4y agoDoing kanban right sure is better than doing scrum wrong.
- theshrike79 4y agoAnd doing scrum right is better than doing kanban wrong :D
- nxpnsv 4y agoAbsolutely
- deleted 4y ago[deleted]
- dgdosen 4y agoI like the analogy of using a kanban for managing work to playing poker. It takes 10 minutes to learn, but a lifetime to master.
- klik99 4y agoBeware blanket statements! I work with sound in games and have multiple times tried to do Kanban, both from an internal team and an outsourcing team, because of basically the same reasons mentioned in the article - it's agile and task based, and seems like a good fit to be a "factory" for sound assets. However games are iterative by several orders of magnitude more than traditional tech (I've also been CTO at a more traditional design/consulting firm) and constantly evolving and audio team, both internal or external, end up tightly embedded over the course of 2-3 year long projects, and Kanban ALWAYS breaks down because the edges of tasks are fuzzier than you expect. Scrum (real scrum, not the surface level dogmatism that passes for it in many places) does work better in this situation. I find myself saying this often "The best tool is the simplest one that does what you need it to". I really do prefer Kanban! It's far simpler. For projects that have clear needs and stakeholders it's great. For "factory" type set ups that provide tools to other internal stakeholders it also works great. But for places where the technical requirements are fuzzy the added complexity of Scrum is helpful, since it focuses on OUTCOMES rather than MEANS/tasks. Don't be afraid to try different approaches for different sprints/releases and tweak formulas. You can normalize estimation by keeping it consistent while also changing methodologies. But just because Scrum is overused and misunderstood doesn't mean it's useless.
- jdkoeck 4y agoNo idea what you mean with outcomes vs means/tasks. Just put outcomes as cards in your Kanban board, they don’t have to be tasks.
- dzikimarian 4y agoThat's often to big to be single card.
- Closi 4y agoI think they mean it from a softer perspective - Scrum encourages more time ensuring all the team and tasks are clearly directed towards an outcome for that sprint. Just putting outcomes as cards on a kanban board will not have that same effect in all instances, as it's more about the soft points of engagement and teamwork driving towards that common goal.
- natch 4y agoTo get a known stable known velocity, so many things have to go right. The most disruptive thing sabotaging this, all other things being positive, is typically manager turnover when they each have their own differing ideas on how, and whether, and what, to adhere to. Hold your advice; doing anything about it is not at the pay grade of anyone who will be with the company for more than another six months. Unless… you leave the company. That is the one effective action you can take.
- kstenerud 4y agoKanban is great for systems with predictable output. If the work units remain mostly the same, you can greatly increase flow efficiency and velocity using kanban. It's basically waterfall meets JIT delivery (which is why it worked so well for Toyota). Scrum is for less predictable work, where many/most of the requirements and/or challenges are not well known or defined yet, or are likely to change as new information becomes available. For this kind of work, you need a constant feedback mechanism so that the captain can adjust course as needed while traversing uncharted waters. I currently work in a team that builds code that accesses poorly or completely undocumented systems, and is seeking a market fit for new products. In both of these cases, agility is far more important than velocity, so scrum is the right approach. In previous places, the work my team did was very predictable, so kanban was the right approach. Note: There's nothing wrong with having both in the same company. Team has predictable work? Kanban. Else scrum.
- cloogshicer 4y agoGenuine question: How does Scrum help with less predictable work? From my experience, the opposite is true: New things are discovered during sprints, but at that point it's already too late because that work item has already been estimated in the sprint planning (most of the time incorrectly). Also the arbitrary sprint deadlines don't help either.
- kstenerud 4y agoWhen new information exposes issues with the current piece of work in a sprint, you discuss it, and then change whatever part of the plan no longer makes sense given the new information. Will it mess up the numbers? Absolutely, but only for that piece. And as a result of the change of plans being entered into the current sprint (with something perhaps bumped to make room, or maybe the work itself bumped to a later sprint to give more time to plan for the new challenges) you already have a new estimate. And you have a paper trail of what happened and how you dealt with it. Your velocity goes down and you lose some predictability, but your agility goes up because you can adjust instantly to new challenges. None of these tools are a panacea; you have to thoughtfully decide which trade-offs will offer the greatest benefit for your particular project. The "deadlines" shouldn't be thought of as hard deadlines. They're estimates of what you expect to have done at the end of some arbitrary period. Your accuracy in this should be measured statistically over time. If it turns out that you're consistently under or over, you adjust how you estimate. Ideally you want your estimates to average out to break-even over the course of a year. The point isn't to be able to determine exactly how much work you'll do, but rather to determine with a high degree of confidence (80%? 90%?) when the work will be done, with the understanding that it's not guaranteed (i.e. it's a point statistic). It's a planning tool, not a performance measure (the moment you treat it as a performance measure, it becomes useless due to the cobra effect).
- theshrike79 4y agoScrum is meant to protect the team from changing requirements mid-work and it's a good way to work when you have a "client" that requires "features" to a product. There is a well-defined standard process for them to add things to the backlog and there is a written down definition in which state items in the backlog have to be in so that they get picked up for the next sprint. If the team works with just one client/product, the client can prioritise the backlog. During the sprint they can't give any input or request "just this one quick feature". The work is locked during the sprint. If they REALLY want something, the Agile Manifesto says to drop and delete all ongoing work and start a new sprint from scratch. Exactly zero clients have agreed to that - they really weren't in that much of a hurry with the feature. After the sprint the client gets a demo of what the team achieved. An actual demo with the actual product. Not a powerpoint presentation of an ideal state or a video done in a demo environment. At this point the client can provide feedback and new features and we GOTO 10. Usually a single member needs to be defined as a firefighter who takes on bugs and production issues that can't wait for the next sprint, but we don't tell that to the client. If there is no urgent work, they work on the sprint tasks as normal. -- Kanban on the other hand works if the tasks have no dependencies with each other, like building maintenance or IT/DevOps type stuff. "Install new laptop for Karen with standard package" doesn't require a sprint, anyone on the team can do it. Or "Set up AWS account with ECS for team B"
- RamblingCTO 4y ago> Scrum is meant to protect the team from changing requirements mid-work But this will happen from time to time. People writing tickets or even devs when checking the tickets don't read the related code. So you have a big and important source of uncertainty. Some things are technically constrained.
- theshrike79 4y agoThat's what the backlog grooming and planning sessions are for. The devs who will be doing the work estimate the work. If stuff looks really vague, do a "planning" or "discovery" task on the issue first, where you dig through and maybe even prototype what you need to do. But yes, requirements can change during a spring, but it should be very very rare and not a regular event.
- DotaFan 4y agoLast 10 months we were running Agile Scrum, for rebuilding legacy app. It's an understatement to say we wasted so much time, and PO had so much trouble running that.
- vikingerik 4y agoThe underlying triangle here: Out of time, scope, and quality, you can pick two to specify but you can't constrain all three. Scrum specifies fixed time and quality ("definition of done"), with scope as the flexible variable, as tasks get pushed out of each sprint. Kanban specifies fixed scope and quality, letting time be the floating factor for each task. Waterfall specifies fixed time and scope, with the inevitable result that quality has to give way. There are some applications that Scrum does fit better than Kanban, notably anything tied to a real world calendar, say a scheduled live event or a school year or holiday or other seasonal concern. But yes, most businesses don't need to be time-boxed with Scrum anywhere near as much as they think they do, particularly given how much of that time is always consumed by organizational friction around the time-boxing negotiations. (What happens if you do try to constrain and specify all three? We call that a death march. Actually, time invisibly flexes as workers cram in effort at a higher pace, until they burn out and then you're back to quality implicitly or time explicitly giving way unless you reduce scope.)
- azophy_2 4y agoThis is a good explanation about differences between the three
- sublinear 4y agoIt doesn't matter what methodology is used. The most heavily weighted factor by far is whether the product owner and managers understand the implementation details well enough to keep estimates accurate and mitigate scope creep.
- misja111 4y agoYou don't need Kanban, you just need to do Scrum right. It seems most people who are complaining about Scrum, are really complaining about the lousy implementation of it in their company. Which tends to be the result of lousy management. With lousy management, any process will be a pain. Doing Kanban with a manager behind your desk asking why your feature is not ready yet isn't a pleasure either. There also seems to be some misunderstanding about speed of development and Scrum; some posters are complaining that Scrum slows them down. Yes it does! And this is on purpose. Scrum focusses on delivering business value, not on delivering lines of code that possibly nobody needs. So there are moments in the development process when feedback is gathered from stake holders. This is important, because it gives them an opportunity to adjust what's being built, or even switch to a more important feature altogether. The downside is that this takes time. But the upside is that you will have far greater chance of delivering something that is actually needed.
- rightbyte 4y agoWe are way way past "doing it right". It is agile that is at fault, not the average management on the average company. If the average manager and dev won't be able to do it, then it is a lousy process.
- layer8 4y agoI agree about Scrum, but if you read the Agile Manifesto, Agile isn't Scrum.
- rightbyte 4y agoIt is too vague. Compare to the ten commandments. Half of them are repeating detailed versions of "don't mess with your neighbour" to make things clear. The Agile manifesto should have been written in a similar style ...
- switch007 4y agoIf we all had a dollar for every time we read “you just need to do scrum correctly”, HN would be full of millionaires.
- hatsune 4y agoScrum needs surprising effort from coworkers to understand the system as well unlike common kanban that has existed for eternity. Meanwhile at some stages the stuff just becomes mythical and people stop to implement but rather improvise.
- zie1ony 4y agoUnpopular opinion: if your team is small enough (up to 5 people) you don't need any methodology.
- deleted 4y ago[deleted]
- ido 4y agoIt's sorta like Valve et al having "no management/hierarchy" - there is still one, it's just not codified/official.
- lutarezj 4y agoThe experience i have with scrum is similar to what the procrustean bed suggests. Funny thing -to me - is that usain bolt did not use scrum to win, neither did federer. You can’t go to the moon with scrum. But I do see value in it as long as I drop 80% of what it proposes. Scrum is just a passion killer. We shoud use the ideas from the No Estimates and Accelerate books
- supermatt 4y agoPeople trying to shoehorn scrum into their startup is the problem - not scrum itself It is specifically designed for interfacing with project-external stakeholders. It works well for “project teams” in a large org for whom the project isn’t the primary business focus. e.g. an internal tool to assist with problem X, or a development project for an external entity. There is no other use case for which scrum is a good fit - and it’s those mismatched experiences that always result in scrum hate. I think people just got caught up in the cool name and the certifications and blah. Stop using scrum for the wrong thing!
- _def 4y agoThat sounds sensible. Soo... How do you get your managers to this insight? In my company each team uses scrum and I think no one is really happy with it. Mine certainly isn't. I'm not even talking about the engineers: at least from my point of view everyone involved suffers from it. But I have the impression we lack responsibility for such decisions. Oh well, I think I'm just venting now :)
- liampulles 4y agoScrum is kanban plus bureaucracy. The real underlying challenge is keeping bureaucracy low as an organisation grows.
- BiteCode_dev 4y ago"just"
- cauliflower99 4y agoKanban and scrum are solving different problems. Kanban focuses on the flow of work through the team. Scrum is a framework with the bare essentials to deliver value to the customer. Most scrum teams use kanban to control the flow of work through their team. They're separate processes. What the article is saying is that bad scrum is much worse than no scrum - which is so so true. But good scrum is waaaay better than no scrum. Combine it with effective Kanban (eg. controlling WIP) and you're on your way to a very productive team.
- fogzen 4y agoAs someone who runs a software agency, kanban sounds like nonsense. If you don’t know exactly what you’re doing, for whom, by when, you fail to meet expectations by delivering the wrong thing by the wrong time. There is design & estimation, planning, development, and evaluation phases. End of story. It doesn’t matter what you call those phases. If you don’t do design and estimation, you have no idea what you’re building or any metric for success. If you don’t do planning you have no schedule for delivering it. “I’ll do this feature as defined by a two sentence ticket whenever I complete it” is incompetent and reckless. It’s idiotic. I’ve seen many companies operate this way, and they are constantly delivering the wrong thing by the wrong time (particularly VC-backed startups).
- deleted 4y ago[deleted]
- ShadowBanThis01 4y agoToo bad the article doesn’t say what Kanban is.
- nvarsj 4y agoIndeed. You can even argue that scrum is one implementation of Kanban. Kanban afaik just describes having a swim lane task board. The process for managing that board is left as an exercise to the reader.
- Marazan 4y agoHeavy assumption in the comments that sprints "are" 2 weeks. I've found scrum works best with 1 week sprints. It forces ceremonies to be short. But at thr end of the day the only important parts of Scrum are ensuring the standups are run ruthlessly short, no fat, and that the Retro produces actions that are actually done. Because if you are running proper retros after 6 months "your" Scrum won't look like anyone else's Scrum as it will be customised to your work and team.
- dazsnow 4y agoYou don't need Scrum, and don't have to do Kanban right, you just need to use Pivotal Tracker.
- deleted 4y ago[deleted]
- watwut 4y agoYeah, that is because Scrum is awful.
- azangru 4y ago> As I mentioned before, sprint planning meetings are unproductive because they lead to “designing by committee” and focus on getting estimations right, which is not only a waste of time, but also impossible to do in a stochastic process such as software development. This sentence alone reveals an incorrect understanding of scrum. First, scrum does not "focus on getting estimations right". In fact, if you search through the scrum guide [0], you will not find any mention of estimates whatsoever. Second, the purpose of a planning meeting is to identify what next to work on in order to add the most value to the product. Therefore, the meeting involves the product owner, who has the clearest understanding of the business value of the product at any given point, and the developers, who have the clearest understanding of what's going underneath the hood of the product. Their conversation informs both the developers of what's most valuable, and the product owner of what's doable. Third, in the planning meeting developers, who are actually going to be doing the work, have an opportunity to decide how they are going to split the work, how they are going to collaborate on it, and whether there are any unsolved dependencies preventing them from taking the work into the next iteration. How this can be dismissed as a waste of time is beyond me. [0] - https://scrumguides.org/scrum-guide.html https://scrumguides.org/scrum-guide.html
- JohnFen 4y ago> How this can be dismissed as a waste of time is beyond me. I think a lot of it is because Scrum as practiced is often not like you describe.
- shuntress 4y agoWhat you say is completely true for a spherical team floating in a frictionless void. The reality is that it is quite difficult to break products down into separate features then work on those features separately and in order. Because of this, it's very easy for planning meetings to accidentally become "What did we work on last week? Will this still be done on time?"
- azangru 4y agoSo. The article is comparing Kanban done right with Scrum done wrong. That doesn't seem fair.
- phendrenad2 4y agoIf you ask different parts of your company if Scrum or Kanban is better, you'll get WILDLY different answers from different parts of the business. The CEO has very different needs and wants than the on-the-ground code monkey. We have to take all of that into account before saying we "don't need" Scrum. Yes, okay, you don't NEED scrum, but maybe it's the best tool for the job, given the collective requirements of the business. Judging by the perspective shared in this article, I'd say it's coming from a Team Lead / Lead Programmer role at a small company, where Kanban works great. Once you grow beyond a certain size, almost everyone switches to Scrum. Why? Because it reduces friction with other parts of the business, which want - nay - NEED to slice time up into manageable, trackable chunks. And this goes all the way to the CEO and investors. You may not like it, but it's a very real constraint on your choice here.
- AtNightWeCode 4y agoSome benefits of Scrum over Kanban: * Scrum is less flexible. It is easier to force everybody into a fixed process. Kanban can easily become cowboy development especially with junior devs on the team. * Scrum comes with clear short term goals. Kanban may hide the important milestones. With that said. I think the drawbacks of scrum are just too many. It is inflexible. You have to sit in meetings to solve Scrum-problems instead of real problems. Retrospectives are just magic though when you work with people that are great at agile software development. Ad hoc talks during daily work can never replace that. The velocity one can achieve by constantly improving and challenging the software developing process during dedicated sessions is just ridiculous. But it also have to do with having the right people. 2 hours of people whining about test environments will not accomplish anything. Edit: Btw, problems with test environments is usually down to poor architecture and hard to solve. Design for testing too...
- lowdownfork 4y ago"Scrum shortens planning horizons by limiting batch-sizes to two week sprints. . . Still, because Scrum is a push-based system, it still requires you to do some form of estimation . . . This demand for estimations leads to unproductive and unnecessary estimation meetings." I actually prefer Kanban over Scrum, but none of this matches my experience at all. 1) People plan multiple sprints ahead in Scrum. Not necessarily the full sequence of tasks, but things like telling a stakeholder which sprint their task will be in. 2) Many people are in a situation that's inherently push-based and requires estimates. Scrum is just a way to achieve that. The author gets snarky in the first paragraph about choosing Scrum vs having it chosen for you, but really . . . most people know full well that Scrum was chosen for them, and that it was chosen for planning purposes. And that they do tasks because other people need them done, not because they had some free time. Heck, the whole project usually exists to serve the needs of others, not the joy of working fast. 3) Even in Kanban, we'll usually have basically the same grooming meeting. That's because the meat of that meeting is sharing information and thoughts about what the upcoming tasks involve and discussing whether and how to break them down into sub-tasks.
- nineteen999 4y agoYou don't need to pick a particular flavour of Agile, just chuck it in the bin, the term is done. Along with devops.