Blogs
Four Mistakes to Avoid in Requirements Meeting
Adriana Beal has wrote an interesting post discussing four mistakes to avoid when leading a requirements meeting. The first mistake is to create unnecessary meetings and/or failing to recognize when one is needed. The second mistake is failing to prioritize the order in which items will be discussed, and whenever possible, the amount of time […]
Read MoreHow Long Do Requirements Take?
In this blog post, Karl E. Wiegers tries to answer the question: How long will it take to “do requirements” on your software project? The answer is naturally: it depends! The post lists conditions that can accelerate requirements development and other factors that lengthen the time needed for effective requirements development. Things are also different […]
Read MoreMinimum Viable Hypothesis
In this blog post, James Shore suggests that the concept Minimum Viable Hypothesis should replace the idea of Minimum Viable Product (MVP). His point is that when you focus on the product you could end up being in love with it.
Read MoreThe Three Agile Innovation Drivers
In this blog post, Roman Pichler presents the three innovation drivers in Agile product management: desirability, viability and feasibility. He introduces a simple model to explore where innovation occurs in products, based on the fact that “product innovation usually occurs in the following three areas: the user experience (UX) and the product features, the business […]
Read MoreCapabilities Based Planning for Requirements
In this blog post, Glen Alleman explains the concept of capabilities based planning to elicit requirements. You use capabilities is to answer the question “Why is this requirement needed?” Capabilities statements are then used to define the units of measure for program progress which is the most meaningful to the customer. Starting with the Capabilities […]
Read MoreOrganize Requirements with a Requirements Mapping Matrix
This blog post by Kim Spilker explains how to using a Requirements Mapping Matrix (RMM) to organize and identify requirements. The RMM is a visual model that can help organize requirements to find missing links, missing information, and unnecessary information you can cut. RMMs are used to map elements of models to one another, for […]
Read More