Agile sucks for software development and I’m tired of pretending it doesn’t
91–93 of 93 posts
Re: Agile sucks for software development and I’m tired of pretending it doesn’t
#92> My current company spends 4 out of 8 hours every day in meetings. I hate to pull a "no true scottsman", but absolutely nothing about that is being agile. The manifesto says nothing about cargo culting various ceremonies, in fact quite the opposite.
Re: Agile sucks for software development and I’m tired of pretending it doesn’t
#93In my experience and practice, “it” works very well when the team and management understand why and how they do, what they do.
Its about working in a way that makes the development process both receptive and responsive to change. Focus shifts from requirement specification to early prototyping and quick release cycle.
To be agile is to be adaptive, not fast. You do that by working closely with customers / End users. You deliver small changes more frequently (sprints). To enable that you setup CI and CD infrastructure.
If most or all of these things sound unfamiliar, you need to question your own understanding of your process and focus on the “why” of it.
There is no set-in-stone way to “do agile”, therefore your criticism sound like someone pissing in the wind and shouting to everyone else about why its hitting you in the face.