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.. 🙂

BABOK is all well and good – but in the "real world"…?

Skilled warrior

This post has been updated to include further detail on the way the BABOK presents information.

One of the main comments I heard today, at an Accelerated CBAP course, was “this is all fine, but in the real world things are different“.

The message was that what IIBA’s Business Analysis Body of Knowledge (BABOK) presented with regards Knowlegde Areas (KAs), and Tasks, didn’t actually align with what happened in projects.

Continue reading

The Pro's and Con's of using a Livescribe smartpen – for Business Analysis

In 2013 I purchased a Livescribe pen.

The Livescribe Echo pen

Livescribe Echo smartpen

For those that aren’t in the know, a Livescribe pen allows you to capture the conversation taking place while you are writing notes.

By using specially marked paper, the pen can synchronise the audio being recorded with what you are writing and, at a later stage, you can press the pen anywhere on the page (on which you have written your notes), and the conversation that was taking place at that particular time is played back to you.

I have used this pen in a lot of elicitation situations and, in this post, I would like to describe some of the “lessons learned”.

Which Livescribe Pen have I got?

There are several models of the Livescribe pen available. The latest version in Livescribe 3 Smartpen and it offers some pretty cool functionality.

When I was looking at the pens 3.0 hadn’t been released yet.  And I also reasoned that I did not need real-time syncing to the cloud.

As such I chose the Echo Smartpen (see image above). You can see what this pen is capable of here and here.

How I used it?

In any elicitation situation where I was taking notes, I would use the Echo to keep a record of the actual conversation taking place. At the same time I would take be taking notes.

After the session I would playback the conversation at various points, to confirm that my notes were correct, or to expand on what I had written (you know that written notes don’t always capture everything that was discussed).

Using the Livescribe Desktop app, I was able to convert my written notes into a dynamic PDF that could be archived, or distributed to others in the team. This PDF had the audio embedded and the reader could click on any word to playback the discussion taking place at that time.

When I was not the scribe

Often when you are running an elicitation workshop, you are up in front of everyone, leading discussions, asking questions, prompting and encouraging responses. You can’t do this and write everything done. In this case, there is usually someone else who has been assigned this task (the scribe).

When I was in this situation, I was still able to use the Livescribe. Whenever there was a change in discussion, or a particular point that could be summarised in a word, I would write that on the special dot paper. After the session, I could still playback what was said at that point.

The Pro’s of using the Livescribe

Using the Livescribe pen has a lot going for it:

  • You are able to capture the whole discussion and tie it in with your notes.
  • The audio is synchronised to the notes you have written, so you can playback the conversation that was taking place at specific points.
  • The notes with audio can be shared with other members of the team, or with the stakeholders (f desired), as part of your Work Product.
  • You are confident that you can go back over the audio to pick up things that were said, but not written down.

Lessons Learned

Using the pen has been very handy, but it also has its down-sides. What follows are some of the “lessons learned”.

Ask Permission

Before actually using the pen during any elicitation event where other people are involved (workshops, interviews, active observation, etc), ask if it is OK to record the conversation. Usually people are pretty good about this and don’t mind. However it is important to reassure participants that you are using the pen merely as a tool to support the notes you are taking. And as an professional BA, you need to remember that, also.

Don’t let the pen be a replacement for Active note-taking

Use the pen to capture the conversation, but don’t be lazy. You still need to actively listen, and write down the important points from the conversation.

You still need to Confirm

Just because you have an audio record of the conversations that you have, does not mean that you don’t have to validate, that the stated requirements match the stakeholder’s understanding of the problem and the stakeholder’s needs.

What is written, and what was said, still might not be what was actually meant.

Make your notes meaningful

As I mention above, in a workshop situation you might just write a word of two and let the pen capture the conversation.

I’ve had situations where, after a series of seven one-hour workshops I’ve gone back over my notes, and haven’t been able to work out which part of the workshop the squiggle on the page tied in with, or what that strange sentence that I wrote (which meant something at the time – three days earlier) actually referred to.

When you are writing “headings” to describe certain parts of a conversation/discussion, write something meaningful, so that, after five days, it will still be clear. The discussions in workshops, or interviews, don’t always take place in nicely define “sub-sections”.

Never just record the sessioN

This is a classic newbie mistake, and relates to something I wrote above, Never, ever, just record the elicitation session thinking with the intention of “writing up the notes later on”. You might have have a three day workshop. Remember – when you playback the audio, it will take three days to listen to it! (And this includes all those side-conversations, jokes, and irrelevant comments that get made.)

Secure the output

This is related to “Ask Permission” above.

