2 ms·
You appear to be conflating Scrum with Agile, avoiding doing any Scrum-like practices and avoided the clear communication problems within your team ("I strongly
by nl 11y ago
You appear to be conflating Scrum with Agile, avoiding doing any Scrum-like practices and avoided the clear communication problems within your team ("I strongly suspected half of the team didn't know the details of what the other half is working on").
And then you say your Agile experiment didn't work.
the sprint model of Agile easily lends itself to arbitrary deadlines and building for the "demo" of the story/epic of that sprint
"Sprints" isn't Agile, it's Scrum (See for example Kanban).
and build-up of tech-debt (e.g., build a demo for one sprint, spent next 3 sprints fixing bugs for the features of the first sprint).
That is the complete opposite of anything that any kind of agile process would recommend.
To be honest, given that you don't know the difference between Scrum and Agile I think it's fair to say you don't know what you are talking about.
I'm no fan of pure Scrum. I think it's an overly ceremonial approach to building software and the ceremonial aspects of it lead to a cargo-cult like mindset, where people concentrate on the process rather than the reasons why things are done.
But Agile as a general approach works well, and a properly run Scrum process isn't a bad place to start.
- noname123 11y agoThanks nl for your thoughtful feedback! I'll follow up to all your reply threads here. I think you pointed out my negligence in not dealing with "communication problems" on my team, "weak leadership" for not putting my foot down (not prioritizing the backlog of the project and thus making the project delivery date late), avoiding morning standup's completely instead adapting and adjusting a good process on the fly (ensuring that everyone during their updates are succinct); and finally just my plain ignorance in what is the simple distinction between Scrum and Agile is, all points duly noted :) (And being honest, I don't agree with 100% of your criticism; but I do take to heart all of them and will try to work on improve on those specific things you brought up in terms of project management skills in the future!) Although I think we disagree on what is a good project management methodology for software, I think at least we can agree on the fact that having a proper lead to run the project irrespective of the project methodology is really important.
- douchescript 11y agoAgile/scrum defense arguments are like a doomsday sects defenses for why dd didn't happen, everybody didn't believe enough. Now if all would believe...