Comment by Tareq Hassan on "What are better project management paradigm alternatives to Agile?"

Sometimes Agile can hold up you, or the company's progress if it was over-used. let's take this example, If I have a startup, a small team, and a clear plan for my startup I would definitely go for WaterFall Technique because you sometimes you have to _"Move fast, Break Things", _Once you are there, and all of your developers got the idea and aim for the startup they are working for, hold them down, take a deep analysis of what's been done, and how can we learn from the mistakes done so far.

Move then to (Agile) because once the project has gone big, you can't control all of the areas of your startup, and all of the written code and business logic with Waterfall.

Gg you know the author of "waterfall" actually wrote in the paper that you shouldn't use that technique ? :D

And everything that has to go fast should be agile :D that's the definition of the word agile that you can easily react :D .... or lean if we go for the MVP :D.

:) didn't know that. but waterfall can be useful especially if you want to kick start an application in the fastest way. IMHO agile should be only used once you have an application that is up and running, like when you have a stable app and you need to organize, add new features, revamps... .

hmm, maybe you're talking about a different waterfall model. But as I learned it you spend a lot of time calculating the time and you don't have a lot of flexibility to react because everything has to be done at a certain time and only a specific amount of resources available.

So to this is a classic big business "lets plan our fiscal-year" approach. Maybe you did not really have to use waterfall ? So if you were kinda free-styling you were actually doing agile.

At least that's what I learned in project management you have to specify everything and the other pm has to specify everything. Wasting hours writing about interfaces and problems you cannot know at the time, binding them to a timeline that only works if you tweak and lie about it.

For me "using what I need to get the job done" is the fastest way to do things :) and I pick what I need from scrum, kanban, extreme-programming, pair programming, mob-programming, outlining, UML, ERM, "the hacker way" or whatever paradigms are floating around :)

So at least to me Waterfall done right only works if your guesses are lucky. If you wanna get things done quick and easy the agile manifesto (not to be confused with the different implementations of it) is a better starting point :D

But if you like waterfall, I won't argue against it. I am a pragmatist so whatever works will be used as long as it doesn't slow me down without a worthy trade off -> (for example: branching strategies -> more security, more overhead -> worthy trade off to me)

Tareq Hassan oh and you need to tag me so I get a notification about your answer:)

J , yes indeed. It really varies from team to another,and from company to another, it is not about choosing what is theoretically the best, it is what is the best for your team to coupe and to work with the minimal effort, and yes as you said, sometimes a mixture between them can achieve that.

It needs a good amount of effort, time and adjustments to know what is the best for you, or your team.

nice talk j , Appreciated!

Search Hashnode