In this article, we will examine one of the key skills of a Business Analyst (BA), the ability to assess needs.

Initially, this topic may seem redundant as many of us assume that we have the necessary skills and understand the concepts required to be a business analyst. However, when we delve deeper into the actual tactics of being an effective business analyst, we will realise that it depends as much on hard skills such as customer satisfaction as it does on analytical process skills.

Needs assessment

The needs assessment domain includes five key activities related to understanding a business problem or opportunity and assessing different inputs to help develop an effective solution

1: Use problem and opportunity analysis techniques to provide input to create a solution scope or a business case

2: Collect and analyse information from different sources

3: Clarify business needs and solution scope to align the product with the company's goals and objectives

4: Identify the project team so that parties are appropriately represented, informed and involved

5: Use of appropriate techniques for prioritisation of requirements.

1. Step : Opportunity Definition

At this point, you will want to sit down and have a conversation with the primary stakeholder. Allow the stakeholder to tell their story so you can better empathise with their situation. This conversation will lead to writing an 'Issue Statement'. The basic problem statement format is as follows:

Problem W (target/root cause) affects X (users/stakeholders), the impact of which is Y (outcomes as a result of the problem), so a successful solution will be Z.

• Step : Data collection and analysis

There are several techniques and tools recommended by PMI that should be in your business analyst's toolkit. Some of these techniques for obtaining information from the stakeholder are:

• Brainstorming
• Document analysis
• Focus groups
• Interface analysis
• Interviews
• Workshops
• Reverse engineering
• Surveys

• Step : Develop project objectives

It is the duty of business analysts and Stakeholders to have clear, unambiguous, achievable and realistic objectives. Project objectives will also be critical for future project managers who will be tasked with project completion.

1. S.M.A.R.T

• Specific
• Measurable
• Attainable
• Results-focused
• Time-bound

2. OKR Approach

• Objectives
• Key results

3. BSQ

• Think BIG
• Act SMALL
• Move QUICK

4. ABC Targets

• Achievable
• Believable
• Controllable

5. FRAME Targets

• Few
• Realistic
• Agreed
• Measured
• Explicit

• Step : Stakeholder Identification

The continuation of step 3 will be the identification of other stakeholders. Stakeholders will often be responsible for parts of the business model that have a stake in the implementation of a successful solution and will need to be fully involved. Business analysts are also responsible for ensuring that stakeholders have a clear understanding of their requirements. An effective business analyst must ensure that stakeholders are informed and involved in the process. This level of involvement will be used by the project manager to develop the communication plan.

• Step : Prioritisation of Requirements

Paydaşları belirlediğinize ve listeye aldığınıza göre, üzerinde anlaşmaya varılan gereksinimler önceliklendirme açısından temel alınmalıdır. Gereksinimlerin öncelik listesi üzerinde anlaşmaya varılması, sorunsuz bir proje planı tasarımı ve uygulamasını büyük ölçüde geliştirecektir. Paydaşların tepkilerine ve sözsüz iletişimlerine dikkat eden zeki bir iş analisti, işin iç işleyişine dair çok değerli içgörülere sahip olacaktır. Paydaşların RACI şemasındaki (Sorumlu, Hesap Verebilir, Danışılan ve Bilgilendirilen) yerlerini tespit edebileceksiniz. Yine, RACI şemasının proje yöneticisinin proje başlangıcından önce sahip olması gereken bir başka çıktı olması gereklidir.

Bir sonraki içeriğimizde bilgi toplama ve hedef geliştirme tekniklerini inceleyeceğiz.