Quick Links: Articles MA Blog Community Blog Templates Books BA Humor Events Jobs Interview Questions RSS Feeds
Not all requirements are created equal, so to make smart choices about which product requirements you should explore and implement—or whether you should delve into them at all—you need to prioritize them. Many teams do not prioritize properly and waste time specifying requirements that are never delivered. Why spend time and energy on requirements you won't use? In this article, Ellen Gottesdiener answers the question by detailing how and when requirements should be dealt with.
Author: Ellen Gottesdiener
Advertising Opportunities | Contact Us