A look back at the best from this week in the past.
Flashback: A Year Ago This Week on Tyner Blain [2006-12-1]
A look back at the best from a year ago.
Flashback: A Year Ago This Week on Tyner Blain [2006-10-27]
A look back at the best from a year ago.
Flashback: A Year Ago This Week on Tyner Blain [2006-03-10]
A look back at the best from a year ago.
Flashback: A Year Ago This Week on Tyner Blain [2006-02-17]
A look back at the best from a year ago.
Writing Stylish Requirements
You knew it would happen eventually, the big ten rules of writing requirements has become the big twelve rules. Maybe scope creep isn’t such a bad thing after all. Writing style plays an important role in writing requirements too.
Writing Correct Requirements
We ran a series called Writing Good Requirements – The Big Ten Rules in May 2006. Bloggers are notorious for not being able to count. We had ten rules at the time, and now we’re adding an eleventh. Writing Correct Requirements may have been the unwritten rule, but now we take a look at it.
Monty Python and Software Requirements
The Monty Python troupe helps us remember five (no, three sir!) things about software requirements. And now for something completely different…
Writing Passionate Requirements
One of the ten big rules of writing a good MRD is writing passionate requirements. What in the world is a passionate requirement [they were all wondering]? When you believe in the product, are committed to the work, and aren’t bored, you can write passionately. The goal of a requirement is to create sustained understanding. A dry document can create understanding, but an engaging document will sustain it.