Fork me on GitHub
Risk First Logo

Home of Risk-First Software Development



Start Here


Home
Contributing
Quick Summary
A Simple Scenario
The Risk Landscape

Discuss


Please star this project in GitHub to be invited to join the Risk First Organisation.

Blog


Consuming Hacker News 14 May 2019
Twitter Cards 22 March 2019
Next - Scrum? 7 March 2019
Available On Amazon 25 February 2019
New Proof 10 February 2019

Publications



Click Here For Details


Under Construction

What Is It

Requirements Capture is not a single technique, but a broad category of techniques such as:

How It Works

Whatever exact methodology you are using, the aim is to meet stakeholders and try to capture their Internal Models in written form. This has a few effects:

Variations

Structured Requirements

Use Cases

See also: Terms Of Reference

Feedback Loops / Risks Mitigated

Requirements Capture is itself a process of Meeting Reality, and in a limited way: rather than speculatively building a piece of software and trying it out on the world, Requirements Capture allows us, cheaply, to go and see what the world thinks it wants, which is much cheaper, but perhaps less accurate.

Feature-Risk

Asking people what they want is often a way to reduce Feature Risk by stopping you building the wrong thing.

[

The feedback loop for any design is review. You can also follow review with Sign Off.

Attendant Risks

Steve Jobs - people don’t know what they want until they see it.

Elizer Yodowski - what exactly is a MVP.

Found this interesting? Please add your star on GitHub to be invited to join the Risk-First GitHub group.