Premium
7.1.3 Using a Requirements Management Tool in Technical Requirements Negotiations
Author(s) -
Dale R.S.
Publication year - 2004
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2004.tb00582.x
Subject(s) - negotiation , hindsight bias , variety (cybernetics) , requirements management , process (computing) , requirements analysis , contract management , computer science , liberian dollar , process management , business , engineering management , engineering , political science , law , marketing , psychology , artificial intelligence , cognitive psychology , software , programming language , operating system , finance
Abstract This paper records the experiences of tracking the technical requirements for a missile system during the contract negotiation phase. Initially WORD documents were used to record the requirements but, because of their complexity and the frequency of change, these were abandoned in favour of using a Requirements Management tool. The paper tells the story as it was and then comments on this using the wonders of hindsight. Whilst the process worked well on this particular contract, it is recognised that contract negotiations can take a wide variety of forms from formal multi‐billion dollar contracts to strawman discussions for in‐house projects. I believe, however, that the underlying problems and approach to combatting them are sufficiently general to be applied universally. This paper highlights 10 tips as encouragement to anyone contemplating facing such negotiations.