It doesn't help that users might be split across instances. I posted recently over on this instance: [email protected]
I didn't want to repeat my post and annoy people who might see it two or three times.
yesterdayshero
joined 2 years ago
Agile isn't meant to replace anything. You need to use the right method for your context. No one said the purpose of agile is to replace all other methods.
Agile doesn't have to be implemented perfectly to work. You seem to be holding agile to some higher standard than anything else.
You have to get over the communism comparisons. They aren't relevant.
Just because you haven't worked in an agile environment you enjoyed, that doesn't mean it can't work. It can and does work. Just like any other method. And it can and does fail. Just like any other method.
OP didn't work in agile. They were told that they were working in agile but it was just an excuse for the business to not have requirements and continually change their mind. Every one of the issues they raised could have happened in any other methodology. It's poor management.
So if all approaches are poor, then anarchy? I think you need to move on from the communism comparison, and the idea that unless something is perfect it's not worth doing.
Believe it or not, there are people working in successful agile teams right now. Just because you haven't, that doesn't mean it isn't tenable.
As long as it's not LEGOs I can get behind that.
I disagree. I'm currently working in agile and it's the best team I've worked in/with. It can easily go wrong, but it can also work really effectively. Implementing agile in an "ok" way, is still better than waterfall in most instances. Of course it depends on the business context.
Take all of OPs complaints for example. Sure, they can be an issue if agile is implemented poorly (or not at all in OPs case), but all of them are inherent issues with waterfall. Developing something only to find out days before launch the business has something else in mind. There would be much less chance of that happening in an agile environment over something like waterfall.
There's a big problem with people saying they work in agile, when they're really not. Like in OPs instance. And that leads to the negative sentiment about agile never working. I get it, I've been there and had to work in agile teams that weren't really agile. That doesn't mean it can never work.
Good points. And from what I remember of the books, 80% of them was people talking about things that have or will happen, not actually seeing it. I'm not sure a direct dramatasiation of the novel's would have made great tv.
Maybe enjoy isn't the right word come to think of it. But I guess DoH was rewarding and memorable haha.
Sword Saint was great too. It really felt like it escalated with each phase to a crescendo.
Owl father was a real challenge for me, so maybe I didn't get to enjoy it. But come to think of it, without that fight and the plenty of practice it gave me, I would've struggled a lot longer on some of the following bosses. I think it was Isshin Ashina and Owl where I had to learn move sets and think about my approach.
What do I play next though is the real question. What did you follow it up with?
How do I do that?