A team wants to prevent a requirement from disappearing between elicitation and testing. Which practice is most appropriate?

Published
  1. Maintain identifiers, ownership, and traceability through the lifecycle
  2. Treat all passing tests as proof that every need was captured
  3. Rename requirements on every meeting without history
  4. Store requirements only in private messages

Comments — 0