A look at “A Navigator to Business Analysis”

A review of “A Navigator To Business Analysis”

I’m a Business Analyst, I’ve got my CBAP certification from the IIBA, and I’ve got a few scars. So when I saw that Sergey Korban had a new book out, I decided to give it a critical look. 

What is it?

“A Navigator to Business Analysis” is the latest book from Sergey Korban (Aotea Studios). 

The cover of "A Navigator to Business Analysis"

In the words of the book itself:

This book is for everyone who wants to either start a business analysis career or would like to learn practical tips and tricks to get the job done in an effective way.

 

My “first glance” impressions

Did I read the book thoroughly when I first got it? No. I looked for clues to see how valuable this book would be for a Business Analyst,

I looked for clues to see how valuable this book would be or a Business Analyst. I scanned the Table of Contents, I looked at the headings, and I scanned through the diagrams.

Subject Matter Indicators

The title is “A Navigator To Business Analysis“. This is a good start.  I have never seen the word “Navigator” used in this way before, but it told me to expect a lot of guidance.

Further in, I saw this quote

A guided tour into a terra incognita is better than a journey there on your own...

This was another sign that the author has a good idea what the purpose of their book is. They haven’t just vomited words on the paper and bundled it up.

Breadth of content

Consisting of 400 pages, the book is divided into three parts, each of which contains several modules.

The parts are:

  • Part 1 – “Business Analysis“,
  • Part 2 – “Beyond Business Analysis“, and
  • Part 3 – “Build Up Your Value
Contents of A Navigator to Business Analysis

An overview of the contents of “A Navigator to Business Analysis”

That gave me a good overview, and I was excited to see (yep – I’m a BA geek)  the contents of the Beyond Business Analysis modules. It’s good to see these domains listed.

Flicking through each module, I scanned the titles, and the sub-titles, and looked at the diagrams. This was dangerous as I often found myself stopping because Sergey was covering material that I did want to get into more. My goal, at this stage, however, was to NOT read the content.

Charts and Diagrams

Sergey has filled “A Navigator to Business Analysis” with a lot of charts and diagrams that illustrate further what he has written.

Even on their own, these are incredibly valuable. (I suggest you check out the website for Aotea Studios where you can download several great BA related charts).

(Note – their change management chart was included in the book Project Management for Healthcare by David Shirley)

Practical Advise, Practical Tools, and Additional Reading

Scattered (generously) through the pages, Sergey has included: Practical Advice icons, Practical Tools icons, and Additional Reading icons.

A Navigator to Business Analysis Practical Advice icon      A Navigator to Business Analysis Practical Tools icon       A Navigator to Business Analysis- Additional Reading icon

When the Practical Advice icon is visible on a page, there is also accompanying text that relates to the contents of the page. As with the Charts and Diagrams, if this was the only text that you read on each page, you will learn a lot.

The Practical Tools icon can be seen on pages that contain a useful resource. This includes templates, matrixes, checklists, diagrams, etc. (As discussed above.)

The Additional Reading offers suggestions of material that will supplement the contents of the book.

Thought-provoking Quotes

At several spots through the book, Sergey has included quotes from variAll you need is the plan, the road map and the courage to press on to your destination..ous sources that are relevant to the content at that stage.

For example, in the section
“Business Analysis Lifecycle”:

 

I really liked these. They gave you that little boost of inspiration. (Some of these quotes were even from Aotea Studios).

Revisions

Reading through the content and looking at the diagrams, in a book is one thing. Recalling what you have read is another.

At the end of each module, Sergey has included a Revision page. This usually includes a series of questions that prompt you to check whether you can recall what you’ve read.

This is something useful for both newbie BAs and seasoned BAs alike.

Actually making the effort to go through each question, and writing out a detailed answer, would either a) ensure that you truly understand what you have read, and b) you truly understand what you have read. (This works for everything, though,)

 

The Meat of the book (aka – the actual text)

The next step was to actually read what Sergey had written.

Writing Style

The text in “A Navigator to Business Analysis” was, generally, easy to read.

