3 ms·
No matter how detailed the requirements you give them are, the requirements are not software and they are not fully formalized. The job of developing software
by rhinoceraptor 7y ago
No matter how detailed the requirements you give them are, the requirements are not software and they are not fully formalized.
The job of developing software is to take requirements and find the inconsistencies at every level of detail. The software is the design, not the requirements.
All software teams miss deadlines, it's a natural consequence of the fact that developing software is an exploratory process.
- daveslash 7y agoThis. I've heard some devs before complain that the requirements aren't specific enough. As a dev myself, my opinion is that if the requirements were 100% clear, thorough, precise, and unambiguous, then you'd essentially have a programming language. If you have developers requesting that specs be 100% perfect, then you have either (a) too junior devs who are lacking a senior mentor or (b) somehow the devs have gotten the idea that any imperfection, misinterpretation, or bug is going to reflect poorly on them, so they're trying to pass the buck - I see this a lot and it's usually a systemic culture problem.