Post #2139696
2026-04-02 14:10 UTC
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.
Replies (1)
-
@waldoj@mastodon.social 2026-04-02 14:11
In the case of those 16 workflows, it would be a real victory if user research found that, actually, only 9 workflows were needed. That's faster to build and cheaper to maintain. But only if the contract allows building just nine! Did it specify 16? Well, then you're getting 16 now.