I recently stumbled upon this video, got a kick out of it and thoughts I’d share. It is basically a video parody for the process of designing the stop sign if the project were kicked off in 2008. There have definitely been times in my career as a BA where I’ve felt like the poor chap trying to design to the customers’ specs.

Oh.. and for geeks like me who saw this and then wondered when we really did get the stop sign, here’s an interesting link.

My company has been looking at requirements management solutions, which has provided me with the unique opportunity to play the “user” role for a change, and to do a little research into the attributes that make requirements management successful.

Anyway, what I’d like to do with this post is to share a few items I’ve found on the Web as well as some of my own thoughts on what might be of use to others who might be looking for a requirements management solution.

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

A few thoughts on identifying use case actors and a job-aid that may help simplify the effort.

“[T]he determination is made by evaluating project environments and organizational stakeholders.”

A recent CIO.com article has piqued the interest of many business analysts.

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: