I can’t remember a time when software development methodology was not a hot, contentious topic of discussion.
“We need to be Agile, because that will make us go faster”
“Scrum will save us from everything we are doing wrong”
“Waterfall is the devil’s child”
“Design Patterns are the only way to go”
“Design Patterns don’t work for me”
The problem with every architecture style and delivery methodology (new and old) is the same as it was yesterday, last year, five years ago and most likely in the 80s.
We refuse to look at what the problem is that we are trying to solve and instead are content with slapping a band-aid on it and calling it “fixed, because we now have #INSERT FAVOURITE METHODOLOGY HERE#”.
If you are not will to identify what is wrong with your delivery of software in the first place, you will never be able to apply the correct methodology that applies to you.
And when I say “identify what is wrong with your delivery of software”, saying “we’re always late” is a cop-out to the true problem.
My company BetaRover Inc, specializes in working with organizations getting over these humps and breaking through the Invisible Barriers that are holding them back.
Check us out, we’re always happy to chat.