The Community Blog for Business Analysts


Elicitation (BABOK KA)

NO Image:
As business analysts, we are often in the fray of designing.  Whether it’s a user interface, report or data fed from one system to another; business analysts create interfaces with human beings and systems.  Our design choices impact users and other systems in a very real way.  This power can go unnoticed even in our own minds....
1 Responses
Years ago, I was consulting as a Principal Business Analyst for the second largest company in the world in the money transfer business. One fine morning, I was engrossed in my work when my business stakeholder, (let's call him Tom) arrived at my desk.  Tom: Praveen, I have a change request for you. Well, this is a new business requiremen...
1 Responses
This entry was published on May 01, 2016 / Praveen Udupa. Posted in Elicitation (BABOK KA), Requirements Analysis (BABOK KA) . Bookmark the Permalink or E-mail it to a friend.
  Knowledge can be explicit as well as tacit. Explicit knowledge is something that can be easily documented, studied and transferred from one individual to another. On the other hand, tacit knowledge is knowledge that cannot be easily documented, taught and transferred from one individual to another. It includes the beliefs, attitudes,...
0 Responses
This entry was published on Feb 28, 2016 / CVM. Posted in Elicitation (BABOK KA). Bookmark the Permalink or E-mail it to a friend.
I recently had the chance to spend half a day with some customer service representatives (CSR) in one of my organization's call centers, in order to get a better grip on their work and to see how they interact with the multiple systems available to them to better serve our customers. I didn't answer any customer call (God bless them!), but I sat n...
2 Responses
This entry was published on Jan 16, 2015 / Eric Provost. Posted in Elicitation (BABOK KA). Bookmark the Permalink or E-mail it to a friend.
A while back, I was reading a Computerworld - Singapore article on Business Intelligence and embedded in it was a small, but significant, truth about the business analyst role.  The article points out that a common mistake made by many organizations is to treat the business analyst as a request taker. That is - if the bu...
1 Responses
This entry was published on Jan 07, 2015 / Adrian M.. Posted in Business Analysis Planning (BABOK KA), Elicitation (BABOK KA). Bookmark the Permalink or E-mail it to a friend.
The problem: Do you know when you’re done? Given a specific project with a reasonably defined charter and clear business goals you, the business analyst, set out to elicit and document the detailed business requirements. So when do you stop? Whether you lead a team of business analysts or you do the work yourself, you probably struggled tr...
2 Responses
This entry was published on Dec 03, 2014 / Adrian M.. Posted in Elicitation (BABOK KA), Analytical and Problem Solving Skills. Bookmark the Permalink or E-mail it to a friend.
The question will undoubtedly arise during your tenure as a business analyst, ‘How do I manage a difficult stakeholder?’ I once encountered a stakeholder, a very highly respected mathematician, who had developed an application based on a mathematical model of his weather systems. The algorithm was amazing. The application sucked. It wa...
4 Responses
As part of preparation to sit the IIBA CBAP exam, I wanted a one page summary of the overall BABOK flow. The first step of creating a summary matrix showing a derived master list of documents (e.g. Inputs + Outputs) versus the process that creates or uses it was interesting, but not entirely helpful. By using the matrix to create an indicative ...
1 Responses
In my previous posts I outlined how I was able to succeed being the first and only BA at a company and the importance of establishing trust between you and the stakeholders.   So you're the first BA at a company.   All are looking at you and thinking what can this person do for me? Good question.   What can you do f...
0 Responses
"Garbage in, Garbage Out" - To elicit accurate requirements, the business analyst must learn to ask the “right” questions “the right way”. The manner in which questions are delivered and the composition of these questions have a direct impact on the usefulness of the responses we receive.   If your questions are properly and thoughtfully fra...
2 Responses
This entry was published on Mar 02, 2013 / Stephanie Famuyide. Posted in Elicitation (BABOK KA), Soft Skills. Bookmark the Permalink or E-mail it to a friend.
“Something is happening. We are becoming a visually mediated society. For many, understanding of the world is being accomplished, not through words, but by reading images – Paul Martin Lester,
“Syntactic Theory of Visual Communication Research has shown that communication with a visual dimension is more effective than communication without. Hero...
0 Responses
This entry was published on Feb 16, 2013 / Stephanie Famuyide. Posted in Elicitation (BABOK KA), User Interface & Usability. Bookmark the Permalink or E-mail it to a friend.
For those of you who do define requirements for their software development projects, but are new to buying packages, a cautionary warning; they are not the same thing. Consider the following “the system shall” requirement  statements.   1) The system shall determine if a person ordering pizza is a current customer. 2) The system shal...
0 Responses
This entry was published on Feb 08, 2013 / David Wright. Posted in Elicitation (BABOK KA), Requirements Analysis (BABOK KA) . Bookmark the Permalink or E-mail it to a friend.
I started my career as the administrator in a project management department.  The first fact drilled into my head was that “the job ain’t finished until the paperwork is done’.  To emphasize this fact, this rule was printed and put up on the wall with a picture of a toilet paper roll.  It worked.  I know you can see the picture ...
0 Responses
This entry was published on Jun 10, 2012 / hildasteyn. Posted in Elicitation (BABOK KA). Bookmark the Permalink or E-mail it to a friend.
Information Systems Users don't know what they want... So, don't ask them what they want: and definitely don't write some software and then say "how's this look?". On the other hand, don't have someone spend weeks talking to various people about what they want ( and not get to talk to other people ), write it all down and deliver a document, sayin...
1 Responses
This entry was published on Aug 06, 2011 / David Wright. Posted in Elicitation (BABOK KA), Business Analysis. Bookmark the Permalink or E-mail it to a friend.
Requirements gathering is an essential part of any project and project management. Understanding fully what a project will deliver is critical to its success. This may sound like common sense, but surprisingly it's an area that is often given far too little attention. Many projects start with the barest headline list of requirements, only to find ...
2 Responses
This entry was published on Jun 08, 2011 / a.prvz. Posted in Elicitation (BABOK KA), Requirements Analysis (BABOK KA) , Business Analysis. Bookmark the Permalink or E-mail it to a friend.
What do you need the most when eliciting Requirements? Face-time with Subject Matter Experts and their Managers.  As a Business Analyst employed in a typical organization, what is the thing you get the least of? Face-time with Subject Matter Experts and their Managers. Who will Subject Matter Experts and Managers make time to see? Outside Cons...
0 Responses
This entry was published on Apr 28, 2011 / David Wright. Posted in Elicitation (BABOK KA), Business Analysis. Bookmark the Permalink or E-mail it to a friend.
When creating a data dictionary, it is critical not to design with it.  You should not be attempting to create a database nor should you be showing the relationships of data.  This will be a detailed description of the data involved in your project.  It will also be one of the largest morale draining approval processes you can have f...
1 Responses
This entry was published on Aug 05, 2010 / Seilevel. Posted in Elicitation (BABOK KA), Data Analysis & Modeling, Business Analysis. Bookmark the Permalink or E-mail it to a friend.
I've come to understand the necessity for stakeholder involvement throughout the Requirements Gathering process. But what if it's another BA who is the stakeholder company's point of contact whom you'll be gathering requirements from instead of the stake holder themselves? Is there an advantage? How do we leverage the strength of our Requirements&#...
1 Responses
This entry was published on Dec 02, 2007 / Chris. Posted in Elicitation (BABOK KA), Business Analysis. Bookmark the Permalink or E-mail it to a friend.


