Welcome to the December 10, 2007 edition of the Carnival of Business Analysts.
Hello everyone and welcome to edition 5 of the Carnival of Business Analysts. Regular readers will know that since edition #3 each new edition of the Carnival of Business Analysts has been following the knowledge areas described in the BABOK. I hope you find some useful info in here, and if you know of any other good articles plug them into the comments below for others to check out.
Firstly we have Chris Baker who provides a very on-topic article called Requirements Analysis at his blog Usability Notes. In it he describes the challenge of communicating requirements across the business technical divide, offers up an acronym for checking off your requirements and the challenge of dealing with competing requirements. A good opener for this topic.
Secondly, Jeramie Mercker delivers A Requirements Analysis Primer at Tech Links. In particular read his rules of thumb for some very practical guidelines on how to tackle requirements analysis. Lalit also offers a list of Types of requirements at Rapidshare Ebooks
Next up is Gareth Thomas Hill’s blog with his post on Quality Software Requirements with a checklist of what goes into good requirements and what identifies bad requirements. You can also read about an ISO9001:2000 approach to requirements assessment at (ISO) Quality Manual Chat.
Ahamad complements the QA perspective with a testing one in Requirements testing at his Software Testing blog. Remember the V-model and Test driven development? The same principles apply to requirements; they should all be testable and you should basically have your test cases written before you get your requirements signed off.
Zuzar provides a list of four major problems with software requirements in ‘Most common errors in requirements analysis’ at the Blue Mango Blogs. Don’t make these mistakes when putting yours together.
This discussion on Requirements Analysis has to include the topic of business rules and business process management. Theresa whole big discussion just on how these two topics interact with requirements. Have a read of Requirements vs Process and Rules at Roeland Loggen’s Process transformation blog.
The Role of Architecture in Business Analysis is discussed at Ashok’s blog space by Michael Rosen. Architecture – both business and technical is an increasingly important part of business design and management. How does it fit in with project requirements analysis? Go take a look.
The Art of Commerce blog has a couple of good posts on requirements. The one most pertinent to this months theme is “Should you trust your analyst?” This post sets up your stakeholders to challenge what you give them.
On the topic of specific Analysis Techniques Dale Wolf posted an article on Conjoint analysis at his Perfect Customer Experience blog. Also Jim presents Common Cause Variation at The Kaizen Business blog. This topic is one of the six sigma tools and is a process analysis tool.
Warren Wong presents some financial perspective in What Is The P/E Ratio And What The Price Earnings Ratio Means at Personal Development for INTJs, with "A description of what the P/E ratio is and what the price earnings ratio actually means."
Interestingly we also have an article from a lawyers blog; Noric Dilanchian presents How to make contracts more certain and less costly posted at Lightbulb, saying, "It's time to stop believing the myth that lawyers can provide legal protection with words alone. In addition to words, protection in contacts requires knowledge and know-how regarding business process, policies, training, standards, and codes of conduct. This article discusses why this is so in Australia, the United States and other countries with contract law derived from the law of England." My view on this article is that it provides an interesting alternative view to many issues BAs face with projects.
Off topic, but close enough Sagar gives us The eCommerce Customer Service Checklist: 50 Things Every Business Should Be Doing posted at Virtual Hosting and James D. Brausch presents Business Systems Also Improve Sales And Customer Experience posted at jamesbrausch.com.
There you have it; the 5th edition of the Carnival of Business Analysts. This particular Carnival series is a special way of highlighting the excellent contribution blogs can make to the body of knowledge for analysts. If you have a post you would like to contribute please let me know either via the comments, by emailing me, or by the carnival submission form.
Next month’s topic; Requirements Communication, and submit your posts by January 27th!
Read other Carnivals of Business Analysts here
(And past posts and future hosts can be found on our blog carnival index page.)