On the contrary. I like agile for when you don’t know exactly what you’re building but you can react quickly to change and try to capture it.
Moving fast and breaking things, agile.
On the other hand. When you know what you want to build but it’s a very large endeavor that takes careful planning and coordination across departments, traditional waterfall method still works best.
You can break that down into an agile-fall process with SAFe and Scrum of Scrums and all that PM mumbo jumbo if you need to. Or just kanban it.
Knowing exactly what you want to build is pretty rare and is pretty much limited to "rewriting existing system" or some pretty narrow set of projects
In general, delaying infrastructure decisions as much as possible in process usually yields better infrastructure because the farther you are the more knowledge you have about the problem.
...that being said I do dislike how agile gets used as excuse for not doing any planning where you really should and have enough information to at least pick direction.
reactordev|1 month ago
Moving fast and breaking things, agile.
On the other hand. When you know what you want to build but it’s a very large endeavor that takes careful planning and coordination across departments, traditional waterfall method still works best.
You can break that down into an agile-fall process with SAFe and Scrum of Scrums and all that PM mumbo jumbo if you need to. Or just kanban it.
In the end it’s just a mode of working.
PunchyHamster|1 month ago
In general, delaying infrastructure decisions as much as possible in process usually yields better infrastructure because the farther you are the more knowledge you have about the problem.
...that being said I do dislike how agile gets used as excuse for not doing any planning where you really should and have enough information to at least pick direction.