5 ms·

so you kinda skipped the code review and refactoring parts, right?

• jamesbritt 17y ago
  I'm guessing you were modded down for implied snark, but it's well worth asking how a small project becomes a big project with no noticing, or noticing but not taking appropriate action. It happens to the best of us, the feature creep, the must-haves, the rush to ship. So, does agile actually fail to address this, or is this something subtle that manages to evade detection despite better practices and intents?
  • run4yourlives 17y ago
    but it's well worth asking how a small project becomes a big project with no noticing, or noticing but not taking appropriate action. Simple, nobody pays you to notice how much of a problem the software that works perfectly has become. They pay you to improve feature x by a very small amount, or to add feature y. So, sure Agile works fine, in the same world that most every other methodology works fine. It's not the methodology that makes good software, it's the people behind it.
• Tamerlin 17y ago
  No, that's the sad part. But when you have 10 people tromping around the same code in a hurry it's hard to keep things clean and consistent even with code reviews... and there's been such a push for new stuff that there hasn't been time for refactoring.
  • aaronblohowiak 17y ago
    "nd there's been such a push for new stuff that there hasn't been time for refactoring." This is a management failure, and you haven't been practicing Agile.
    • Tamerlin 17y ago
      I agree. It's been what I would call lip service to agile, but that's about it. My experience with agile has been that most managers who seek to lead agile teams wind up equating rapidly typing code to rapidly developing software.