5 ms·
Coming from big corp, I definitely miss my days at smaller shops that did Agile. I feel like so much of this has little to do with the development methodology a
by gleenn 4y ago
Coming from big corp, I definitely miss my days at smaller shops that did Agile. I feel like so much of this has little to do with the development methodology and more to do with the people though. Smart people can make any methodology. Even at big corp, more waterfall-y processes are not terrible because I think my coworkers make it alright. The author seems to be unhappy about empowered developers being problematic, which I've seen, but a few of those people probably would have been as big a pain as in waterfall land. In general, I think Agile is good because it emphasizes smaller iterations and adapting processes, amongst many other connotations. I think the core of those ideas are miles ahead of whatever was produced decades ago by more rigorous engineering processes. Building a bridge is not the same as building a big piece of software. Developing software is hard in general. I think we're just slowly iterating as an industry towards better practices and we aren't there-there yet. As always, YMMV
- swader999 4y agoYep. Problem developers can create larger problems with longer feedback cycles.
- polotics 4y agoThe main difference between Some-planning-up-front and big-A Agile IMHO is that responsibility for failure of delivering on the plan can be shunted away from the leadership to a slow-burn failure of delivering on quality after many iterations. A product will have been built, but it is too costly, low quality, expensive to maintain. Lack of qualified software design can be papered over for several years with the big A...