Email or username:

Password:

Forgot your password?
Greg Wilson

As far as I can tell, _every_ software development process works if the people using it are well rested, knowledgeable, respect each other, agree on goals and methods, and have achievable deadlines. Just sayin'…

8 comments
Simon Detheridge :snorlax:

@gvwilson these are definitely prerequisites, yes. I do think that an agile process, suited to the needs of the team and well-rounded through retrospectives that actually engender change, is a very valuable thing for keeping things cohesive.

That should be an outcome of the kind of system you are describing, but it helps to have leadership invested in continual improvement so that the "process" can be as optimal as possible.

Eljorgeabides

@gvwilson
You can't know that because that state of work doesn't exist!

😂😂😂

John Turner

@gvwilson I agree. But I also think that the goal of a software development process is maximize those things, not consider them as inputs or complications to the process of shipping software.

PirateRo

@gvwilson and they are paid startlingly well, the project interests them, is or isn’t a moral application of technology that inspires the crazy control need in each of them, includes the cool foods like hostess orange cupcakes, all kinds of toys, education payments and an excellent free medical and a startlingly g real bonus.

Servelan

@piratero @gvwilson Exactly. Project I was on went through two tons of M&Ms (it was a 'dot 0' release and kinda stressful) and the money and benefits were pretty darn good...

DELETED

@gvwilson

This is so relevant in my home right now.

Fred Moyer

@gvwilson don’t awake the scrum lords with that talk 🤣

Security Writer :verified: :donor:

@gvwilson I’ve been preaching this for years.

The difference between one company getting bad results with, say, waterfall, and one with Agile getting good results is management.

I’ve seen just about every dev process and framework work just fine if it’s managed well.

As an aside, I also think the likes of Agile or Scrum are a result of bad management and employment practices. Made popular by some of the most prevalent software coming out of the US.

Agile, Scrum et al make the best of a bad situation when there’s a lot of corporate micromanagement, changes of direction, VC whims that need to be allayed. They’re very well suited to collaborative projects and startup culture. They’re a well thought out, and useful in their own right, but are themselves the result of bad management.

Then you see some MBA try to make them the entire company’s operating process, and it becomes a crutch for people without a plan.

@gvwilson I’ve been preaching this for years.

The difference between one company getting bad results with, say, waterfall, and one with Agile getting good results is management.

I’ve seen just about every dev process and framework work just fine if it’s managed well.

As an aside, I also think the likes of Agile or Scrum are a result of bad management and employment practices. Made popular by some of the most prevalent software coming out of the US.

Go Up