IIBA ECBA - Entry Certificate in Business Analysis (ECBA)

According to the BABOK® Guide v3, modeling of requirements can commence with elicitation results in any state. This means that even unconfirmed or preliminary elicitation results can be used to begin modeling, acknowledging that further elicitation may be necessary to refine and validate the models.

Reference from BABOK® Guide v3:

"Elicitation Results (any state): modelling can begin with any elicitation result and may lead to the need for more elicitation to clarify or expand upon requirements."

— BABOK® Guide v3, Section 7.1.3 Inputs

In the context of business analysis, the input status of requirements for undertaking requirement verification activities is ‘Specified and Modeled’. This means that the requirements have been detailed and documented, and models have been created to represent them. This status is crucial for verification activities because it ensures that the requirements are clearly understood and can be systematically evaluated against quality standards to ensure they are usable for their intended purpose.

The task that provides stakeholders with business analysis information after the collated results are confirmed is "Communicate Business Analysis Information", which falls under the Elicitation and Collaboration knowledge area. This task ensures that stakeholders have a shared understanding of the business analysis information, facilitating informed decision-making.

Reference from BABOK® Guide v3:

"Communicate Business Analysis Information: provides stakeholders with the business analysis information after the collated results are confirmed."

— BABOK® Guide v3, Section 4.4

The BABOK® Guide includes “Analytical Thinking and Problem Solving” as one of the core underlying competencies, and under this category fall the capabilities of learning, systems thinking, and decision making. These skills enable BAs to analyze complex information, make sound judgments, and approach issues holistically.

BABOK® Reference – Underlying Competencies (Chapter 9):

“Analytical Thinking and Problem Solving includes creativity, decision making, learning, problem solving, systems thinking.”

Process analysis is a business analysis technique that benefits from frameworks and methodologies like Six Sigma and Lean. These methodologies are focused on improving processes by eliminating waste and reducing variation. Six Sigma uses a set of quality management methods, including statistical tools, and creates a special infrastructure within the organization (champions, Black Belts, Green Belts, etc.) who are experts in these methods. Lean, on the other hand, is centered around providing value to the customer by optimizing processes, reducing waste, and improving flow. Both methodologies are process-centric and align with the goals of process analysis, which aims to understand and document the current process and design an improved future state.

Business analysis information packages are prepared to facilitate reviews and approvals. These packages compile essential information in a structured format, making it easier for stakeholders to review the content and provide feedback or approval. This ensures that all relevant information is considered and that decisions are made based on a comprehensive understanding of the issues, requirements, and proposed solutions. Effective preparation of these packages helps streamline the review process and supports better decision-making.

Good collaboration with stakeholders is characterized by regular, frequent, and bi-directional communication with all stakeholders involved in the initiative. This ensures that all voices are heard, and that information, ideas, and innovations are freely exchanged, contributing to a more inclusive and comprehensive understanding of the project requirements and objectives.

When a Business Analyst continually tracks risks such as delayed approvals, they are engaging in the activity of monitoring stakeholder engagement. This involves observing stakeholder participation levels, analyzing communication effectiveness, identifying risks to collaboration or approval timelines, and taking action to keep stakeholders engaged and responsive.

Tasks in this area include:

Tracking engagement levels

Identifying potential roadblocks (like delayed responses)

Mitigating communication breakdowns

BABOK® Reference:

Within the Elicitation and Collaboration knowledge area, “Monitor Stakeholder Engagement” is focused on ensuring stakeholders are actively involved and responsive throughout the project.