24

I'm starting on a new project and the person that is wanting this done recommended we have a "living document of requirements"

Fuck no!

Comments
  • 8
    This project isn't for Boeing by any chance?
  • 5
    I think I saw that movie! One of Romero's flops: "Night of the Living Requirements"

    Well, if the scope creeps (or shambles in a zombie sort of way) you'll at least know why, right?
  • 3
    Agile != Anarchy
  • 1
    @gibus Not directly, but it kind of is in a way.
  • 6
    Just say ‘you can have whatever you want but I am not starting it until the living document of requirements is in a fucking coma’.
  • 2
    Yup, we got a few, they're called package.json, Gemfile, and Dockerfile.
  • 6
    It's fine... just have a livingline instead of a deadline... whoops, the line moved two months into the future! Oh look, it moved again!
  • 3
    And a living salary demand: oh look, prices just went up...
    Maybe make that correlate with lines of code being added to that requirements doc...
  • 1
    Combine a living hourly rate with a living line and you've got a realistic workflow designed for people who have no idea what's going on but have a lot of money.
    Yes, I'm talking about the government.
  • 0
    Finally a product owner who is experienced enough to know that requirements will change multiple times over the project's runtime.

    For most non-trivial software changing requirements are an unavoidable fact. Business processes change. Laws change. Markets change. The experience of the people involved change. Design errors are found (in the software - and in the business processes to be modeled).
  • 1
    @Oktokolo Wait, are you pro that guy? This is devRant, we gotta be the ranter.

    But I get your point. living requirements could also be a Jira.

    However, with living requirements, there comes living deadline or living payment.
  • 3
    @dder
    My comment actually was a rant against naive devs not knowing that requirements always change... But i cut that part before submitting.

    And yes: With great change comes the great crunch and deadlines fall like flies on the fields of meager pay...
  • 1
    @Oktokolo I wouldn't exclude the possibility of requirements changing, but updating the requirements document involves updating basically everything about the project. It's not a "live document" at that point, it's just amended, once everyone approved the new plan, new conditions, new price and new deadline.
  • 2
    @helloworld HAHAHA.

    Bring a baseball bat, a wooden stake and a lead pipe to the next project meeting and say that you're planning on making sure the living document dies and _stays_ dead.
  • 0
    I don’t see a problem if they pay for the added time and no deadlines are set, i actually like those project the most!
  • 0
    Can you give the project a nickname?

    Like "Trying to Catch A Fly With Chopsticks"

    or

    "Whack-a-req"

    or

    "I've Got the Football. Stop Moving The Fucking Goalposts"
  • 0
    @elwd Unfortunately with layoffs looming I would like to show I can bring as much value to the company as possible and not have my time dedicated to a project that eventually has no impact.
  • 0
    @elwd Also I'm salaried so no overtime.
Add Comment