News for hackers. Stuff that matters.
Re:In a nutshell, why do a lot of developers dislike Agile? by trentnix on Saturday August 05, 2017 @01:47PM (#14936881)
Because few organizations actually enable real Agile development. I did some "Agile coaching" in a previous life and time and time again I'd see teams embrace the cosmetic parts of Agile - daily standups, iterations, retrospectives - but workflow was still much the same as it always was.

Agile, done right, is more about how work is broken down into consumables and deliverables. It's about clear prioritization and freedom to focus on the task at hand. But most development teams would iterate aimlessly, while the organization around them continued doing business as usual.

To successfully embrace Agile, the entire organization has to do so at some level or another. You have to break requirements down into pieces that can be consumed in an iteration. You have to prioritize clearly. And you can't change priorities until the iteration is complete.

Additionally, many software teams misunderstand how they work. I can't tell you how many times a team would insist to me they were using a waterfall process, but when I asked them to describe the previous workday they'd describe end-to-end firefighting. When I would introduce Agile and the controls that it brings, they would react negatively expecting that Agile was some magical organized free-for-all.

Additionally, lots of consultants made money off of the promise of Agile and the cult of Agile. They didn't provide practical solutions, and organizations resisted change. So much of the indigestion that developers have regarding Agile is due to their own experiences with organizations that bought the promise of Agile but didn't do the necessary work to make it successful.

Re:In a nutshell, why do a lot of developers dislike Agile? by Tomis02 on Saturday August 05, 2017 @02:45PM (#14937219)
> real Agile

Heh, classic response. Whenever your project fails, your coach tells you it's your fault because you didn't do real Agile. Same with OOP, whenever your code inevitably becomes a tangled mess of classes, you will have all sorts of gurus making metric shit tons of money from books and consulting telling you you didn't do real OOP.

Guys, please, can you just admit there is no recipe for success (rhetorical question, of course you can't, that's where you money comes from, maybe you even believe your own bullshit)? There is no real Agile and OOP and other crap that I forget, they're just buzzwords that, when applied long or hard enough, produce shit. If you had kept you project to an absolute minimal level of Agile and OOP, it would probably still be alive and kicking. But you didn't, because you jumped on the bandwagon, you used religiously whatever was popular.

> Agile, done right ...

Yeah, heard that a thousand times before. Sadly, younger developers fall for this all the time, so shit grows exponentially. I'm aware my opinion has always been in minority but whatever.

Re:In a nutshell, why do a lot of developers dislike Agile? by wpietri on Saturday August 05, 2017 @02:52PM (#14937252)
I have done it right. It worked well for me. I've been on happy teams that produced good code: high quality, high test coverage, good for users. We did technical work that I'm still proud of. And we believe that was true because we paid careful attention to how we were working and improved it continuously, using a lot of techniques from the Agile movement.

I grant that there's no one right way. There are many, and they depend on circumstances. I certainly grant that there are an ocean of idiots selling bullshit. But you're throwing the baby out with the bathwater.

There are better and worse ways to make software. Teams can reflect on how they work and get better over time. Those teams can recognize patterns, and other teams can benefit from learning about those patterns and trying them out in their environment. And that's how things like Extreme Programming came to be: teams experimenting and sharing what they'd learned with other people who wanted to get better. That was exactly what the early Agile movement was.

Piss all over that if you like. But you'll be missing out.

Re:In a nutshell, why do a lot of developers dislike Agile? by lj3 on Saturday August 05, 2017 @06:22PM (#14938256)
I've been on teams that have agile it right. Some have failed and some succeeded. I've been on teams that practiced chaos driven development. Some of those succeeded and some of those failed.

Did you drink any kool-aid on the way in?

Re:In a nutshell, why do a lot of developers dislike Agile? by wpietri on Saturday August 05, 2017 @07:33PM (#14938642)
Your theory is that software is totally random? There's no correlation between what people do and how the project goes?

That is a really weird theory for a programmer to have about anything, let alone what he's chosen to spent 80,000 hours doing.

Re:In a nutshell, why do a lot of developers dislike Agile? by lj3 on Sunday August 06, 2017 @12:56PM (#14942092)
My opinion (not "theory") is that teams are not interchangeable. Companies are not interchangeable. Industries are not interchangeable. What works for one team may not work for another. What works for a 10 man startup is not going to work for a 200,000 person company. What works for a web app company is not going to work for a video game company. But, Agile and Scrum have been shoehorned into every tech company I can see no matter how inappropriate it may be for that particular team, company or industry.

Your question prompted me to consider a thought experiment. Let's assume that management techniques are completely ineffective and the deciding factor in whether a project ships and is successful or not lies entirely with the programmers and designers. Now, let's take it one step further and say that most management techniques actually reduce the likelihood a product ships and is successful. Do you think that would stop management from trying to exert control over something that is completely out of their control? Do you think that would stop management from thinking that their input is actually making things better when in fact their input is making things worse? Managers are ultimately responsible for producing results, but they have no direct control over those results. Most humans, when put in that situation, will try to do something, anything, to make it feel like they have some control over the situation. Even if it makes that situation worse. Finally,what if what I have described above isn't actually a thought exercise, but a fairly good description of what is happening in the real world right now. Would we be able to tell?

Food for thought.

Re:In a nutshell, why do a lot of developers dislike Agile? by wpietri on Sunday August 06, 2017 @01:24PM (#14942265)
Managers in large companies will push anything in a top-down fashion. Before, they pushed waterfall. Now, they are pushing something they call Agile. (They do, I don't.) In 5 years, the consultant-managerial complex will push something else. I agree that is bad. [1]

But the top-down thing is explicitly not what the Agile movement was about. As the early Extreme Programming community would say, "By-the-book Extreme Programming is where we suggest you start, but it's definitely not where you should end up." The notion was always that teams would take time every iteration to look at how they were working and improve it to match local conditions.

That was definitely true even at the beginning; "self-organizing teams" was one of the principles from 2001: http://agilemanifesto.org/principles.html

So the way to think about it isn't in terms of manager interventions. It's in terms of those non-interchangeable teams experimenting and then sharing what they've learned with other teams. Teams will learn things! Some of those things will apply to other teams. A few will apply widely. And that's exactly how the good Agile teams work today. They may start from some recommended set of practices, just like any novice does while learning things. But they are supposed to evolve from there to match local talent and conditions.

[1] I've written more about that here: http://agilefocus.com/2011/02/21/agiles-second-chasm-and-how...

Re:In a nutshell, why do a lot of developers dislike Agile? by Tomis02 on Sunday August 06, 2017 @02:37AM (#14940069)
> That is a really weird theory

Not so weird at all. Codebase and process don't matter to a customer, all they see and judge is the end product. Sometimes even the end product doesn't matter, as the likes of Google can put much more money into ads and marketing than you.

There might be a correlation between what people do and how the project goes if you're NASA or BMW. But for 99% of the software world, nobody cares if you have the most hacky codebase ever as long as it does what it's supposed to do and doesn't have too many bugs.

Re:In a nutshell, why do a lot of developers dislike Agile? by wpietri on Sunday August 06, 2017 @01:25PM (#14942271)
The customers don't care how the programmers work as long as they get good results. But the people on the team should really care. And if they do, they should a) experiment, and b) exchange ideas with other teams.
Re:In a nutshell, why do a lot of developers dislike Agile? by trentnix on Sunday August 06, 2017 @10:56AM (#14941541)
> all they see and judge is the end product

Pretty sure that's a big part of the problem Agile and other approaches to software development try to address.

Re:In a nutshell, why do a lot of developers dislike Agile? by martijn_himself on Saturday August 05, 2017 @03:06PM (#14937319)
I totally agree (well I do think OOP is less of a snake oil than Agile).

There is absolutely nothing wrong with the Agile Manifesto, but this can not be said of the industry that was created on the back of it.

Re:In a nutshell, why do a lot of developers dislike Agile? by carapace on Saturday August 05, 2017 @03:04PM (#14937310)
Well, I don't know if that's fair: most of the places I've worked at that claim to use "Agile" methods were participating in a kind of Cargo Cult. In other words, they thought they were jumping on the popular bandwagon, but if you examine what they did and compare it to what the Agile et. al. stuff was supposed to be, it's not that.
Re:In a nutshell, why do a lot of developers dislike Agile? by Tomis02 on Saturday August 05, 2017 @03:51PM (#14937550)
So what you're saying is that they didn't do real Agile, right?
Re:In a nutshell, why do a lot of developers dislike Agile? by carapace on Monday August 07, 2017 @03:09PM (#14950305)
Well no. If you make a pancake and pour chocolate sauce on it you can call it "cake" but it's not cake.

No true Scotsman would have misunderstood me.

Re:In a nutshell, why do a lot of developers dislike Agile? by mavelikara on Saturday August 05, 2017 @08:27PM (#14938918)
How does one do "real OOP"? Or "real FP"?
Re:In a nutshell, why do a lot of developers dislike Agile? by Tomis02 on Sunday August 06, 2017 @02:29AM (#14940050)
I don't know how one does real OOP, but I know what C++ OOP looks like when used long enough.

1) Architecture. Architecture trumps everything. Even though "favor composition over inheritance" has been repeated for a very long time, some people just didn't get the memo, and you'll encounter mind-boggling inheritance hierarchies (sometimes even template inheritance, to make it fun) with more levels than circles of hell.

2) Class-itis. Everything must be a class, and free-floating functions are seen as coming straight from The call of Cthulhu. Most people are more concerned with the way the class will look and fit in the existing architecture than if the desired functionality is achieved.

3) Code reuse mania. If you write the same line of code in two different places, some people's palms start sweating. More than two identical lines in two different places and you'll have people screaming to move the coded to another place and share it, irrespective of whether it is beneficial or not.

4) God objects. When people just can't take it anymore and simply jam yet another object in the God object. Yes, I know a lot of people from the cult of OOP will tell you this is an anti-pattern, and I agree, but it happens. And when they unravel the God object, an even bigger mess emerges most of the time.

I don't know, I'm probably forgetting a dozen other manifestations of OOP.

You know what "you're not doing real Agile/OOP" sounds like? "You're not doing real communism". And we never will.

Re:In a nutshell, why do a lot of developers dislike Agile? by eesmith on Saturday August 05, 2017 @08:45PM (#14938995)
For "real OOP," use a lot of names from the "Design Patterns" book, reference the SOLID principles, and sketch out the design in UML.
Re:In a nutshell, why do a lot of developers dislike Agile? by BenoitEssiambre on Saturday August 05, 2017 @03:25PM (#14937413)
>you can't change priorities until the iteration is complete

The original agile manifesto was meant to avoid following plans blindly like that. It's only four lines one of which is "Responding to change over following a plan".

Despite what the kanban people think, Agile isn't supposed to be "small waterfall" where the work and priorities are set in advance instead of discovered as you test hypotheses through trying different technological approaches and doing back and forth with the users.

What you propose means that if in a cycle you discover that the plan was sub optimal and not well prioritized (and when you are iterating, you are in the best position to find that out) you march on towards the dead end and only adjust after the "sprint" is over? That is not agile, it may fall under scrum but really it is just small waterfall.

Good agile as it was originally stated is compatible with and even comes from a similar line of reasoning as the Lean approaches. The core of Lean is that the people closest to the technology should be put in a close relationship with the users to be in the best position possible to resolve what I like to call the crux of innovation. Innovation's most difficult and most crucial part which is to figure out what work has the most value to effort ratio, what has the most risk and needs to be studied early to clear up that risk and ultimately what the team should be working on first. At least for any work that is somewhat leading edge or a bit experimental, priorities cannot be properly assessed without experimentation, user feedback and management of uncertainty and risk trough early experimentation.

Scrum tends to ignore this core problem by positing a product owner that has the answers. This is very reminiscent of waterfall where people disconnected from the technology and who aren't experimenting and putting things in front of users, who are ultimately in a bad position to make plans are making those plans anyways. IMO what you are describing and a lot of the ideas in scrum are the very things that original agile was meant to prevent and also goes against Lean approaches.

Here is the agile manifesto:

"Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan"

Re:In a nutshell, why do a lot of developers dislike Agile? by Clubber on Saturday August 05, 2017 @03:15PM (#14937369)
The problem with breaking things down iteratively is the same as trying to paint a mural 1 square inch at a time. The developers / designers don't get a feel for the overall picture what so ever.

Also, instead of having broader estimates in terms of months, you force developers to rush constantly with sprint completion pressure. In case you didn't know, rushing developers is very, very counterproductive. Cost, Time, Scope. Pick 2.

Re:In a nutshell, why do a lot of developers dislike Agile? by scarface74 on Saturday August 05, 2017 @04:18PM (#14937675)
Software development is all about breaking problems down iteratively. If you can't break the problem down to a scale where people understand, how can you ever break a problem down to a scale where a computer can understand?

But I do agree with you about "sprint completion pressure". With Kanban you don't have that and you don't have large day long "sprint planning sessions". You have just enough work in the "Dev ready" column to keep the pipeline going.

Of course not having the sprint planning pressure and not having a deadline to release doesn't work without a continuous delivery pipeline and some way to turn features on when ready.

Re:In a nutshell, why do a lot of developers dislike Agile? by Clubber on Saturday August 05, 2017 @09:48PM (#14939224)
>Software development is all about breaking problems down iteratively.

It is, but it depends on the size of the iteration and who is breaking it down as to whether or not it is useful.

I much prefer, "here is the problem, solve it," to "here is the problem and I'm going to tell you how to solve it, even though I have no idea how software development works."

Of course, the most recent "official scrum" environment I worked in was horrible. They really used it to micro-manage development. We actually created all the stories for a multi-year project so we could give an overall timeline (waterfall) to management, then the business dictated the order of the stories even when they made no sense. It was a constant battle.

Re:In a nutshell, why do a lot of developers dislike Agile? by scarface74 on Sunday August 06, 2017 @09:11AM (#14941150)
It is, but it depends on the size of the iteration and who is breaking it down as to whether or not it is useful. I much prefer, "here is the problem, solve it," to "here is the problem and I'm going to tell you how to solve it, even though I have no idea how software development works.

Yes I've been subjected to that also. But the right way to do it is to have an experienced developer working with the business representative/product owner to do "backlog grooming" before the item ever gets seen by the rest of the team.

Re:In a nutshell, why do a lot of developers dislike Agile? by mpweiher on Saturday August 05, 2017 @03:28PM (#14937427)
> breaking things down iteratively is the same as trying to paint a mural 1 square inch at a time.

What you are describing is the opposite of iterative. When you iterate, you go over the same territory multiple times, with more insight/detail.

Re:In a nutshell, why do a lot of developers dislike Agile? by Clubber on Saturday August 05, 2017 @09:51PM (#14939232)
Where I recently did this, each iteration was a feature and it was supposed to be "code complete, ready for production, never needing to be modified again." We had to constantly fight to refactor existing stories when new stories were introduced that made our original designs less than desirable. It was a mess.
Re:In a nutshell, why do a lot of developers dislike Agile? by jeffdavis on Saturday August 05, 2017 @02:47PM (#14937236)
Breaking tasks down is the hard part. Usually much harder than completing them once broken down properly.
Re:In a nutshell, why do a lot of developers dislike Agile? by t0mbstone on Saturday August 05, 2017 @10:12PM (#14939288)
> "you can't change priorities until the iteration is complete"

And yet the very definition of the word, "Agility" is supposed to mean moving quickly and nimbly, able to easily change direction.

Re:In a nutshell, why do a lot of developers dislike Agile? by trentnix on Sunday August 06, 2017 @08:05AM (#14940962)
Then you shorten iterations if you need to change priorities more often, or you stop the iteration and start a new one. Waterfall created a scenario where requirements couldn't be changed without significant effort. Agile creates a situation where those managing the backlog can change requirements whenever they see fit. And developers, next time an iteration is planned, take the top items from the backlog that fit into their iteration capacity.

The side effect of shorter iterations is that requirements have to be broken down to fit inside the smaller iteration, so there is a price to be paid by those managing the backlog and generating requirements if change needs to happen quickly.

Agile methodologies don't enable change as needed, they create a structured way of handling inevitable change. And when the backlog is adjusted to accommodate that change, the consequences of that change to budget and delivery date are easy for everyone to see.

If you don't have controls in place, then there is no understanding of the cost of change. And without understanding the cost, good cost-value decisions can't be made.

Re:In a nutshell, why do a lot of developers dislike Agile? by Avernar on Sunday August 06, 2017 @03:48PM (#14943085)
Shorten the iteration or abort it midway? Not gonna happen. Management loves having a Monday to Friday iteration. That structure and control is way more important to them than reaponding to change.

Shortening the iterations means you now how to rechop all your tasks and do the estimates again wasting even more time. Also the smaller the task the less people focus on the bigger picture and your software just turns into a mess of puzzle pieces.

Just my experiences from having to go through Agile Hell.

Re:In a nutshell, why do a lot of developers dislike Agile? by trentnix on Sunday August 06, 2017 @10:08PM (#14944830)
Then that confirms my OP - everyone wants to embrace the cosmetic pieces but the actual meat of Agile is ignored.

Every control has to have consequences, or else bad behavior has no cost. Your organization is addicted to what the calendar says, and the software is neglected. The consequences are suboptimal productivity and/or quality. Appearing to work has more value than completing work.

No software process is immune to leadership failures.

Wasting time? Measuring twice and cutting once is done because it saves time. As a shirt I saw recently said, "weeks of programming saves hours of planning".