This website uses cookies to ensure you get the best experience.
Learn more.
A team wants to prevent a requirement from disappearing between elicitation and testing. Which practice is most appropriate?
Published
- Maintain identifiers, ownership, and traceability through the lifecycle
- Treat all passing tests as proof that every need was captured
- Rename requirements on every meeting without history
- Store requirements only in private messages
Comments — 0
Sign in to comment