3 ms·
"So had "agile failed" there? I'd say not." But was it the cause of success? Who knows? In my experience, if you assemble a great team (either by happenstanc
by georgemcbay 11y ago
"So had "agile failed" there? I'd say not."
But was it the cause of success? Who knows?
In my experience, if you assemble a great team (either by happenstance or by planning) pretty much any process you adopt can work great, but (ignoring the downtime for learning the new process) you could swap out that process with virtually any other software process that is common enough to have a name and still get great results. Meanwhile, a mediocre or overly political team will find new and interesting ways to fail with any process.
- mindcrime 11y agoBut was it the cause of success? Who knows? The cause? No, I wouldn't say so, not in and of itself. I don't know that any process can really "cause" success all by itself. But some are better than others at not getting in the way and actually helping rather than hindering. My (admittedly subjective) observation is that our use of Scrum at Lulu was helpful, compared to either "no process" (eg, pure cowboy coding) or some of the more broken processes I've been exposed to in the past. And to me, that's about as much as you can hope for. Because, at the end of the day, it really is more about the team than the methodology. And yes, a truly great team can probably overcome nearly any broken methodology / process and still ship something awesome. The question is how much pain they have to endure to do so.