Category: Business Analysis

We Are Neo

We Are Neo

Recently I was talking with someone who is transitioning into Business Analysis. One of the things we talked about is "What other job do you know where you get paid to learn from experts." Our endless curiosity is met by an endless supply of industries, sectors, changing demands, new technologies, and on and on. There … Continue reading We Are Neo

Goals of Agile Analysis at the Delivery Horizon

Coming into Delivery, the Strategy has identified a need to be met, and the Initiative Horizon has identified a solution and its features. When working as an Analyst in the Delivery horizon, the key is to expend the least effort to discover information and support informed decisions about the solution. I’m sure you realize it … Continue reading Goals of Agile Analysis at the Delivery Horizon

Goals of Agile Analysis at the Initiative Horizon

From the Strategy Horizon, we understand the overall purpose of an initiative and its intended impact. But there is a lot that remains undetermined at this point. The initiative may have the organization's backing, but that doesn't define exactly how it will work, what resources are involved, or how much it will cost. The role … Continue reading Goals of Agile Analysis at the Initiative Horizon

How to Avoid Delegation Through Abdication

How to Avoid Delegation Through Abdication

As I am writing this, I have recently finished a panel discussion on Agile Transformation given at my IIBA Chapter. One of the recurring themes of any discussion involving Business Analysis is stakeholder engagement. Lack of stakeholder engagement shows up in a myriad of ways ranging from indifferent behaviors to actual hostility toward anything involving … Continue reading How to Avoid Delegation Through Abdication

BACCM: Impact on Knowledge Area 6. Solution Evaluation

BACCM: Impact on Knowledge Area 6. Solution Evaluation

This post wraps up this series with a discussion of how the BACCM relates to Solution Evaluation. In its introduction of this knowledge area, the BABOK guide makes an important distinction between Solution Evaluation from either Strategy Analysis or Requirements Analysis and Design Definition - that Solution Evaluation is performed against work that has been … Continue reading BACCM: Impact on Knowledge Area 6. Solution Evaluation

BACCM: Impact on Knowledge Area 5. Requirements Analysis and Design Definition

BACCM: Impact on Knowledge Area 5. Requirements Analysis and Design Definition

Because Requirements Analysis and Design Definition has a broader scope than many see envision, including measuring requirements and designs against overall organizational strategy, this Knowledge Area remains essential to Business Analysis. Here is where models, designs, and solutions are documented, revised, and verified. Inputs to this Knowledge Area include the Solution Scope, which represents potential … Continue reading BACCM: Impact on Knowledge Area 5. Requirements Analysis and Design Definition

BACCM: Impact on Knowledge Area 4. Strategy Analysis

BACCM: Impact on Knowledge Area 4. Strategy Analysis

When we talk about Strategy Analysis, we are referencing the activities and analysis that is performed to ensure alignment with business goals and to address a business need. We ensure that the need has strategic or tactical importance to stakeholders and that proposed solutions meet the need and fit within the context of the organization's … Continue reading BACCM: Impact on Knowledge Area 4. Strategy Analysis

BACCM: Impact on Knowledge Area 3. Requirements Life Cycle Management

BACCM: Impact on Knowledge Area 3. Requirements Life Cycle Management

According to BABOK v3, the following table represents the application of the Six Core Concepts to the Requirements Life Cycle Management Knowledge Area. BABOK v3, Table 5.0.1: The Core Concept Model in Requirements Life Cycle Management   First, we need to clear up the scope of Requirements Life Cycle Management (RLCM). Whenever something is called "Life Cycle," … Continue reading BACCM: Impact on Knowledge Area 3. Requirements Life Cycle Management

BACCM: Impact on Knowledge Area 2. Elicitation and Collaboration

BACCM: Impact on Knowledge Area 2. Elicitation and Collaboration

In previous articles, I have discussed how Business Analysis has suffered an identity crisis of sorts. But if there's one area which people think is core to Business Analysis, it is most likely summed up by the Elicitation and Collaboration Knowledge Area. You'd think I'd be cheering for that. Not quite. BABOK V3 Business Analysis … Continue reading BACCM: Impact on Knowledge Area 2. Elicitation and Collaboration