Objective praise!

The reason that you are reading this review is probably because you have just become, or are considering becoming, a Business Analyst (IT), and are looking for suitable learning material to assist you down that path. If this is the case, there is something you should know - there is no one, clear definition of the job title `Business Analyst (IT)'. For this reason, you will undoubtedly find varying degrees of positive and negative reviews on just about any book ever written on the subject - this book included. With that in mind, I propose to give you first, my hopes and expectations for buying this book, and then why I found it a positive experience. If you can identify similarities between yours and my expectations and hopes, then I think it's fair to assume that you can expect to benefit from it as I did. (But that isn't to say that if you don't identify those similarities, that you won't find something in it for you - only that I can't say whether or not you will be satisfied).

So, I have been in the IT business for very many years, and I have (at one time or another) worked in all of the disciplines (as defined by RUP) of the project lifecycle, and my job title is currently `Business Analyst (IT)'. I am certified OCUP UML and RUP Solution Designer, which means that I am familiar with both the nuts and bolts of the UML, and of the software development process (as defined by IBM) as a whole. But these experiences and certificates individually do not collectively confer the title Business Analyst (IT) by anyone's standards. Correctly, completely and clearly eliciting and documenting business requirements such that they can be used to guarantee a successful implementation of the contract between Business stakeholders and software developers takes much more than that.

So, what was I looking for in a book? A workflow that would enable me to confidently ask the right questions of the right people at the right time. A logical place to store the captured information. The appropriate level of detail to put into models and documents to enable me to progress efficiently with the dialog between respective stakeholders. The right places to store and cross-reference additional artifacts. The means to cross reference different pieces of each model to ensure consistency and completeness. How, when and where to consider testing aspects. The means to bring it all together. In other words, what I wanted was to `see' and `feel' the complete process in action, not just the parts.

I can safely say that I got what I was looking for. Every project in every company is different, and `Adapting the software development process' is the first thing that is always necessary when starting a new project. There will be tasks to perform that are not covered by this book, and there will be tasks detailed in it that are not necessary in some situations. Nevertheless, this book is a great foundation for the BA (IT) and I have seen little else that tackles the subject as well.

My hat is off with sincere thanks to the author.

Other Reviews

• Objective praise!
• UML "Plus" Reference Guide for the Business Analyst
• Entry Level
• Not sure
• Must read for business analysts