• @[email protected]
    link
    fedilink
    0
    edit-2
    5 months ago

    I’ll rephrase them, except in good faith:

    1. Talking directly to the people about the work is better than a 95 state JIRA pipeline

    2. Document your finished working work, not every broken POC, because that’s a waste of time

    3. If the contract isn’t actually going to meet the desires of your stakeholders, negotiate one that will

    4. If you realize the plan sucks, make a better plan.

    • @[email protected]
      link
      fedilink
      English
      05 months ago

      Agile development reminds me of the Life of Brian.

      He’s giving sensible and well meaning life advice but all the people want is to follow the gourd.

    • @[email protected]
      link
      fedilink
      0
      edit-2
      5 months ago

      It assumes that: devs can and have the right to talk to the final user, devs can negotiate anything, and devs can make plans. Where I’ve used agile, the whole circus was taken hostage by the managers and there was nothing you could do about it.

      You’ll tell me it’s not real agile, but it’s like real communism, I’ve never seen it.

      • @[email protected]
        link
        fedilink
        05 months ago

        I mean, I’ve never seen a real platypus but I’m not going to use that as a justification for why they can’t exist.

        I don’t know what to tell you. It’s a spectrum. I’ve worked in shops that claimed to be agile but to them, that just meant JIRA and story points. I’ve worked at places where agile meant having daily standups.

        And I’ve worked places where there actually was a genuine attempt, and that was an awesome place to work.