Flashback: A Year Ago This Week on Tyner Blain [2006-06-02]

mirror

A look back at the best from a year ago.

Writing Valuable Requirements

first rule of writing good requirements

One of the ten big rules of writing a good MRD is writing valuable requirements. How do we determine what requirements are valuable? To whom are they valuable? When a requirement represents a continuum how much is enough? What is too fast, what is too scalable? To whom must the requirement be valuable?

Writing Concise Requirements

rule 2 of writing requirements

One of the ten big rules of writing a good MRD is writing concise requirements. We have to minimize the amount we write to avoid information overload. We also need to make sure we write enough to get the message across. How do we strike the balance?

Writing Design-Free Requirements

rule 3 of writing requirements

One of the ten big rules of writing a good MRD is writing requirements that do not specify design. How do we specify enough detail to be actionable without constraining the engineering team? How do we trust our developers to do the right thing?

Leave a Reply

Your email address will not be published. Required fields are marked *