All Entries Tagged With: "documentation"

Passing Thoughts on Business Analysis & Requirements

Here are just a few impressions I’ve jotted down over the past few weeks that may never evolve into full blog posts, but that I wanted to share just the same. Please feel free to chime in with your support or challenges to my list, or with your own observances.

Did I Really Write That?

As I was scanning through some of my old documents, I found that I wasn’t that thrilled with a lot of my older work. Ever had that happen to you?

Does Your Paperwork Add Value?

That it’s required doesn’t mean that it adds value.

Looking for Sample Requirement Specifications and Templates?

Quick, simple tips to find sample requirement specs, templates and other sample documents.

Documentation is No Substitute for Interaction

I’ve long been of the opinion that involving as many stakeholders in the project as early as possible is a key to successful business analysis, and, more importantly, to successful projects, and have said as much in a few of my posts on this site.

Jim Highsmith, in the book Agile project management : creating innovative products, thinks that the reason projects tend to have so much documentation and so few results is that:

Functional Specs: Don’t write them??

“Functional specifications documents lead to an illusion of agreement. A bunch of people agreeing on paragraphs of text is not real agreement. Everyone is reading the same thing, but they’re often thinking something different.”