Posted by JB | Dec 27, 2007 | Business Analysis |
I love reading Thomas Sowell’s articles on economics and its social and political ramifications. His “Basic Economics” book broke down the basics of supply and demand as well as other economic principles in a way even I could understand! Today, however, his article was a rant on how hard today’s electronic gadgets are to use.
Read MorePosted by JB | Dec 26, 2007 | Requirements |
I recently posted about the need for accuracy and precision in requirements. In that post, I mentioned that natural language requirements are probably the least precise format for expressing requirements. Many BA’s, myself included, write specs composed of natural language requirements and a few flow diagrams for clarification and context. So, given that natural language is not inherently precise, how do we at least make them as precise as possible?
Read MorePosted by JB | Dec 18, 2007 | Requirements |
The business analyst’s job is not complete if the requirements are documented and accurate but lack precision.
Read MorePosted by JB | Nov 11, 2007 | Requirements |
Requirements elicitation is an art. Watching a solid business analyst efficiently identify and document business need by using a careful mix of questions is much like watching the work of any other type of artist.
Read MorePosted by JB | Nov 3, 2007 | Requirements |
I have used user stories – or at least something similar – to help me identify user requirements, but have never used them as the means of documenting requirements. I am somewhat familiar with the concept, though, and have been interested in learning more.
I found a great deal of help in Mike Cohn’s article, Advantages of User Stories for Requirements. In this article, Cohn explains user stories and the advantages of using them over traditional, natural language requirements and use cases.
Read More