The Business Analysts Handbook (Anglais) Broché – 7 janvier 2009
|Neuf à partir de||Occasion à partir de|
Produits fréquemment achetés ensemble
Les clients ayant consulté cet article ont également regardé
Descriptions du produit
Présentation de l'éditeur
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
Dans ce livre(En savoir plus)
Quels sont les autres articles que les clients achètent après avoir regardé cet article?
Commentaires en ligne
Commentaires client les plus utiles sur Amazon.com (beta)
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.
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.
I recommend this as an essential tool in your BA toolkit especially if you perform business analysis in Agile software development environments, though many of these techniques can be adapted to other software development methodologies as well.