In the division of the company I work for, requirements bloat and creep are sort of an accepted normal, and very few people even bother to properly challenge requirements. Worse yet, while we have processes in place that are designed to stop requirements creep, they are rarely honored. It's fairly normal for PMs and service owners to accept new requirements without considering the short and long term cost implications, or even the full impacts on existing priorities.
Since the complexity and success of the work done in Semiconductor design and manufacturing are clearly influenced by the requirements gathering and related processes -- I was wondering if some of you could share your experiences on what works for trying to address both requirements bloat (initial pass), and creep (post-requirements review). What are your thoughts on quantity vs quality of requirements, did you try something that failed, etc..
Lastly, if anyone is aware of any good references for the increasing cost of requirements over time, I'd love to read that. (For example - if it costs 1x to write a requirement, it might cost 10x to design, 50x to support, and 100x to change/"fix".. )
Thank you!
P.S. When sharing, please let me know if you're discussing abstract requirements (such as a customer asking for a bid on support where they want to see your innovation), or 'concrete' / functional requirements (such as the container must hold 1 liter of water).
Since the complexity and success of the work done in Semiconductor design and manufacturing are clearly influenced by the requirements gathering and related processes -- I was wondering if some of you could share your experiences on what works for trying to address both requirements bloat (initial pass), and creep (post-requirements review). What are your thoughts on quantity vs quality of requirements, did you try something that failed, etc..
Lastly, if anyone is aware of any good references for the increasing cost of requirements over time, I'd love to read that. (For example - if it costs 1x to write a requirement, it might cost 10x to design, 50x to support, and 100x to change/"fix".. )
Thank you!
P.S. When sharing, please let me know if you're discussing abstract requirements (such as a customer asking for a bid on support where they want to see your innovation), or 'concrete' / functional requirements (such as the container must hold 1 liter of water).