Regardless of whether you have been given the OK, by the session participants, to use the Livescribe, be aware that a lot of things are said during the workshop/interview/active observation session that might not be relevant,or are “off-record”. It may note be your intent, but you don’t want a situation where something someone says is later used against that person.

Have a way of charging the pen

The pen can be used for several hours, but it won’t last for ever. With the Echo I could plug a USB cable in to it, and plug that into my PC. This allowed the pen to be constantly charged, while I wrote notes.

Ensure you have enough paper

The live scribe uses paper with microdots on them. This allows the smartpen to be able to map what is being written, and the location on the page.

Livescribe sells this paper in the form of notebooks.Ensure that you have an extra notebook with you. You might never use it, but, then again, you might. (You can print out the Micro Dot paper yourself, but read the next “Lesson Learned” for more on this.)

71szq9bc+jL._SL1500_

Keep track of the pages

Each page in the notebook has a unique, sequential, ID. This way, the Livescribe can keep all the pages in the correct order. Don’t write your notes on random pages. It makes it difficult, when it comes to working with the notes, and audio, when you are back at your computer.

Printed Pages

As mentioned above, you can print out the Micro Dot paper yourself. If you do this, you will have several loose sheets. These are handy if you want to put the sheets in a ring binder, etc., but be aware that, as with the notebooks, each page is in sequential order. Keep them in the correct order (the page number is printed on each). This saves a lot of pain when exporting to a PDF, etc.

 

Conclusion – Would I recommend using the pen?

The pen is an incredibly handy tool (with the later version offering even more functionality, as well as looking like a real pen).

However, for the purposes of Business Analysis I would not, personally, recommend using it.

Why?

As I alluded to in some of the Lessons Learned, being able to record the conversation taking place is valuable. But it also makes you relax.

It’s easy to think “Oh I won’t write that down – I’ll go back over the audio later.” WRONG! The idea of the elicitation session is to actively capture the main points, In real-time.

That’s part of being a good BA. Active Listening, and Active Note Taking. You are in the elicitation session to really understand the message that the stakeholders are communicating. And you need to make sure that you have captured it properly.

Going back over a recording of a session, in my opinion, is of little value. The real value should be in your notes. If they need expanding upon, or clarifying, that is something that needs to be done directly, with the appropriate stakeholder.

I’m not saying that a smartpen is worthless. But if you think about it, BA’s have been taking notes as part of the elicitation process for years. How many have recorded the session?

However…

My conclusion above, however, is how I feel about it. For you, fellow BA, it might be a different situation.

In fact, someone pointed out to me that their handwriting was terrible, and they often could not read their own notes. Having the pen would mean that they could, indeed, dive into what was being said at the time the notes were made.

I can’t argue with this reasoning…

Other Reviews

For other reviews of the Livescribe pens, click here.

Your opinion

Have you used the Livescribe pen? What are thoughts on it? Do you think that I am wrong in not recommending it for BA work? Feel free to let me know in the comments.

 

 

  • Handwriting Isn’t Dead – Smart Pens and Styluses Are Saving It – The Wall Street Journal
  • Future Of Research – Research Tools for the Age of Digital Scholarship
  • Hands-on with Livescribe’s new Android support
  • Digital pens allow smooth, convenient communication at schools, hospitals

What I like in an Agile article, post, or book…

Preaching to the converted

…is balance.

There are so many Agile books, articles, and posts that do one of two things:

  1. spend a lot of time pointing out how evil, backwards, or just plain stupid anything, that isn’t Agile, is.
  2. Spend a lot of time shouting (enthusiastically) about how great Agile is, and that you are stupid for not embracing it.

I like the idea of Agile, but I also believe something should be able to stand by itself, without resorting to slagging off any alternatives. Let the good points of the methodology/ideology/whatever-ology be seen, and leave the reader to convince themselves, rather than trying to do it for them.

At the same time, don’t just rant, and rave, about the fact that I “just have to” adopt Agile, or I’ll be considered a Luddite, a caveman, or just a person who is not willing to “see the truth”. Give me good, sensible, reasons, and I’m likely to keep reading.

A good example of something that doesn’t do either of the two things mentioned above, is something that I am reading at the moment – “Agile Estimating and Planning” by Mike Cohn. He steps you through the idea of Agile, with regards to planning, without once talking about Waterfall.

It’s a strange experience for me. With regards Agile I have wanted to believe. The problem was that every time I tried to learn more I met glazed eyed enthusiasts that just told me “Agile is good…Waterfall is evil”. Agile Estimating and Planning, however, has me nodding my head with every chapter I read.

 What do you think?

Do you agree? Or am I just talking out of a hole in my head…?