• henfredemars@infosec.pub
    link
    fedilink
    English
    arrow-up
    52
    ·
    1 year ago

    I’ve had this conversation:

    We need to increase our velocity! Has the customer told us yet what they would like us to build?

    • NewAgeOldPerson@reddthat.com
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      Unfortunately I can’t have that chat ever. I’m the one (in most of my career, not now) responsible for telling my folks what the customer wants, and not in a sales way.

  • Gork@lemmy.ml
    link
    fedilink
    English
    arrow-up
    23
    ·
    1 year ago

    “Boss, most of the bricks we have are broken in pieces. We can’t build the wall per specifications.”

    “We have a deadline, get it done however possible by the end of the day today.”

  • scytale@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    ·
    1 year ago

    This applies to lift-and-shift migrations too. “We need to migrate this now, let’s fix it as a next phase”, then it never gets fixed; instead of taking the opportunity to fix stuff as you build on a clean slate.

    • psud@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      1 year ago

      I loved agile as an analyst, we used to use waterfall and you’d hear about incorrect designs months later, or not at all, where in agile you can work out the details with the programmers and get both nearer the business requirements, and better designs

      Also I absolutely love the job of scrum master which had no equivalent in waterfall

      • Lysergid@lemmy.ml
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        I love waterfall as an developer, I’m using agile now and we have incomplete, conflicting designs every sprint, or spills which affect our metrics, where in waterfall you can workout all the details and have full vision of product and better design with less reworks.

        Not to mock you. My point is that methodology is not import when team consists from responsible professionals

        • SpaceCowboy@lemmy.ca
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          I think a lot of it dependent on management. If you have a good product manager, software architect (or whatever) who can have things solidly designed before sending it to development, agile works great. But if the people writing the cards suck at their job, well then the project isn’t going to go well.

          But then bad management is going to suck no matter what methodology is used.

          • psud@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            You’re right on. We have some good expertise left over from our previous methodology which was both waterfall and siloed so bad feature documents don’t cause too much problem, but once our expertise retires (and we’re not makeing new experts as the silos were removed) the features will need to great to get decent products

            And bad management is the biggest thing to make a job miserable

        • psud@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          I don’t take it as mocking or anything, I know that some devs in my team preferred waterfall. I’m just saying there are aspects of agile I really enjoy

          Waterfall makes higher quality software in many circumstances. It’s optimised for quality.

          Agile is optimised for speed explicitly at the expense of quality. Whatever methodology you can only pick two between development speed, cost, and quality

        • gravitas_deficiency@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          1 year ago

          There are some instances in which waterfall is not only entirely appropriate, but also the best possible choice in terms of work organization.

          There are some instances in which agile is the best fit. Likewise kanban.

          Different domains have different optimal workflows.

  • notannpc@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    ·
    1 year ago

    My conversation with the moronic MBAs that lead my org today. Who cares about doing impactful work when we can just do useless busy work that makes the nontechnical morons happy.

  • I Cast Fist@programming.dev
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    “We’re just using old, time tested frameworks. They worked fine in the past, they’ll still work today for sure!”

  • Bilb!@lem.monster
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    just keep coding, your employer will outsource you the very moment i seems convenient

    • b14700@lemm.ee
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 year ago

      should work fine if there is no load on it , this seems deliberate for the look

    • Fixbeat@lemmy.ml
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 year ago

      I’m not a mason, but I guess it would work, if it is vertically straight. It’s ugly though. The customer would complain…unless you hide it somehow.