A Guide to the Business Analysis Body of Knowledge (Babok Guide): Version 2.0 (Anglais) Broché – 31 mars 2009
|Neuf à partir de||Occasion à partir de|
Produits fréquemment achetés ensemble
Les clients ayant acheté cet article ont également acheté
Descriptions du produit
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.
Détails sur le produit
En savoir plus sur l'auteur
Quels sont les autres articles que les clients achètent après avoir regardé cet article?
Commentaires en ligne
Meilleurs commentaires des clients
Ce n'est pas une introduction à l'analyse des besoins, ni un ouvrage de pédagogie mais une "somme" comme son titre l'indique(body of knowledge = corpus des connaissances).
Comme beaucoup d'ouvrages de référence, celui-ci est difficile à lire. Il n'y a pas de fil conducteur, les "underlying competencies" sont classées par ordre alphabétique, et les différentes techniques sont présentées de manière neutre.
C'est un excellent ouvrage de référence, à déconseiller vivement aux débutants (si par hasard l'idée leur prenait).
Difficile à noter (Je mets *** faute de pouvoir m'abstenir).
Notons que la totalité de l'ouvrage peut être consultée gratuitement sur Google books, et que la version 1.6 est téléchargeable gratuitement.
Commentaires client les plus utiles sur Amazon.com (beta)
This book will tell you everything you need to know to be an expert Business Analyst. And then you will have to go elsewhere to learn how to do all those things.
Some students are disappointed that this book doesn't actually TEACH them how to do a Business Case, for example. It only tells them what their contribution to a Business Case should be, and it tells them what the general elements of a business case are (and identifies techniques useful in developing those elements). Likewise for all the other pieces of a Business Analyst's work.
In addition, some students struggle with the model depictions of the work (a diagram showing how one piece relates to another). For some, this is a whole new language. Once you understand what is in the diagram, it makes a great chapter (or section) summary. But it isn't intuitive, unless you have the background necessary to understand the diagram.
But if you want to prepare for the IIBA exam, or complete a certificate course in this area, you must come to terms with the BABOK. Accept no substitute. Just don't expect that this book alone will make you an expert Business Analyst in all the areas you must master. It won't. But it will tell you what it is that you need to learn, in a systematic and complete way.
The BABOK is NOT meant to be a textbook so instructors please stop trying to use it as one. It adopts a format with each topic to include: purpose, description, input, elements, techniques, stakeholders, output and then forces EVERY topic to adhere to that format which often felt forced, clunky and out of place. It does not explain HOW to do anything just that it may or may not need to be done. For example under requirements for re-use a Configuration Management Systems is needed but it doesn't tell you general information that would need to be included or how to set one up or even what it is. I understand that every business, process and project will be different so they want to keep the perspective broad but there are key components of each collaboration that are not addressed which is a disservice to BA's trying improve their skills or BA departments/organizations trying to set standards. There are NO examples in this book (not even of a basic requirement), no sample project so you can see how it all fits together or give a concept context which are only two reasons why this makes for a horrible textbook. There were obviously multiple contributors/writers for the book (some of whom were my instructors) so it reads a little hodge podge at times. There is no flow.
The BABOK is also NOT a resource guide. It's too wordy, vague and inefficient and there's no direct way to any topic. It will take you longer to find your topic then to just look it up on the internet. Once you find your topic the information is sparse (which is what you would expect from a resource guide) but definitions are filled with industry "speak" (lots of big words but says nothing). And again the flow is a head scratcher. For example Defining Business Need which I think of as one of the first tasks in a process isn't addressed until Chapter 5.
Since this class was also a prep class for the exam we took "quizzes" every week and the questions were samples from the actual exam. If that is true then this book is the ULTIMATE STUDY GUIDE. Memorize it word for word because the answers to the questions on the quiz were taken word for word from the text. Regurgitate the text on exam day and voilà you'll be the envy of BA's everywhere.
To be fair after much criticism the IIBA did come out and say the BABOK is not meant to be a textbook OR a resource guide but I'm unclear what it was meant to be. Too bad IIBA didn't take this opportunity to raise the bar and set some basic standards for all BA's.
It splits the discipline into six key knowledge areas:
* Business analysis planning and monitoring
* Requirements management and communication
* Enterprise analysis
* Requirements analysis
* Solution assessment and validation
What's especially good is that it puts such a strong focus on planning and managing what we have to do, as well as going through the basics of eliciting, documenting and analysing, communicating, assessing, and validating.
Alongside these 6 knowledge areas, it also has a whole section on underlying compentencies (the 'soft' skills we need as business analysts), and another detailing 34 techniques we typically use.
For those that have already seen/used version 1.6, there are some key differences. The layout, tone, and diagrams are more consistent; the techniques are in their own separate section (rather than spread through the knowledge areas); the tasks that encroached slightly on the project/line management disciplines have been removed; and the enterprise analysis knowledge area has become more focused on what I would call 'problem analysis'.
A great reference that I keep on my desk all the time -- and I'm really looking forward to the next publication which will focus more fully on the Strategic aspects of what was covered under enterprise analysis in version 1.6.