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 (1)
-
@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.