The Business Analyst's Handbook 1st Edition

Some of the reviews written on this site are rather odd. It seems some people must have expected this book to be written for entertainment. It isn't a comic book or a love story. It isn't a book you are going to read in a week and miraculously become a Business Analyst.I found the writing to be very clear, explanations well thought out and concise, and the overall composition to be structured in a professional manner. The structure follows the BA's modus operandi making it extremely easy to know which section of the book to turn to for a quick reference.For CBAPs and practitioners you would understand that it follows the BABOK structure. To the layman, consider that part of the title identifies it as a "Handbook".This is a paperback but, physically, it is a big book weighing several pounds. The text is a medium font. I wear reading glasses normally, but they are not necessary with this text. The pages are a non-glossy off white making it easy to read in natural or artificial lighting. I can read this book for several hours with only a minimal amount of eye strain.The Business Analyst's Handbook is a reference. No, it is an Excellent reference. It is detailed with numerous charts, models, and definitions. I am enjoying reading it. But, then, one of my degrees is in Economics and I thouroughly enjoyed reading all of my textbooks in that discipline.Every BA, PMP, and aspiring practioner should have a copy of The Business Analyst's Handbook on their shelf for a quick refresher.

This book is a great reference guide and handy pocket tool for Business Analyst and stakeholders that want to learn more about business analysis as it relates to system design and software development. From a prospective of an IT Consultant with over twenty year's experience, this book should be required issuance to Business Analyst on day one! As stated by the author this book is not intended to be read from end to end, but used as a reference guide for Business Analyst career development. A career is the pursuit of a lifelong ambition or the general course of progression towards lifelong goals. A job is an activity through which an individual can earn money. It is a regular activity in exchange of payment. With that said a career oriented Business Analyst will have material on a variety of subjects and organize their time to sharpen their saw!

In my experience most technical books are either overly dry and are useful as a reference tool or completely theoretical leaving it up to the reader to determine application modes. Howard Podeswa does a great job of blending the two. He also does this in the context of one of the most important and least discussed role - the Business Analyst.Over the years I have had the privilege to be part of many software teams. We have had great successes and a few failures. One thing that is a constant is the impact of the Business Analyst role on project success. The The Business Analyst's Handbook provides a complete tailorable approach to facilitating, organizing and disseminating business information that is sure to have a positive impact on any team.This is a book that should be near and dear to any professional Business Analyst.

The good news is that if you are a Business Analyst or need to understand the work of business analysis, Podeswa gives you a framework. That is no small thing, and for that, he is to be commended. Whereas the BABOK (Business Analyst Body of Knowledge) gives you a model, Podeswa gives you what you could use as (though he would protest) a method or process for doing this work.Because this is an encyclopedia of techniques and terms, it isn't the most user-friendly book. It has lots of stuff, but most of it is listed alphabetically, not by situation, so you have to know what you are looking for to find it.And then, two beefs with his approach to this work that may not bother others.First, he assumes that Business Analysts will be part of software implementation. I understand that his approach has to account for that, but a large, large portion of my work and people who have done this work for and with me has stopped short of a software implementation. Just process work. Just understanding the problem. Etc. He doesn't offer disclaimer enough for my taste that a Business Analyst may put his/her time to good use serving ends other than software development or implementation.Second, he assumes that decisions happen in meetings. He includes lots of great meeting design templates and checklists. My experience says that meetings are not where real conversations take place. If you wait until that point to look for consensus, you are asking for trouble. The meeting will either make official what has been decided elsewhere or (God help you!) give lip service to the proposal until the REAL discussion happens in the hallway. So a Business Analyst may do all that Podeswa says to set up good meetings--and still not get the commitment to a decision he/she needs.Still, this is a useful addition to your library--for now.

Have been a BA for more years than I care to acknowledge :) and found this book to be very informative and a great reference. Particularly appreciate the detailed questions to ask stakeholders that have never occurred to me. They say you never know how ignorant you are until you learn something. Well, I've been ignorant and thankfully a more knowledgeable after reading this book. A great tool for any BA.