The core argument: AI made producing software cheap, but understanding it is still expensive. The Manifesto optimizes for the former. This addendum shifts the emphasis toward the latter.
Four updated values, three refined principles, with reasoning for each. Happy to discuss and defend any of it.
This is because your average BA or project manager have long gotten away with blaming programmers for missed deadlines. If you’ve worked both sides of the fence you know the users only vaguely know what they want, the BA role is essentially an incredibly lazy one (I made a wrong ticket but nobody knows it’s wrong until UAT so who gives a fuck about making them right). No matter how your sprint is organised or how many stupid ceremonies you insist on, if you can’t be arsed doing the hard work of specification the whole process is pointless.
I truly hope AI starts doing 100% of the coding so that the tide properly goes out on this farce.
9rx•1h ago
The original Agile Manifesto abolishes VP roles. Are these amendments an effort to try and save your job?
zufallsheld•1h ago
9rx•1h ago
Where you find a VP, Agile isn't applicable. At least not in its entirety. It it is likely that you can still cherry-pick some ideas from it to apply to your non-Agile situation. "Do your manager's job for them" is often considered common wisdom after all.
brackishman•56m ago
brackishman•58m ago
9rx•57m ago
brackishman•51m ago
win311fwg•40m ago
Winston Royce, in his book, invented the waterfall methodology as a hypothetical of what not to do in order to help explain his core thesis. It is not a real thing. Why do you suggest the Agile Manifesto was created to help avoid leaning on a strawman?