Post #2139695

2026-04-02 14:10 UTC

When procuring custom software, agencies commonly make the mistake of contracting for detailed deliverables. They think “our existing system has 16 workflows, so let’s require those the contract for the new system, so that we’ll know we’ll get all that functionality.” This ends badly.

Replies (3)

@waldoj@mastodon.social 2026-04-02 14:10

The core proposition of an Agile contract is this: Instead of defining lots of requirements, those are introduced as user stories throughout the life of the project, based on constant user research, prioritized by a government product owner. When you define requirements up front, they'll be wrong.

Open ##2139696
@paul_ipv6@infosec.exchange 2026-04-02 15:38

@waldoj the govt RFP system seems to just love over specifying. it's how the military got $700 hammers, part of why 2 IRS upgrades and the patent office upgrade are almost legendary. i was at the pentagon when PCs were being used but COTS hadn't been figured out yet. overly specific detailed requirements lead to a boom for folks with antiquated heath PCs when vendors really wanted to sell the latest CPUs instead. good blog on why this is the path to madness.

Open ##2139704
@paul_ipv6@infosec.exchange 2026-04-06 15:43

@waldoj one of the most useful discussions i have with clients who start with an overly detailed build/design is ask: "let's step back. what is the set of key problems you are trying to solve?"

Open ##2139705