Year: 2013
Agile Requirements: a Self-Building Documentation
How do agile requirements work? Where does documentation fit in? For many of us, the transition from the security of upfront analysis and detailed specification documents to ‘doing Agile’ and embracing the process of discovery is a terrifying prospect. Agile theories don’t readily address the concern ‘how will we know where we’re going if we […]
Read More
Find Missing Requirements
This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.
Read More
Creating Customer Value with Quality Requirements
How do you know what to build of your customer wants a “secure solution with a good amount of flexibility and user-friendliness”? You don’t! Force the customer to be more specific!
Read More
Split Testing for Product Discovery
This video explores split testing as a way to not only increase revenue and conversion through simple, surface-level changes, but also to dig deeper in order to help guide a product’s roadmap by discovering which features customers really want and how much they’re willing to pay.
Read More
Perfect Requirements
In this blog post, James Christie starts from the fact that perfect requirements don’t exist to discuss the idea that the quality of requirements is directly influenced by the time and money you invest in crafting them.
Read More
Why Should You Write Requirements
In this blog post, By Scott Sehlhorst starts with a simple fact: if there is a lot of discussions on how to write requirements, there is not so much material on why to write requirements. His advice is that you should start by thinking about why you write requirements before you decide how to write […]
Read More