• @makeshiftreaper@lemmy.world
    link
    fedilink
    English
    3312 days ago

    More accurately the waterfall mission ends up on Phobos only to have to scramble to figure out how to land on Titan because the customer can’t tell the difference between moons

  • @SpaceCowboy@lemmy.ca
    link
    fedilink
    1211 days ago

    Waterfall is more like: You want to go to Mars. You start to build the rocket. Managers that don’t know anything about building a rocket starts having meetings to tell the engineers who do know how to build a rocket what they should be doing. Management decides to launch the rocket based on a timeline that’s not based in reality. Management tries to launch the rocket based on the timeline instead of when it’s actually finished. Rocket explodes. Management blames the engineers.

    The various methodologies don’t actually change what the engineers need to do. But some of them can be effective at requiring more effort from management to interfere in the project. Bad managers are lazy so they’re not going to write a card, so they can be somewhat effective in neutralizing micromanagement. I say somewhat, because bad management will eventually find a way to screw things up.

  • @RizzoTheSmall@lemm.ee
    link
    fedilink
    English
    3612 days ago

    What’s not covered is the 25 years of R&D in advance of waterfall project starting, or that it’s delivered 200% over time and cost due to those requirements being insufficient and based on assumptions that were never or are no longer true.

  • @9point6@lemmy.world
    link
    fedilink
    11212 days ago

    A software engineer was not involved in this if waterfall is painted positively.

    I think the last time I heard an engineer unironically advocating for a waterfall IRL was about a decade ago and they were the one of the crab-in-a-bucket, I-refuse-to-learn-anything-new types—with that being the very obvious motivation for their push-back.

  • @aghastghast@programming.dev
    link
    fedilink
    English
    3311 days ago

    Test-driven development: You spend all your time building a gizmo to tell you if you’re on Mars or not. A week before the deadline you start frantically building a rocket.

    • Camelbeard
      link
      fedilink
      6712 days ago

      I’m getting pretty old so I have experienced multiple waterfall projects. The comic should be

      You want to go to mars You spend 3 months designing a rocket You spend 6 months building a rocket You spend a month testing the rocket and notice there is a critical desing flaw.

      You start over again with a new design and work on it for 2 months You spend another 6 months building it You spend 2 months testing

      Rocket works fine now, but multiple other companies already have been to Mars, so no need to even go anymore.

    • @tyler@programming.dev
      link
      fedilink
      1312 days ago

      pretty sure they’re saying waterfall for building a rocket because that’s literally how NASA builds a rocket, including the software. It’s terrible for building anything other than a rocket though, because the stakes aren’t high for most other projects, at least not in the way that a critical mistake will be incredibly bad.

    • @mmddmm@lemm.ee
      link
      fedilink
      8
      edit-2
      12 days ago

      Scrum is not about any of the things that Scrum proponents claim it’s about.

      Specifically, it’s not about agility, it’s not about velocity, it’s not about quality, it’s not about including the “customer”, and it’s only about a kind of transparency that has absolutely no impact on the final product.

      But yeah, it’s about some kind of transparency.

      • @Atomic@sh.itjust.works
        link
        fedilink
        011 days ago

        Specifically, you would have to put in effort to be more wrong.

        Go read the scrum manifest.

        In reality, companies always adapt for what they think suits them. Very rarely do you actually use scrum completely as intended, that’s fine. But you don’t blame the cow when the cook burned your steak. You blame the cook.

        • @mmddmm@lemm.ee
          link
          fedilink
          111 days ago

          Oh, Scrum has a manifesto now? Where is it?

          Or you meant the Agile manifesto, that Scrum breaks half the items and does nothing about the other half?

          • @Atomic@sh.itjust.works
            link
            fedilink
            211 days ago

            Perhaps poorly translated, they call it the scrum guide in English

            https://scrumguides.org/scrum-guide.html

            I don’t know what parts you are talking about since you’re not specific.

            Furthermore. Kanban is just a method of keeping track of who does what and what the progress of that is. You can use kanban in waterfall. You can use kanban in scrum. No one is just using kanban and nothing else. As your post seems to think.

    • @boonhet@lemm.ee
      link
      fedilink
      912 days ago

      Must be OP trying to hide it, Toggl displayed it proudly. The author used to work for Toggl marketing and ask can be seen from this post, did an excellent job. He still has a webcomic, it’s just not marketing for Toggl anymore. Here it is

      As for bias - it’s a time tracking tool, but I don’t think they actually shill for waterfall, I think it’s just poking fun at the agile methodologies.