14 ms·
Agile won the war but lost the peace
- maxxxxx 8y agoThis always happens with promising technologies or methodologies once big companies get their hands on them. OOP was a great idea until it turned into a strict religion, Agile was good until it turned into a micromanagement system, the internet liberated people until it turned into a surveillance machine, collaboration is good so we got a workplace with open offices that's so distracting that it's hard to get work done. Watch the same happen with FP or things like diversity. Companies are basically dictatorships that want to control their employees ("resources") and everything else so it's pretty natural that they will distort every new movement into a tool to extend that control.
- spaceribs 8y agoI think it's easy to look at the short-term and miss the larger picture. The printing press being the only other well documented time of this explosion of knowledge/technology allows us to see that no matter how power expands and then coalesces, it takes the good ideas, fragments away, and then repeats the process as a sect of the greater power.
- brightball 8y agoSprints are where all of the issues with agile really come from. Constant arbitrary, meaningless deadlines that serve no purpose but create rushes, tech debt, missed “commitments” that serve as a meaningless metric to use against teams while made commitments give no benefit. Everything around sprints to try to avoid the negatives results in huge wastes of time in meetings attempting to plan better rather than actually getting work done. Sprint are the root cause. Just use Kanban and you eliminate most of your problems.
- edem 8y ago_This_. I've been advocating Kanban for years. Why try to adhere to rules which you don't need at all instead of having a non-restrictive framework which is adaptable?
- mbesto 8y agoFair, but sprints are effectively what have forced a lot of software dev organizations into actually thinking about making tasks bite-sized....which was one of the problems (both conceptually and logistically) about waterfall.
- TheOtherHobbes 8y agoThe lack of feedback breaks classic waterfall. You get a plan, and the plan is assumed to be correct. Of course it never is. As mistakes are revealed, unexpected challenges appear, and requirements are updated or clarified, the plan unravels instead of adapting. The only real benefit of Agile is that it should - in theory - allow the plan to be modified, so projects can be steered towards a target instead of being treated as fire-and-forget. (And miss.) Task granularity should not be a specific benefit - it should fall naturally out of competent goal-based planning in whatever paradigm is being used.
- walshemj 8y agoI've never see a waterfall process that did not have feed back.
- octorian 8y agoBut not all tasks can be made bite-sized. Or more specifically, sometimes the bite-sized pieces aren't "complete enough" to be a valid unit of work to be nicely wrapped up and finished during a sprint. What happens as a result, is that more major tasks never get sufficient priority to actually happen. This can easily lead to an incremental "refuctoring" of the code base, where you have a lot of individually-nice bite-sized tasks that, in aggregate, turn the source tree into a total mess.
- umvi 8y agoIn defense of sprints, not everyone is the same. Deadlines for me are a strong motivation to get things done, whereas "no deadline, just do it at your own pace until it's done" will cause me to procrastinate and get it done much more slowly. There is no silver bullet for software development process. It takes hard work and flexibility to optimize your team's work flow.
- yebyen 8y agoI've been reading "It Doesn't Have to be Crazy at Work" and they have a chapter about this. Deadlines are great! Estimates are terrible, and humans are terrible at estimating. Scope needs to be elastic to accommodate this fact of life. If the project is not done in the 6 weeks you set aside for it, just ship something anyways and move on. It was only worth 6 weeks when you planned on getting it done in 6 weeks, so why spend more? Go ahead and plan another sprint if it turns out what you were able to build in the time allocated wasn't enough, and you really need more. (Put it up against the other opportunities you have, and give them all a fair chance at those finite development resources, something else might also turn out to be more important.) Just don't spend forever and drag out the deadline, throwing off the timeline for whatever you had planned to do next, because you needed more time for the thing that underestimated how big it was, so it wasn't really possible to do that whole thing in only 6 weeks. The release that is reduced in scope might be totally insufficient, or, it might be just what your users needed! The knife also cuts both ways – if you're willing to accept that project scope can change in either direction, you can occasionally deliver things early too. I really like everything about this book.
- TheOtherHobbes 8y agoIf you set aside 6 weeks and it takes 12, you suck at estimating. Not only are you likely to ship a broken product, but you also have no way of making intelligent business decisions about possible projects. Project A will bring in $X. You estimate 6 weeks. It takes 12. Project B will bring in $Y. You estimate 6 weeks. It takes 7. If X is similar to Y and you bet on the wrong horse, you've dented and/or sunk your cash flow for no reason. Saying "Humans suck at estimating" is nonsense. It's a skill that can easily be improved - usually at the cost of some up front planning - and there are plenty of resources to help you with that. The real problem with Agile is that it gives management an excuse to do no estimation at all. Some alpha-wannabe manager bangs their fist on a desk and says "I want this in three weeks". Instead of saying "You're insane" teams are pressured into trying to make up for someone else's laziness and lack of contact with reality.
- matthewmacleod 8y agoDon’t run sprints if you don’t need them - that’s the answer. But honestly, I’m not sure what the problem is. I’ve found they they’re perfectly suitable at providing: - an opportunity to check in with a wider team and demonstrate features. - the chance for the development team to periodically review progress and identify any recurring issues. - the chance to plan upcoming work and identify any external tasks that need to be taken care of. Is the problem maybe that some organisations are over-using the “commitment” aspect as a metric? To my teams, “commitment” has generally meant “what we have agreed among ourselves we will be able to deliver in a unit period”. The metrics are purely internal, and useful for allowing us to see if we frequently over- or under-estimate how much work we can do; the sprint is really just the period of time across which we measure and refine.
- spiritcat 8y ago"The metrics are purely internal" bwhahaha, good one!
- matthewmacleod 8y agoWell, I'm describing how my teams have worked, and it's true! I'd be even stronger on that point – not only should metrics probably not be available outside of the team, but they are even completely without meaning if they're used outside the context of the team. Maybe one of the biggest problems people experience with Scrum or Agile generally is the inappropriate use of metrics.
- deleted 8y ago[deleted]
- freedomben 8y ago> Don’t run sprints if you don’t need them - that’s the answer. Except the people being forced into the sprint aren't the ones with power to opt out. It has always been my experience that there is a "product owner" or agile coach or some other title who makes the decision, and isn't one that has to live inside the system they create. So I agree with you in theory. Some people thrive in the sprint, others suffer and struggle. If everyone could opt in or out, it would be great. But in practice I've never seen the ability to opt out.
- deleted 8y ago[deleted]
- ken 8y agoLast week, at the end of a work day, we started talking about what the schedule was going to be for Saturday (not a 6th work day -- we're not on a M-F schedule here). Someone asked "Is it a goal-based day or a time-based day?" And there was an answer ready! Fantastic. In 20 years, I've never heard anyone ask that in the software field. In software, I've always been expected to work as fast as possible at all times, and when we get near an (arbitrary) deadline, to stay late as needed. Software is full of young people, and people who have never managed any kind of team before. I have no problem working for someone younger than myself, but I do think that people should have experience managing some kind of team before they're thrown into the deep end. Software is much more complex than almost anything else we make, and it's no wonder that just figuring it out as we go along has yielded less than stellar results.
- acoard 8y agoI've often heard this (or a similar?) distinction as "man-hours" vs "calendar time"
- thaumasiotes 8y agoken doesn't describe what a "goal-based day" means, but I don't see how it could match the distinction between man-hours and calendar time. The difference between today and tomorrow is one day of calendar time. If you have a team of 3 people working 5 hours a day on a given project, then in one work day of calendar time 15 man-hours of work will be done on the project. Man-hours just aggregate calendar time contributed by multiple people (and ignore calendar days when no work occurs). But none of that has anything to do with goals.
- lkrubner 8y agoI've seen some young people who are very good managers, but I've also seen some absolute disasters. I've also seen some older folks who are absolute disasters. I shared a story about both kinds of manager in How To Destroy A Tech Startup In Three Easy Steps: https://www.amazon.com/Destroy-Tech-Startup-Easy-Steps/dp/0998997617/ https://www.amazon.com/Destroy-Tech-Startup-Easy-Steps/dp/09...
- LoSboccacc 8y ago> Sprint are the root cause. I disagree. there's nothing inherently wrong with short iterations or a predictable release window. trying to do agile with fixed budget, fixed requirements and a fixed timeline is the core issue. most of the problems with agile, including "devs having to do this much tasks or die" within each iteration, comes from trying agile on an inflexible plan.
- rooam-dev 8y agoI came to a similar conclusion and prefer Kanban to Scrum. If there are not enough tasks you pull from backlog, if it's too much then they get finished in next sprint. Work never ends, so why the need for extra overhead to group it into 2 weeks? I always see it as a "marathon", constant sprinting is no good long term. However, Kanban works as long the team knows priorities and can choose between good and over kill solution, which is easier said than done. Working in a good pace without a deadline is challenging itself, since you think you have all the time in the world.
- _hardwaregeek 8y agoI hate the term "sprint". The word gives an impression of desperation and short term thinking. You don't sprint when you're running a marathon; it's not sustainable. It's a superficial complaint, but names do matter.
- matwood 8y agoLet's rename it to 'checkpoint' then. Even in a marathon a runner is checking their time to where they are every X miles. The runner then adjusts their pace if they have a goal time. In software a checkpoint should result in the same behavior.
- jrvarela56 8y agoJust change the name to 'iteration'. Removes the speed/intensity analogy and reinforces continuous improvement.
- sonnyblarney 8y agoI really disagree with this. Sprint objectives are by no means arbitrary or meaningless - or any more so than other deadlines - they have value to the extent they are intelligently formulated. Sprints have a very important operational dynamic, in that they set a fairly clear, achievable, short term goal. Software is always a pandora's box, and left to their own devices, a lot of devs could work on the smallest thing ... forever. We are all guilty of this. Long term milestones (i.e major product iteration) are hard to internalize, they are vague to each individual even if they have meaning at scale. Sprints provide the means for large things to be broken down into achievable pieces, which much more strongly enable small teams and individuals to focus on that specific outcomes. Maybe they shouldn't be called 'sprints' maybe just 'mini milestones' or something ... but they are useful. Or 'waypoints'. Getting lost in a sea of software is very easy ... so setting 'waypoints' I feel is very, very useful.
- bb88 8y ago> Sprints have a very important operational dynamic, in that they set a fairly clear, achievable, short term goal. Lately, the trend with those using Jira in large organizations is to just "carry-over" what's not done in the current sprint into the next. And so instead of talking about why something didn't get completed, and how to resolve it quickly (move it to someone else, change the way it's done, postpone it until something else makes it easier), the work snowballs, with even more work getting piled onto the sprint. That's because while the dev team is agile, management deadlines often won't budge. The other problem is dependency upon another process/service internal to the organization that is not on your sprint cycle. Typically they have other, different priorities, which don't match yours. So they may get around to it eventually, which might mean a week to a month typically. I think Kanban is in someways vastly superior in these cases. You can still do "waypoints" at say every two weeks to see how things are moving along, but at some point if your company isn't "agile" then it really makes no difference if your team is.
- brightball 8y agoChecking in is useful. The problem from sprints comes when each one is treated as a deadline instead of just a point to check in, evaluate new information, potentially pivot. When they are treated as deadlines, the problems come. And there is no reason you can simply forgo sprints entirely...and still check in, see how things are going, pivot, evaluate new information. To this point in my career, I’ve never seen sprints present when they didn’t go down the destructive path for teams.
- majormajor 8y ago"Planning better" is a hugely valuable thing, if you can pull it off. You'll end up with less pressure, happier stakeholders, and less frustration with your own output. Even in a purely selfish better-for-the-team way: an accurate plan and capacity projection (relatively - if you have bosses who expect perfection here, that'll bit you) makes a great input into decisions about headcount, hiring, and project allocation. If you can't plan well enough to know you need to ask for help, you're screwed. Agile as I've seen it in the wild is easy to twist into "plan more verbosely" instead of "plan better," though. The most recent way I've seen this manifest is coming into a team that planned out each ticket in great detail when it came to execution - gotta maximize that committed/completed ratio - but invested very little in making sure they were planning the right thing. Someone would ask for something, it would become a ticket. But whether or not that was the right thing short-/medium-/long-term? That's a conversation that didn't have anywhere to happen. Another is confusing "producing more estimation artifacts" (subtasks, hour allocation, etc) with "investing the right amount of time in planning." Going from a 30 second story point estimate to a 2 minute subtask breakdown in sprint planning isn't what it takes to make an accurate estimate for a project.
- joseph8th 8y agoSounds like management is using sprints to enforce deadlines and releases. Our team uses them to improve our ability to estimate, which in turn requires us to think each set of technical requirements through and anticipate issues before we start pounding keyboards. We use them to structure our work, but decoupled them from releases. The Dev team owns the sprints, but the business owns releases. DevOps uses Kanban however, because it works better for them. That makes us more flexible. Agile. It's been a years-long process but I'm really happy with our "Agility" these days. Our sponsor is the VP of Tech and he gets it (used to be our QA lead). If we have rollover we talk briefly about estimating better but it's not the end of the world, because we actually have gotten better at estimating. Some sprints we nail it. Other times we miss, but management isn't using those metrics as a bludgeon so it actually helps us to work smarter.
- sebazzz 8y agoThe problem is not agile, it is an all-alige approach. It is at least in our case. Sprints are feature-focused, which leaves little time for software development craftsmanship: reducing technical debt, updating outdated dependencies etc. To give some context: We have multiple pieces of software we build and maintain for multiple clients. When a client requests some features, they buy some sprints and we do the work and then it's done. During the life cycle of the software there is a maintenance contract for service and support and resolving bugs. This does not have much room for software craftsmanship either. This is just where I work,but I can't imagine we are the only one working like this. This is an implementation problem, not an methodical problem. One of the ultimate causes is that our org is project based, so no project, no work for that client. And the software quality suffers IMHO.
- kamaal 8y agoAlso 'move fast, and break things'. Without understanding what you are supposed to do. You move a lot without going no where, with a lot of broken things.
- mcv 8y agoSprints are often misused and misinterpreted. They are not hard deadlines. A deadline is when there's going to be a real problem when you don't make it. When a new campaign, shop, whatever opens, the corresponding website needs to be there. That's a deadline. A sprint goal is meant to provide focus. You've got something to work towards, but if you don't make it, you don't make it. Presumably there was a good reason you didn't make it. It's good to examine that reason to see if that reason can be taken away, or otherwise it can be taken into account in planning. But it's not the end of the world if you don't complete a sprint on time, and you should certainly not work late to complete the sprint. I've worked in very successful teams that never finished a sprint on time. I think that's totally fine. It's not about the deadline, it's about the focus.
- vinceguidry 8y agoMeta-point: Nothing wins the peace, peace is just war that's managed to make itself sustainable.
- jacob019 8y agoWhat a sad perspective.
- MaxBarraclough 8y agoDisagree. Peace means not swinging the axe. If you can't tell whether the axe is swinging, you shouldn't be applying a war/peace metaphor. Also, war can be sustainable, especially if it isn't total war. Look at Europe a few centuries back.
- kylnew 8y agoDo devs really hate agile? I’ve really enjoyed it in workplaces despite it not always being perfect. I’ve never felt micro managed either, just regularly managed. I understand that maybe some want more free will to pursue problems the way they feel is right, but it’s a job at the end of the day and you are a human resource being paid to deliver results. Make sure you’re being compensated enough, at least to not feel like you’re being exploited.
- v1000a 8y agoI'm not a human resource, thanks. Yes, competent devs hate agile, incompetent talkers love it because it hides their deficiencies and they can shine in the useless meetings.
- matthewmacleod 8y agoThat’s a gross oversimplification. I’m a competent, experienced developer. I’be worked in agile, waterfall and “faux-agile” teams. The agile ones have been the best - they adapt quickly to change, have good estimates of progress, and keep all of the team members and wider stakeholders involved in the project. If there are useless meetings in your development team, remove them. If you can’t remove them, then your team is being mismanaged and no form of development methodology will fix that. And also, bear in mind that even among developers on a team there are different sets of skills and preferred working patterns. You may not need some interactions, while other team members benefit from them; remember that the useful measure is the amount of work the team as a whole can achieve!
- cc81 8y agoMy experience is that it is more likely that "hero devs" who love to do what they think is important rather than what the team needs will hate any attempt to reign them in.
- mathieuh 8y agoI hate it. Constantly being pressured to move some stupid card or add some stupid tag so people’s graphs look nice. I just want to get work done, Scrum just adds overhead.
- marsrover 8y agoAgile is like communism. Looks good on paper but you end up in Soviet Russia.
- tannhaeuser 8y agoDo you know any substantial software in wide use that was created using "agile" methodologies?
- lordnacho 8y agoI never saw agile as anything other than some useful observations about project management. Get feedback fast, sync with team members often, don't try to plan the whole thing in one go. Any particular incarnation of it, say Scrum, is going to have issues when applied to real world problems. Guidelines like "get quick feedback" are useful, but decrees like "one week sprints" can get tyrannical. Luckily a lot of people seem to understand that and I've never met anyone who insists on doing exactly according to some specific scripture.
- Aeolun 8y agoI think the problem with Agile as implemented by larger corporations is not anything described in the article, but that it’s just fundamentally antithetical for corporations to work agile. There is just no way that some salesperson is going to be able to sell a product that’s going to be developed in collaboration with a customer in 2 week increments (unless the customer is already specifically dealing with a software consultancy). They sell a package of ‘this is everything the product is going to do’ and then somehow try to squash that waterfall list of features into ‘stories’, and call it agile.
- rusk 8y agoIn agile, it’s the salesperson that’s the customer, not the actual “customer”. Unless you’re doing professional services or something agile is an internal matter. As with many things the less your customer knows about your inner machinations the better!
- PretzelFisch 8y agoIsn't this a problem with the sales team not being able to sale the current product?
- Aeolun 8y agoIf there is a current product. I think they’re generally trying to sell a future ‘better’ product.
- tyurok 8y agoIt's also the problem that software is not strictly a product, but a mix of service and product. There's the core product that you are selling (say e-commerce) and there's the customization service that's been sold to increment the product per-customer basis. Traditional sales knows how to sell either a product or a service, hardly the mix of them, which makes software special (but not unique).
- williamdclt 8y agoThat's just factually false: to give a counter-example my company (~200 people) does exactly that (1 week sprints, though). Except that we don't sell "a product", we sell time. We'll do everything we can to help you getting a product out of this time, but if you can't, you were doomed from the beginning. It's just a different thing to sell for a salesperson, they have to adapt. But it works.
- marcus_holmes 8y agoSo true. But then, Agile solved problems developers had, not project managers, sales people, or accountants. In fact, it caused those people more problems. It was only ever going to be actually implemented in developer-run organisations, because only then are developer problems more important than everyone else's problems. Maybe that's the answer - more developer-run organisations.
- hippich 8y agoAnd finding developer-run customers. I wonder how many such customers exist.
- wirrbel 8y agoI think agile is usually presented as an approach that tries to reduce a split between the business and the developers. If you take the business out of the equation you usually get development models that just-for-fun open source projects have. Waterfall is cool with customers and sales, at least it was if it wasn't risky. So agile is a risk minimation strategy.
- geezerjay 8y ago> Maybe that's the answer - more developer-run organisations. I don't agree. Once you put a developer in a project management role, he starts to experience problems associated with managing projects and using solutions to those problems. When that happens, the developer ceases to be a developer and becomes quite plainly a project manager.
- lostcolony 8y agoThe whole idea of a sprint commitment, of pointing, of measuring velocity, of a sprint demo, is in deference to the business need to plan and adjust priorities. It does them based on realities, whereas older more waterfall style methods tend to due them on hypotheticals, decisions made with the least amount of information, and then the business wonders why the heck everything is late.
- octorian 8y agoI was once on a project where the managers loved it, because it gave them the ability to micro-manage a project like never before. They got daily status meetings, and bi-weekly cycles to adjust things.
- lowry 8y ago«Хотели как лучше, а получилось как всегда» is better translated as "We tried our best — you know the rest".
- menzoic 8y agoWas hoping the author would explain what people get wrong about agile.
- Farradfahren 8y agoAgile is basically the average guys "Wing it with cooperation" and wins like OO by redecorating the default human behaviour pattern as a ideology.
- XorNot 8y agoI've yet to see anyone actually do Agile where the tasks were broken up into reasonable increments. All of my Agile experiences involve a project manager throwing a sentence up on the board for what they want done and saying "yeah I think it'll fit in this sprint" for something which no one has any idea how long it'll take because the scope is unknown and no preliminary investigation has been done (a process which would take maybe a week). "Task estimation" for sprints never seems to involve any actual data on which to base the estimates.
- rusk 8y agoI’ve experienced scrum done “right”. Company I was with made it a strategic thing and set aside time and money for the org to make the transition. It actually worked quite well in the end but it was a lot of work. It’s an outlier though - I’ve never come across a company before or since that would go to this much effort. Usually the conversation with management about implementing agile ends at the point where they realise the upfront costs.
- hippich 8y agoThere is a concept of "spike" work. Basically, when you do not know what it takes to implement something, you work on a "spike", the result of which will be new stories better describing what needs to be done.
- jasonlotito 8y agoWhat happens when the spike is done early in the sprint. Do you just hold off a week or so until you can report back? And who works on those follow up tickets? The person who did the research? They've had the most experience, so that makes sense to me, but I've been told everyone should be able to pick and choose, and if I don't grab the tickets fast enough, I'm sol.
- MBCook 8y agoPart of the spike should be documenting the results so that anyone else can use them if there are the person who picks up the next ticket. If the person who does it just remembers it themselves and doesn’t do anything to help the other developers then they haven’t completed the spike.
- bigbluedots 8y agoUsually the claim is that if Agile is not working for you, you're 'doing it wrong'. This article is no different.
- draw_down 8y agoIs anyone else tired of this story by this point? Agile was wonderful and beautiful, the problem is all the people who didn’t do it right. We get it. There used to be a joke, “this job would be great if it weren’t for all the users”. It was supposed to be a joke.
- ScottAS 8y agoSome Buddhist wisdom: In life, we will always find “shining cities” to chase. The perfect house, the perfect job, the perfect romantic partner, the perfect software team. But, like a mirage, when we reach these goals it seems that the thing we thought was perfect is actually riddled with flaws. “The shining city” is purely a mental construct, one that gives us structure and purpose, staving off “existential nausea” - the anxiety that comes from living a directionless existence. The way to everlasting peace is to be able to acknowledge: “we live in the shining city right now. Everything is operating according to the laws of physics, humans follow human nature and their genetics. Everything is exactly how it should be.” But this isn’t “giving up”. It’s ok for us to have “shining city goals”. It’s human nature. It’s fun and allows us to experience a journey. But at the end of the day when you see the mirage fade, smile about the journey and the experiences you had along the way.
- booleandilemma 8y agoThe way to everlasting peace is to be able to acknowledge: “we live in the shining city right now. Everything is operating according to the laws of physics, humans follow human nature and their genetics. Everything is exactly how it should be.” This is not wisdom, it’s nonsense. If we followed this advice 2000 years ago we would still be practicing open defecation and dying at the age of 30.
- zkomp 8y agoIt is much more nuanced. Peace is about: accepting and appreciating what you have, and don't have (i.e appreciate the actual reality). Progress is making it better. You will need both, change and the ability to see what is good and works in the current reality.
- ScottAS 8y agoI bet if you measured contentment levels then and now you would not find much of a difference! In fact you might find people are less content now than shitting in a ditch 2000 years ago. But I did not mean this as an excuse for “non-progress”. Humans will “progress”, it’s their natural instinct and drive. It makes more sense to make our lives easier than to make it harder. But the shining city doesn’t exist, and there’s nothing that will significantly increase our internal contentment but winning the internal battle of acceptance.
- dberg 8y agoTo me, I think everyone took the processes WAY too literally which caused the whole big "A" Agile versus little "a" agile. I have seen many orgs get super wrapped up in all the typical nonsense of stories "falling over", religion about who owns the backlog which takes away autonomy of the team, religion about the process for breaking a sprint as new discoveries are made, arguing over product work versus addressing tech debt or working on automation, etc. You end up focusing more on "being agile" than delivering new features. I 100% agree with the other comment around "checkin" points so that work doesn't linger forever, but the forced short delivery boundaries very likely slow teams down overall especially when all the process overhead of points, backlog grooming, standups, sprint planning, demo session, etc are all factored in and mandatory every 2 weeks. Commit to some scope, on some cadence/date, loosely check in on progress, and adjust as needed as a team. Deliver as frequently as possible and demo your work when you can/should.
- MBCook 8y agoThis sounds pretty accurate to what I’ve witnessed. I’ve seen Agile done well, which I really liked. Mostly what I see is water scrum. It’s important to pack every single thing you can into a sprint based on your estimate of points, otherwise you’re wasting precious resources. Of course that means you never get everything done so huge chunk of the sprint always rules over. Everything is dictated from the top, there is no autonomy on the part of the team (or almost none). As bad as all this is, a quickly falls apart whenever something doesn’t go exactly the plan. In other words, constantly. So you just get further behind and more things roll over into the next sprint. They’re “agile”. They hold demos of the tiny bit that got done and congratulate themselves. Because they don’t do waterfall anymore. They GET IT. But none of the benefits. Because that would require actual change.
- wgerard 8y agoThe problem, obviously, is not Agile. This will, naturally, cause hairs on necks to rise waiting to scream back "What are you talking about? Of course Agile is the problem!" But really, the problem is that any business trend/fad is inevitably doomed to become a hollow shell of what it was intended to be. Or more pointedly: Businesses don't really want to overhaul their development process, and any new process integrated will inevitably become just an extension of whatever they were doing before. This is basically what the article's saying without directly saying it. I mean, the very first phrase in the Agile manifesto is: > Individuals and Interactions over processes and tools And yet see how many anecdotes in this thread are about how the most annoying part of Agile is the rigid adherence to certain processes. If 1 week sprints are too short, change them to 4 week sprints. Figure out the cadence that makes sense for your team. That's what Agile is supposed to be about. Regardless of whatever Large Co wants to call their development process, let's stop calling it Agile and start calling it what it really is: Waterfall with a Kanban board and shorter deadlines.
- ken 8y ago> The problem, obviously, is not Agile. Sure, any true Scotsman can see that. What reason do we have to believe that Agile is so great, if (as you point out) most business aren't actually doing Agile?
- wgerard 8y ago> What reason do we have to believe that Agile is so great, if (as you point out) most business aren't actually doing Agile? Read the anecdotes on the other end. People who have reached the shining city the article describes. It's a nice place to be. There are a few in this thread alone. I've personally experienced it as well. It's great. > Sure, any true Scotsman can see that. To continue the analogy, this is roughly the equivalent of declaring myself Scottish because I'm wearing a kilt and playing bagpipes. I have no connection to the country of Scotland presently or historically, but I'm doing the things that Scottish people are stereotypically associated with, so I must be Scottish, right? At that point, I think it's fair to call my bluff.
- coldtea 8y ago
- amai 8y agoAgile always fails, because bookkeeping and financial processing in companies are not agile. Contracts with customers are also not written by sales with agility in mind. So in case time/money runs out agile processes and rules (like "never break a sprint" etc.) will always be ignored, because finance needs the numbers and the customer was promised a fixed feature set at a specific date for a specific price. mandatory Dilbert Comic: https://www.flickr.com/photos/lucaminudel/6059269914/ https://www.flickr.com/photos/lucaminudel/6059269914/
- jdmichal 8y agoI don't think that's a real comic. Looks like the Dilbert site used to have a feature to modify / make your own comics, but I can't find it anymore.
- projektfu 8y agoPeople who work in sick environments will not be saved by Agile. These techniques are meant for teams that already have members who trust each other, in a company that trusts the team, to work with customers they know, who would like a usable product that they can develop and extend the requirements for as they learn more about how it will work. It helps prevent the sicknesses that come from attempting to do all this up front, where an eager team and an innovative customer try to specify everything up front and nail down a price tag right away. It should be sold to management as a form of risk management, not as a way to extract more value from a fixed amount of dollars. If you have $4 million to spend, and you spend that up front, you may waste $4 million. If you spend it bit by bit, and have a functional system after every few weeks, that you can migrate to if you like, then you have not wasted any money, even if you end up throwing it away partway through. I agree with anyone who says the problem with Agile is that it is watered down. It was a least-common-denominator of all the various similar techniques, and I think a lot was lost by encouraging people to adopt Scrum instead of eXtreme Programming. Nevertheless, I've consulted on a lot of projects and there are environments in which I would not want to attempt to implement any new methodology. The people already hate each other and the system is totally sick. They need something more like Deming's management techniques where they get the top to commit to empowering the bottom, retrain and move out people who are in the wrong job, and get a remaining nucleus of players who trust each other to implement a new method (or their own). What ends up happening is programmers come into sick environments, run by "Agile" managers, and say that Agile is the problem and if they could just go back to their office and ignore everyone they could get it done. They're probably half right, in that they also need the full support of the customer. Since programmers are a noisy bunch, they complain far and wide about Agile, saying that it's the cause of all the diseases in their world. But sick systems often have names that are misleading. Deming once saw a poster on a client's break-room wall (or something) touting "Total Quality Management" and he said something to the effect of, "I hope that you aren't predisposed to think I'm wrong because of this", meaning that someone had already set up a sick system and claimed it was inspired by Deming.
- tychomaz 8y agoYeah it doesn’t mean “agile deadlines”
- cjblomqvist 8y agoFrom my understanding, Agile was developed by developers sick of the rigid and static waterfall model and the problems caused by such a model. In discussions on Agile I often see a lot of complaints about managers not doing it right, wrongfully expecting developers to commit to certain things and then actually deliver on that. As a manager, I must say I feel a little bit offended. Not only did the developers specifically ask for Agile in order to fix the issues with late projects that doesn't fulfill their purposes, they are then telling us in threads like these it's our fault. What I read from these comments is a lack of understanding and ownership of the problem, and capability to solve it. To sum it up: Problem: Missed deadlines/cost overruns and lack of success in fulfilling the actual problem. Solution in theory: The theoretical, engineering/developer, solution to the problem: Less commitment and more flexibility. Basically set the right expectations that we'll drive in the wrong direction and then need to correct it rather than continue because that's what's originally agreed. The "solution" in reality: Less commitment and less responsibility and ownership of the business situation (which hasn't gone away and never will). What happens: Less focus on the original problem. Developers thinking that deadlines and not fulfilling the purpose is even more something that is the problem of managers, and not developers. When shit still goes south because developers are still often not any good at tackling the original problem (although the promise was made by them it'll be better if they run the show), they (as obvious from the comments here) still put the blame on management. In other words. Developers thought they were better at solving a problem than a person in a role dedicated to solving those types of problems (compared to developers where it's not in focus at all), still blames management when their proposed solution failed. Ironically (but very logically) the least capable are the ones complaining the most and owning the problem the least. What I believe has caused the situation: An immature industry (due to young age), a complex problem and a lot of demand for developers making companies/managers not having enough leverage to be able to pressure devs into focusing on the right thing/development (the rockstar mentality). Plus of course inexperienced managers that doesn't dare to take control over the situation. The worst part of it all is that it takes away focus from the actual problem, and hides a lot of incompetence (both on the manager and the developer side) which I find is often a root cause (and my understanding is that science agree with me - which and how correctly you use a specific methodology/process is not strongly correlated with overall success. PS. I still believe Agile is good in many cases and there a lot of smart developers doing Agile with great results, but there are equally a lot of people who believe they at better at solving problems they are perhaps the least capable of. What's really sad is that many of those people are actually quite good developers.
- Animats 8y agoGood point, bad article. He never gets to the "why".
- ereyes01 8y agoA big insight for me about where Agile seems to work and where it doesn't was learning about the Cynefin framework [1], which tries to characterize different states to guide the style of organizational decision making. When viewed through the lens of Cynefin, Agile seems to make sense when you've narrowed down a problem space you want to tackle, but you still require rapid iteration and experimentation to finish defining all the finer points of the goal (the liminal state when moving from Complex to Complicated). My impression and personal experience of Agile being a bad fit seems to be associated with a misunderstanding of the decision domain, and the general Agile "religion" that has arisen where it's applied uniformly to every situation. [1] http://cognitive-edge.com/videos/cynefin-framework-introduction/ http://cognitive-edge.com/videos/cynefin-framework-introduct...
- vannevar 8y agoThe title is a nice turn of phrase, but there's no real content in the article, just a series of unsupported assertions painted over with a sense of wistfulness. It reads like a nice proposal for an article that has yet to be written.
- yumraj 8y agoI'm my experience, the irony is that Agile is agile about everything except itself. Companies adopt scrum, after reading a book or worse hiring consultants, and try to follow it by the letter without applying any intelligence or taking into account that one size rarely fits all. Personal anecdote from working at the largest ISV, which went gung-ho on scrum such that careers called scrum evangelists were created, engineers and engineering managers became scrum masters and the program managers, jobs that should have become obsolete to an extent as scrum mastersv take in lots of those responsibilities, started doing who knows what. But of course anyone saying anything against the scrum was a dinosaur.
- OnlyRepliesToBS 8y agowhat terrible actualized results avoid anything to do with this trainwreck
- gfs78 8y agoJust history repeating itself. They are rediscovering the PMI ad-hoc. Not because the Agile ideas weren't better but because human and hence organisational dynamics still are and will be the same. No surprise then, that as Agilists are gaining traction and power they are making their Agility more rigid and dreaming of Chief Agile Officers and roles like that. Organisations have power structures and position there determines progress and survival. They have to de-agilize agility to survive. If not they will have nowhere to go, nothing to latch onto when things go wrong
- luord 8y ago"Agile" hasn't even looked like a word to me in years. It's become nearly meaningless.