Tag Archives: writing requirements

Flashback: A Year Ago This Week on Tyner Blain [2006-11-03]

By Scott Sehlhorst | November 3rd, 2007

A look back at the best from a year ago.

Read the rest of the article …

Posted in Flashback | Tagged , , , , , , , , , | Leave a comment

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

By Scott Sehlhorst | June 16th, 2007

A look back at the best from a year ago.

Read the rest of the article …

Posted in Flashback | Tagged , , , , | Leave a comment

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

By Scott Sehlhorst | June 3rd, 2007

A look back at the best from a year ago.

Read the rest of the article …

Posted in Flashback | Tagged , , , , , , , | Leave a comment

Writing Stylish Requirements

By Scott Sehlhorst | January 5th, 2007

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.

Posted in Business Analysis, Product Management, Requirements, Writing | Tagged , , , , , , , , | 4 Comments

Crossing The Desert With Bad Project Planning

By Scott Sehlhorst | January 4th, 2007

Johanna Rothman recently wrote an article with a poignant introduction: “A project team focuses on an interim milestone, works like the devil to meet that milestone. They meet the milestone, look up, and realize they’re not at the end of the project–they still have to finish the darn thing. They’re living the Crossing the Desert syndrome.” Fixing it isn’t enough – how do we prevent it from happening?

Posted in Agile, Communication, Process Improvement, Project Management, Software development, Testing | Tagged , , , , , , , , , , , , , , | 1 Comment

Software Product Delivery – 20 Rules?

By Scott Sehlhorst | December 7th, 2006

Rishikesh Tembe shared twenty rules for software product delivery last month. His rules are from the perspective of a former software developer. Some we like. Some, not so much.

Posted in CMMI, Process Improvement, Software development | Tagged , , , , , , | 4 Comments

Logical Requirements

By Scott Sehlhorst | December 4th, 2006

We talk about characteristics of good requirements, including completeness, correctness, and ambiguity. But how do we assure that our requirements are complete, correct, and unambiguous? Simple, Captain, with logic.

Posted in Communication, Requirements, Writing | Tagged , , , , , , , , , , , | 1 Comment

Quick Post on Passion

By Scott Sehlhorst | November 10th, 2006

topsyWidgetPreload({ “url”: “http%3A%2F%2Ftynerblain.com%2Fblog%2F2006%2F11%2F10%2Fpassion%2F”, “style”: “big”, “title”: “Quick Post on Passion” }); Why Passion is Important Thanks Kathy for Two Simple Words of Passion… I distinctly remember some eye-rolls when we posted Writing Passionate Requirements as part of the Big Ten Rules to Writing Good Requirements series. When we are excited about our product, and believe [...]

Posted in Requirements | Tagged , , , , | Leave a comment

Writing Correct Requirements

By Scott Sehlhorst | October 30th, 2006

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.

Posted in Business Analysis, Product Management, Requirements, Writing | Tagged , , , , , , , , , | 7 Comments

Monty Python and Software Requirements

By Scott Sehlhorst | October 25th, 2006

The Monty Python troupe helps us remember five (no, three sir!) things about software requirements. And now for something completely different…

Posted in Communication, Requirements, Requirements gathering, Writing | Tagged , , , , , , , , , , , , , | 1 Comment