3 ms·

4 years on, neither will save you. That's an issue of trading off short term schedules for long term flexibility. (Not an absolute right or wrong) Agile coul

4 years on, neither will save you. That's an issue of trading off short term schedules for long term flexibility. (Not an absolute right or wrong) Agile could have helped uncover the need earlier, or enabled the project to react to it mid-project. Post production changes don't seem better or worse served by either.

collyw 11y ago
"Agile could have helped uncover the need earlier, or enabled the project to react to it mid-project." The project is an in house database tracking the samples and pretty much everything else for a DNA sequencing centre. The (sequencing) tech changes fairly rapidly and database migrations are frequent. It is constantly mid-project. If I asked three and a half years ago and was promised, "no it won't ever happen", how would "agile" have helped uncover it earlier? Would a load of unit tests written before have made a difference? A stand up meeting every morning? A scrum master? Sorry, that's just bullshit. It came up when it came up, a couple of weeks back. For the time being the workflow in the organisation will have to workaround. Its not a common case, and its really not worth the effort at the moment. For the record I don't do TDD, Scrum type Agile. I do follow a lot of the principles in the agile manifesto, I have to. I do what works for me and the organisation, and blindly following methodology wouldn't.