Skip to content
loading...

re: Defining quality requirements for a project VIEW POST

FULL DISCUSSION
 

These does not sound like "agile" requirements, some of them are almost the opposite.

  • "Correct"/"Unambiguous" -- there is no such thing as correct and clear. Everybody will see things differently. The goal of an agile workflow is to be able to adapt as it's clear something isn't right.
  • "Complete" -- there is no way to specify requirements in advance in full. You need a good communications channel open with your users and stake holders to answer questions as they come up.
  • "Traceable" -- sounds very structured and heavy on auditing.
  • "Modifiable" -- the term sounds fine, but the details imply an unmaintainable N-to-N feature relation table.
code of conduct - report abuse