Archive for June, 2008

We all need heroes

We have had a lot of new starters at work recently and I was asked to give an overview of business analysis. It is one of many core capabilities and service offerings competing for recognition within our organisation. Project Management and ITIL are the most popular communities of practice. I think this is because consultants in these areas tend to be highly paid in comparison to BAs as these roles often have an element of strategic project coordination and communication with the executive or project governance board.

I thought I would show how the capabilities of a BA are wide ranging and can add value and support throughout the life of a project.  We all need heores is not about BAs being Superman and “coming in to save the day” but rather, we are the support and quiet strenght within the project team - the “reluctant heroes” that have a lot of skills and capabilities to offer. We all need heroes ………

SlideShare | View | Upload your own

As BAs we often use differing abilities in order to deliver what is required for our client area.  We support projects and our analysis skills can be utilised during the various phases of system development and delivery of a project and the discipline of Business Analysis has much to offer with proven methodologies, frameworks and tools to help you get the job done.

 

Business Analysis Life Cycle

Those performing Business Analysis are typically known as Business Analysts (BAs) and often work in dynamic environments where change is not only anticipated, but is expected and embraced. I was recently asked to look at developing a Business Analysis Life Cycle to help frame an approach to BA work. I started with the broad definition of Business Analysis -  as a vehicle to generate and present unambiguous information to help facilitate the decision making process and deliver business outcomes and stressed that the and involves a portfolio of techniques that focus on demonstrating an understanding of the client’s needs and identifying how best to meet those needs.

I believe Business Analysis is increasingly encompassing broader organisational challenges (e.g. strategic planning and business health checks) and solutions to business problems, which may include systems, processes, organisational change or a combination of these.  Whetehr you are a Systems BA, Process BA or Finacial BA, the discipline of Busienss Analsysis is a core caspability. As a consultant this core capability, Business Analysis, is achieved through developing effective relationships with the business and technology Subject Matter Experts (SMEs), extracting, analysing and presenting relevant information to ensure key stakeholders have a common expectation of the quality, scope, cost and benefits of the preferred solution. It very much about facilitation and communication of requirements to meet needs of stakeholders.

To develop the Business Analysis Life Cycle (BALC) I reviewed the framework of the key BA professional bodies:

·         IIBA - International Institute of Business Analysis

 ·         ABAA – Australian Business Analysis Association

and found that the key concepts of any BA life cycle are: 

·         Establish and define the purpose of business analysis;

·         Establish and define the core activities an BA may be required to undertake in achieving the business purpose; and

·         Establish and define the key facilitating processes and resources that will support an BA in achieving analysis objectives.

It is important that the BALC reflects the iterative facilitation and co-ordination processes undertaken in dynamic environments  and therefore the following skills/governance actions of  Communication,  Planning and  Control are central to the approach and support the core elements/activities of the BA role and reflects the analytical process from initiation/definition through to conclusion. I see these six phases as:

1.       Initiation and Scoping

2.       Research and Analysis

3.       Requirements Specification

4.       Design

5.       Development and Implementation

6.       Evaluation and Conclusion