Blog Information

» What is the Community Blog and what are the Benefits of Contributing?

» Review our Blog Posting Guidelines.

» I am looking for the original Modern Analyst blog posts.



Modern Analyst Blog Latests

Jarett Hailes
Jarett Hailes
As we start a new year many of us will take the time to reflect on our accomplishments from 2012 and plan our goals for 2013. We can set small or large goals. goals that will be accomplished quickly or could take several years. For 2013, I think Business Analysts should look to go beyond our traditional boundaries and set audacious goals. Merriam-...
2 Responses
Howard Podeswa
Howard Podeswa
Recently, I was asked by the IIBA to present a talk at one of their chapter meetings. I am reprinting here my response to that invitation in the hope that it will begin a conversation with fellow EEPs and BAs about an area of great concern to the profession. Hi xx …. Regarding the IIBA talk, there is another issue that I am considering. It's p...
11 Responses
Adrian M.
Adrian M.
Continuing the ABC series for Business Analysts, Howard Podeswa created the next installment titled "BA ABCs: “C” is for Class Diagram" as an article rather than a blog post. You can find the article here: BA ABCs: “C” is for Class Diagram Here are the previous two posts: BA ABCs: “A” is for Activity Diagram BA ABCs: “B” is for BPMN
1 Responses
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC