4 ms·
Requirements churn
by velikos 11y ago
Requirements churn
- ThePhysicist 11y agoYou mean e.g. requirements that change over time or requirements that get added during the project?
- hanniabu 11y agoBoth would be somehwat equally annoying in that they change the scope of the project.
- bbcbasic 11y agoRequirements are like deadlines. Made up things to keep us controlled.
- bsg75 11y agoRequirements keep management controlled, exposing them to the concept that change has cost (manager here).
- bbcbasic 11y agoSetting the scope of the work is what is keeping management controlled. E.g. "In Version 1.0, it will talk to these 3 services only..." But that is different from 'requirements' which I take it as 'things that are required' and have a non-negotiable connotation about them. E.g. "It must work with all of our services" Since it is not know which requirements are actually required and which are BS, it may be better to call requirements 'requested functionality' and what is planned to be delivered 'project scope' and drop the requirements word altogether.
- tonyedgecombe 11y agoWhat bothers me more are people who think requirements won't change as development proceeds.