2 comments

  • , 3 months ago

    I know that you can combine and merge these two methodologies in different ways if you realize that the pure Agile or pure Waterfall cannot fulfill your needs. However, I am interested in the critical difference between these methodologies. Who knows?

    0 points
    • Andrew C, 2 months ago

      There’s a term for that — Agilefall. Teams that take “a bit of both” don’t usually fare well because the methods are at odds w each other. Do you want visibility on the future designs or are you ok w quick response?

      If you do vision docs and the work comes out according to plan, but you use “sprints” then congrats - your agilefall. You probably have bugs up the butt, rigid yet somehow still unclear domain ownership, and you attend sooo many meetings.

      I’ve seen it time and time again where companies cherry pick methods like they’re smarter than the ones who wrote the book and end up w a nightmare eng culture.

      It’s better to pick a method when a project or product scope begins and stick w it. Same w other methods like ShapeUp.

      1 point