Sergey wrote in an efficient manner without “added fluff”. The opening paragraph would immediately answer the question the reader has – “what is this section, or module about?” The following paragraphs provided more details, often supported by (as mentioned) diagrams, or charts.

The only thing that made it a little bit difficult, for me, was that the typeface is entirely sans serif. (Although there appears to be no evidence that there is a difference between serif and sans serif typeface when it comes to readability.)

Valuable?

Did the material expand my understanding of Business Analysis? Yes.

The field of Business Analysis is something that is still trying to define itself. Sergey takes this into account. The topics in the book cover not only what are considered the “core skills” of a Business Analyst, but also expand upon this to show how, in reality,  Business Analyst interacts, and works, with many other domains in an organisation.

Alignment with BABOK

About a year ago, the IIBA, published their latest edition of the Business Analysis Body of Knowledge (BABOK). This is often seen as the defining work for Business Analysis work.

Books on Business Analysis should not just repeat, or rehash, what can be read elsewhere. That is, they shouldn’t just be the BABOK using different words.

And this is what impressed me with “The Navigator to Business Analysis”. It aligns with the latest BABOK, while expanding on it, and add insights that 33 years of experience as a BA has given Sergey.

Is there anything wrong with the book?.

While the book is a great resource for Business Analysts, there were two things that bothered me.

  • As already mentioned, the use of sans-serif font for everything made it, for me, a little difficult to read, (This is a personal thing.Others. might not have a problem with it.)
  • When reading a PDF, I always like to use the structured bookmarks. These are the ones that can be displayed on the left side of Adobe Reader (for example). They allow me to get an overview of the layout of the book, as well as easily navigating to a particular section. “A Navigator in Business Analysis” didn’t contain logical bookmarks.
    (Sergey has told me that this is something that they are working on improving).

 

Would I recommend this book?

Yes. Most definitely.

I found the book to be extremely valuable. As I mentioned above, the Business Analysis profession is still being defined. “A Navigator to Business Analysis” gave me an excellent understanding of how it worked, how to work in it, and how it fitted into the “bigger picture”.

This book would have been very handy when I first started on my Business Analysis journey.

I recommend checking the book out. On the Aotea Studio website, you can download a sample.  Have a look, and decide for yourself whether this book will be of value to you.

 

Useful Resources
  • “A Navigator to Business Analysis” information page (Sergey Korban)
  • Business Analyst course
  • Business Analysis Revised Edition (Malcolm Eva, Keith Hindle, Craig Rollason)
  • How to Start a BA Career (Laura Brandenburg)

What is your idea of what a BOK is?

Magic_Scrolls

After my last post, a lengthy discussion started in LinkedIn regarding what the BABOK is.

One commenter – Magnus Stensson – posted a superb comment…

I think there are, roughly speaking, three different groups of interpreters when it comes to BOK’s, be it BABOK, PMBOK, etc.

1. Those who see them for what they are. A collection of current best practices, tools, tips, methods, vocabulary, etc.. grouped into somewhat logical sections called knowledge areas. The reader can get tips and inspiration while choosing how to apply the information in there to suit the environment they are working in. This group has the best use of the BOK as they adapt it to reality and use it to enhance their knowledge and practical ability in the area.

2. Those who, because it is not prescriptive and describes everything in a How to manner, see it as fluffy, too theoretical and incomprehensible, and thus unusable. They are the ones who grumble about it being too theoretical and not useable in the real world.

3. The BOK evangelists who see it as the bible of all things in the area, They seek to apply all knowledge areas and techniques to all projects regardless of scope, creating massive documentation and inefficiency. Everything is referred to against the BOK. “We must do transition requirements as the BOK says so”. “we need these models because BABOk says so”,.. etc. (unfortunately I’ve worked with these people….) . This group refuses to adapt the BOK to suit the situation and end up destroying its reputation because their co-workers, who haven’t read it, see it as a theoretical source of impracticality.

He summed it up nicely.

Further to that, his parting shot was…

The views in discussions like this one reflect which group people subscribe to.. 🙂

