3 ms·
Is it primarily requirement volatility, or primarily ill-defined requirements? (If it's the later, that's some super-irony.) That would explain at least a coup
by pbhjpbhj 7y ago
Is it primarily requirement volatility, or primarily ill-defined requirements? (If it's the later, that's some super-irony.)
That would explain at least a couple of further issues mentioned here. Like rewrites: software doesn't always define it's own outcomes well; the requirements don't change they're just poorly defined.
Requirements changing, and feature creep are subtly different too -- with static ill-defined requirements features could change as the requirements in a particular facet of the software become more clearly mapped out further on in the project.
For example, in the Berlin airport situation (in a comment here), adding a new floor could be due to a realisation that a static requirement for floorspace want going to be obtained, because (say) a static requirement for through-flow hadn't been fully defined and expanding the capacity to meet that requirement then limited the available floorspace. None of the requirements needs to have changed.
Perhaps that's to much of a philosophical distinction.
(Not a [software] architect, or project manager or anything, feel free to tell me I'm talking rubbish.)