Elicitation Posts

Facilitation Top 5

Posted: January 30th, 2012 by Andrea Brockmeier. Comments »

Top FiveAs any instructor will tell you, one of the best things about teaching is learning from your students.  It happens in some way, big or small, every time you get in front of people who are expecting to hear how to do it “right.” 

Of course, there is no “right” a lot of the time.  In my classes, for example, I instruct and inform, but I also facilitate discussions about the options, and the students decide what’s going to work for them.

This brings me to the recent Facilitation Skills Workshop class I taught.  In this class, we learn about different facilitation techniques and then the students do the work; they actually facilitate each of the 12 sessions throughout the class.

7 Trends in Business Analysis and Project Management to Watch for in 2012

Posted: January 9th, 2012 by ElizabethLarson. Comments »

By Elizabeth Larson, PMP, CBAP, CSM and Richard Larson PMP, CBAP

The close of one year tends to make one reflect on what has occurred in the past year and ponder the future. Here we ponder some trends in the Project Management and Business Analysis fields for 2012. Here are our top seven predictions for business analysts (BAs) and project managers (PMs) in 2012.

1. Divergence of the PM and BA Role. In 2009 we predicted that as the economy tightened, organizations would decrease their project budgets and combine the role of PM and BA. For 2012 we believe that organizations will see the need for both roles, particularly on strategic projects, and move away from a combined role. There are several factors for this trend:

Turning Requirements Trash into Stakeholder Treasure – Part 2

Posted: August 23rd, 2011 by Bob Prentiss. Comments »

Treasure_ChestHello all – BobtheBA here and when we last left off we were exploring how innovation can be key to turning requirements trash into stakeholder treasure. The scenario we were exploring was a difficult stakeholder that was not forthcoming with their requirements. Your job (should you choose to accept it) was to improve your 1:1 interview process through innovation by looking at it through different eyes like those of a hostage negotiator. It may yield a different result or help you to be more prepared than what you thought possible.

Illicit Requirements

Posted: April 19th, 2011 by Bob Prentiss. 2 Comments »

NO_symbolHello all – BobtheBA here. Sometimes we can be inspired by the littlest things like a bee, a mosquito, or a play on words. Such was the case for me last month in all three examples, where the last of which I was inspired by one of my students who accidentally substituted “illiciting” for “eliciting” during a class exercise. We all knew what was meant and in class spelling does not count (which is the beauty of it happening during training – a safe environment!). However, in that moment I was immediately drawn to the concept of illicit requirements and what that might mean. Illicit is an adjective meaning “contrary to accepted morality or convention”. Is it possible to have requirements that do not fit accepted convention, i.e. “illicit” requirements? Absolutely!

Should Business Analysts Model Requirements?

Posted: April 8th, 2010 by ElizabethLarson. Comments »

During a recent client visit I encouraged the use of modeling as a way to uncover hidden requirements and expectations. One of my clients expressed her rather strong opinion that modeling requirements was not and should not be a part of business analysis work. Oh, she could accept the fact that uncovering gaps between the “as-is” and “to-be” using process models made some sense, but she was adamant that this gap analysis should be done by a business Subject Matter Expert (SME), not by a business analyst (BA). As to data modeling, well that was technical in nature and if done at all, she said, it should be done by the technical IT staff. Use cases were helpful to the testing staff, but were clearly technical and were not to be done by BAs. Prototyping? This should be done by developers—no question about that one!

Top Fundamentals for Successful Virtual Meetings

Posted: January 29th, 2010 by RichLarson. 4 Comments »

If you’re a project manager or business analyst and have ever facilitated or participated in a virtual meeting, you know they can be highly productive. And, highly frustrating if not run well. Here is a list of 5 things I think all virtual meetings should have to be successful:Picture1

1)      Test your technology. If you have never used the software or hardware for your virtual meetings, make sure you practice with a small group first. If you are doing a formal presentation, I suggest you reboot your PC right before you make it. We recently did a product demo where the presenter’s PC froze up right at the start. It took some fancy “tap dancing” to recover and keep the meeting going. Better to reboot first than to recover later.

The Parallax Effect on Requirements Analysis

Posted: December 3rd, 2009 by RichLarson. Comments »

Blog_Parallax_Plaeides_000002716873XSmallHave you ever gazed at the stars and found it difficult to focus on a particular one? It’s initially a bit disconcerting. If you look away a small amount, the star seems to become visible. Look straight at it and the star begins to dim and even disappear. Scientists call this the “parallax effect.” I just call it frustrating (I’m an impatient star-gazer).

Many times a problem we’re trying to solve or something we are analyzing is like that.

  • How often do you forget the name of something when you try to recall it, only to remember it later while walking outside, or when you are in the shower?