CBAP – I made it, but it's not the destination that I thought it was

CBAP is not the final destination

 After a lifetime of progressive career moves, I started, two years ago, on a serious journey towards attaining CBAP certification from the International Institute of Business Analysis (IIBA).

At the end of 2014 I sat and passed the exam.

It’s been an awesome adventure. There have been struggles and achievements. I’ve had to fight off ogres that wanted to prevent me reaching my goal. (Most of these were in my head). I have met many wonderful, eclectic, people along the way, and have been supported (both morally, and physically) by many heroes and heroines that have been there for me.

And I have learnt a lot. Studying the IIBA’s BABOK (Business Analysis Body of Knowledge), has allowed me to formalise the skills and knowledge that are invaluable for a Business Analyst.

And while I thought that achieving that right to vaunt that I had achieved CBAP status would be the pinnacle of my journey – the very goal that I was striving for, it turns out that it isn’t.

Everything described in the BABOK was, for me, enlightening. Every sentence written in this tome of knowledge is valuable. As I read, and re-read each paragraph, and viewed each diagram, I felt an enriching of my comprehension. As if my brain started working at new levels….

However, the more I read, the more I realised that the BABOK was merely providing an extremely good high-level map of the BA world. One with signposts to areas that needed further exploring.

CBAP isn’t my destination… 

IIBA CBAP … Merely a stop along the way

Today I read …"How to Use Enterprise Architecture to Deliver the Right Solution"

Enterprise Architecture This is the another post in my “Today I read …” series where I aim to summarise. or recapitulate, excellent, and educational, articles that I have read
Previous: BA Practices in a Virtual World

Today I read an excellent article on the IIBA site: “How to Use Enterprise Architecture to Deliver the Right Solution“, authored by Sergio Luis Conte.

For me, this was an excellent article.One that really helped me get a better understanding of Enterprise Architecture, especially from a Business Analysts point-of-view.
Sergio pulls relevant information from the EABOK (Enterprise Architecture Body of Knowledge), the BABOK (Business Analysis Body of Knowledge), along with other relevant sources, to detail:

  • What Enterprise Architecture is,
  • Why it should be used,
  • When it should be used, and
  • How it should be used.

The “What”

Sergio provides a quote from Gartner to answer this one:

a discipline for pro-actively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the execution of change toward desired business vision and outcomes. EA delivers value by presenting business and IT leaders with signature-ready recommendations for adjusting policies and projects to achieve target business outcomes that capitalize on relevant business disruptions. EA is used to steer decision making toward the evolution of the future state architecture. (Gartner Group 2013)

He goes further by describing how Enterprise Architecture consists of several independent, but cohesive architectures: Business Architecture (BA), Application Architecture (AA), Technology Architecture (TA), Security Architecture (SA), and Information Architecture (IA).

The “Why”

Sergio explains that Enterprise Architecture is a way of thinking about the Business from a system management theory perspective. He also ties this nicely in with information presented in the BABOK (under competencies).

The “When”

Enterprise Architecture is used when a business needs to transform itself – when a desired future state is recognised.To identify the gap between the current state, and this future state, a gap analysis is performed, and appropriate steps are taken to make the necessary transformations,

Image “In search of problem situation to solve” – Sergio Luis Conte (IIBA)

This is a repeating cycle. Businesses attempt to adapt to an ever changing environment.

The “How”

For the “How”,Sergio mentions that there are several models available for working with Enterprise Architecture. The one he concentrates on, though, is “The McKinsey 7S model” that focuses on, and analyses, seven elements – strategy, structure, systems, staff, skills, and shared values.

Sergio explains each of these seven elements in further detail, including listing references for further reading.

Conclusion

All-in-all, a great article that helped me lot, and gave me enough information for further reading.

The link to the full article is: https://www.iiba.org/News-Events/Best-Practices-for-Better-Business-Analysis/BP4BBA/2013/enterprise-architecture-to-deliver-right-solution.aspx

If you like this post, feel free to share. If you have comments that you’d like to make, please go ahead and use the comment box below.

Thanks for reading.