For some projects, agile is simply not good but they still force it. Why force something that doesn't work?
16 replies (most recent on top)
Cause it 'sounds' good
To be fair to the poster. Fiserv's implementation of agile in their area likely is about increasing micromanagement. In other words agile is being implemented incorrectly.
Manifesto. Sounds like control
"Agile a fancy word and process to Micromanage people. I have no issues with Agile for developers applying it to everything else.. now that is a different story."
So, the biggest issue with Agile? Nobody knows what the !@#$ it is. Take this post, for instance. "A process to micromanage people"? Seriously? That's the opposite of what it is. Here is the Agile manifesto to help clear up any confusion.
http://agilemanifesto.org/
I have seen Agile work well both in software and outside of software, and I have also seen it work badly or be used in the wrong ways. It can go either way.
Agile a fancy word and process to Micromanage people. I have no issues with Agile for developers applying it to everything else.. now that is a different story.
I love Agile. I get to set in hours of meetings each week describing how it works. It’s my time to catch up on current events and my stocks.
Agile works very well, and there's no going back. Only waiting out the boomers to finally get out of its way.
Rework, bug fixes and requirements changes are going to happen no matter what. Why? Because human beings are imperfect. The question is, do you want 1) to do manageable amounts of rework two weeks at a time, or 2) wait riiiight until acceptance testing and delay a project with 6-12 months of panic and rework to meet requirements?
Option 1 generally results in better products and fewer disasters, but more daily churn. Option 2 results in a false sense of being 'on track' followed by fire drills and obliterated careers when oopsies are discovered.
I'll Option 1 (Agile) any day. Thx.
If it takes millions of dollars and years to learn, it’s probably not that great of sdlc. Great for consultants though
Agile is an old-aged confidence job.
That is why it has to be forced.
Agile,
A religion by another name.
Just like everything else OFD does, this too will fall short. They will say do this or else but then move on to the next latest and greatest "thing" someone read about in a book. Has OFD followed through with anything they have started?
With Agile smaller teams are better. Then they won't look like mo--ns after they lay everyone off.
Because they have a goal to get everyone onto Agile so they do it. They dont wanna lose their bonuses!
Start pushing back and see what happens! And then, find an employer who's fine with you asking logical questions without consequence.