I've been recently thinking about the following question:When are requirements good enough for implementation?I'm trying to create a checklist of some sort that can at least semi-objectively answer this question.Here are some of my thoughts about methods and checks to ensure good requirements:Ambiguity Poll (are the requirements precise enough for thedevelopment team) Non-functional requirements are defined Exclusive use of defined ubiquitous languageConditions of Statisfaction are defined by the customerBusiness Value and Technical Value are clear and communicatedPlease share your thoughts.
When are requirements good enough for implementation
requirements;requirements management