Strategy Analysis is a Business Analysis knowledge area that includes 4 main tasks.

As defined by The Business Analysis Body of Knowledge® (BABOK® Guide v3, IIBA®), the Strategy Analysis is an area of knowledge in Business Analysis. Business Analysts performs collaborative work with stakeholders to identify a need for strategic or tactical importance called the business needs and enable the enterprise to address that need and align the resulting strategy for the change higher and lower-level strategies.

Strategy in an organization is a general plan that defines its direction and decision-making about allocating its resources to pursue that strategy. It is usually defined, planned and executed by executive professionals and can involve different…


In a globalised world, communication is influenced by the most diverse factors, but mainly by cultural aspects. It is possible to observe specific principles that allow us to understand different cultures better and improve communication.

Culture is a complex and central concept in anthropology. It defines what is accepted in society and sets a norm for the way people behave, dress, speaks, etc. There are a diversity of cultures across nations and this can go beyond regional borders since it includes expressive forms like art, music, dance, ritual, religion, and technologies. I had never thought of cultural difference as a barrier to communication until I moved from Ceará, my home state in Brazil, to live in São Paulo. Brazil, the largest country in Latin America, divided into 26 states, has several regional cultures. For example…


The mindset is what precedes and drives values, principles and practices in Agile.

Agile is one of the perspectives in Business Analysis. The Agile Extension to BABOK® Guide (2017) defines the value of the Agile mindset for Business Analysts, however, the Agile mindset foundation comes from the Manifesto Agile (2001). In Agile, business analysts can use various techniques, processes and tools depending on the context to help deliver value; however, the best way to deliver what is expected in Agile is first to adopt an Agile mindset.

Remembering where it all started, in 2001, The Agile Manifesto stated the four values of agile delivery as:
• Individuals and interactions over processes and tools,
• Working…


Here are 10 steps to implement Requirements Management in your organization!

Requirements Management is an ongoing process throughout a project that involves documenting, analyzing, tracing, prioritizing, agreeing on requirements, controlling changes and continuous communication with stakeholders — and keep all these tasks in balance. Managing requirements is very important in business analysis and requirements engineering because Requirements Management can help ensure that requirements effectively meet the stakeholder's needs. The BABOK® Guide v3 defines a knowledge area called Requirements Life Cycle Management that describes the tasks to manage and maintain requirements. It includes trace, maintain, prioritise, assess and approve requirements guidelines (learn more in Managing Business Analysis Information into Requirements Lifecycle). However…


SMART is an evaluation technique that can be used when writing software requirements

SMART is a well-established criteria evaluation tool that originated in business management and extended to other studies fields, such as business analysis and requirements engineering. The first known mention was in 1981 when George T. Doran wrote the paper “There’s a S.M.A.R.T. way to write management’s goals and objectives”, published by the “Management Review”. It discussed the importance of objectives and the difficulty of setting them for management excellence. The author suggested that when it comes to writing effective objectives, ideally speaking; this should be SMART, a mnemonic acronym for “Specific”, “Measurable”, “Assignable”, “Realistic”, and “Time-related”. …


Modelling Requirements facilitates the communication of Business Analysis information with different audiences

Models are a way to represent the business requirement information descriptively and visually during the requirements analysis. Because the communication of business analysis information to stakeholders must be bi-directional, iterative and understandable, models can facilitate the communication with different groups of stakeholders in an initiative. When requirements rely purely on text, there are risks of ambiguity; and a model can make it easier to understand, help set expectations, and share a better and clear vision of the solution. The Requirements Analysis and Design Definition (RADD) knowledge area, by the Business Analysis Body of Knowledge® (BABOK® Guide v3, IIBA®), defines the…


RADD tasks are essential for Business Analysts to develop requirements and solutions that represent value to stakeholders and align with business objectives.

The Requirements Analysis and Design Definition (a.k.a. RADD) is a knowledge area prescribed in the Business Analysis Body of Knowledge® (BABOK® Guide v3) by the International Institute of Business Analysis (IIBA®). RADD knowledge area covers complementary activities from the initial concept, passing through the business need exploration, to the recommended solution.

RADD defines tasks that business analysts need to structure and organize requirements discovered during elicitation activities; specify and model requirements and designs; validate and verify information; identify solution options; and estimate its potential value. The five key Business Analysis tasks within RADD are designed to format requirements, establish solution…


Business analysts must establish a clear communication
with stakeholders and solve conflicts to obtain the approval of the business requirement.

Sometimes the work involved in the requirements approval process requires a huge effort, especially because this simple process can become complex when multiple stakeholders collaborate and are responsible for approval. For this, the Business Analyst needs to establish clear communication with stakeholders to obtain agreement on and approval of requirements and designs.

The BABOK® Guide version 3, in “Requirements Life Cycle Management”, presents the following elements to obtain requirement approval:


The many project areas are interconnected, and any requirement change in one of these areas must be assessed by Business Analyst.

Changes are common in requirements and Business Analysts need to be in alert for whatever change happens during all requirements life cycle. This includes assessing the impact of requirements changes on a project, cooperating with impact analysis and impact solution. These are the main elements to be considered when assessing requirements changes, as defined by the BABOK® Guide version 3, at “Requirements Life Cycle Management”:

Assessment Formality

The Business Analyst needs to define what is the formality of the change assessment process, and it can be impacted by factors such as:

  • Available information — Sometimes the change formality needs to…


Agile, BI, IT, BA and BPM: understand these five Business Analysis perspectives.

Business Analysis is extensive and varies across many disciplines or scenarios. The BABOK Guide v3 nominates it perspectives and highlights five ones that nowadays reflect the most common views of Business Analysis: Agile, Business Intelligence (BI), Information Technology (IT), Business Architecture (BA), Business Process Management (BPM). Understand more about these five perspectives below.

Agile Perspective

Agile comprises the approach used to discover requirements and develop solutions through the collaborative effort of self-organized, cross-functional teams and business stakeholders. It recommends adaptive planning, evolutionary development, early delivery and continuous improvement and encourages flexible responses to change.

As explained by The BABOK Guide v3, because…

Erivan Ramos

Business Analysis & Requirements Engineering enthusiast. Information Systems & Software Engineering specialist. MBA in PM & HR. CBAP®, PMP®, CSM®, ITIL®& COBIT®

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store