A dependent task is a task that belongs to a certain work entity (project or process) and relates to

other tasks of the same work entity in a way that ensures their interconnection and common

direction. A dependent task can be a sub-task of a larger activity. It causes an effect to other tasks

and sub-tasks. A dependent task cannot start until other tasks are completed, because it relies on the

output, input, or resource of those tasks. A dependent task is also referred to as a logical

relationship, because it shows the logical order or sequence of the tasks1. An analysis task is a task

that involves examining, evaluating, or interpreting data, information, or requirements. An analysis

task can be a dependent task or an independent task, depending on whether it requires the

completion of other tasks or not. An analysis task can also be a predecessor task or a successor task,

depending on whether it precedes or follows other tasks. An analysis task is a common type of task

in business analysis2. A predecessor task is a task that comes before another task in a sequence or a

network of tasks. A predecessor task can be a dependent task or an independent task, depending on

whether it affects or is affected by other tasks or not. A predecessor task can also be an analysis task

or a different type of task, depending on its nature and purpose. A predecessor task can start before

other tasks are completed, as long as it does not depend on them3. An independent task is a task

that does not belong to a certain work entity (project or process) or does not relate to other tasks of

the same work entity. An independent task can be a standalone activity or a part of a larger activity.

It does not cause an effect to other tasks or sub-tasks. An independent task can start at any time,

regardless of the completion of other tasks, because it does not rely on the output, input, or resource

of those tasks. An independent task is also referred to as a discrete task, because it is separate and

distinct from other tasks1. Reference:

CBAP® Handbook

Predecessor Task - iiba.org

Dependent Task - iiba.org

A solution approach is a description of the proposed method for delivering a solution that meets the

business need. It is one of the outputs of the enterprise analysis tasks, along with business need,

capability gaps, solution scope, and business case. A solution approach defines the type, nature, and

complexity of the solution, and provides a high-level view of how the solution will be implemented.

It also identifies the major components, features, and functions of the solution, as well as the key

stakeholders, risks, assumptions, and constraints. A solution approach helps to evaluate the

feasibility and viability of different solution options and compare them with the business need and

expected benefits. Reference:

IIBA BABOK Guide v3, p. 30, 176, 264

An Overview of Enterprise Analysis - Modern Analyst

How Do You Know When You Are Doing Enterprise Analysis

Benchmarking is a technique for comparing the performance or practices of an organization with

those of other organizations, usually considered to be the best in the field. It is not a technique for

identifying the solution approach, which is the process of defining the most feasible and appropriate

way to implement a change that addresses a business need. The other techniques are useful for

identifying the solution approach. Decision analysis helps to evaluate multiple options and select the

best one based on criteria and trade-offs. Risk analysis helps to identify and assess the uncertainties

and potential impacts of the solution approach. Brainstorming helps to generate and explore diverse

ideas for the solution approach. Reference:

BABOK® Guide v3, section 10.17 Benchmarking, section 10.18 Brainstorming, section 10.25 Decision

Analysis, section 10.33 Risk Analysis and Management, section 11.2 Define Solution Approach

CBAP® Handbook, section 5. Review the Exam Blueprint

Tips for Earning a Business Analysis Certification, section 4. Leverage a variety of study resources

A test plan is a document that describes the scope, objectives, strategy, and activities of testing a

software product or system. A test plan is mandatory in most software development projects

because it ensures that the software meets the quality standards and requirements of the

stakeholders. A test plan also helps to identify and mitigate the risks, defects, and issues that may

affect the software functionality, performance, usability, and security. A test plan is different from a

communication management plan, which is a document that describes how the project information

will be communicated to the stakeholders. A test plan is also different from a disaster recovery plan,

which is a document that describes how the project will resume its operations in the event of a

disaster or emergency. A test plan is not a procurement plan, which is a document that describes

how the project will acquire the goods and services needed from external sources. Reference:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 9: Solution Assessment

and Validation, page 329-330.

How to write a software requirement document (with template), paragraph 6

These testing methods should be mandatory for any software, paragraph 1

Software Testing Plan - Tutorialspoint, paragraph 1

A requirements trace matrix (RTM) is a tool that helps to ensure that the project’s scope,

requirements, and deliverables remain consistent and aligned throughout the project lifecycle. It

traces the requirements from their origin to their fulfillment by linking them to other project

artifacts, such as design documents, test cases, and solution components. An RTM can also be used

to verify that all requirements are met and to identify changes to the scope when they occur. An RTM

is especially useful for smaller projects where there are few requirements, as it can help to track the

progress and status of each requirement and avoid scope creep. A requirements trace matrix is not

the same as a roles and responsibility matrix (A), a RACI matrix (B), or a coverage matrix ©, which

are different types of matrices that serve different purposes in project management. Reference:

IIBA BABOK Guide v3, p. 30, 176, 264

Requirements Traceability Matrix – RTM - Project-Management.com

CBAP/CCBA/ECBA Certification Practice Test | MindsMapped,

The waterfall software development life cycle is a methodology that divides the project into phases,

and the project manager focuses on control of time, cost, and scope. The waterfall model is a linear

and sequential approach that follows a predefined set of steps from the initiation to the closure of

the project. The waterfall model assumes that the requirements, scope, and design of the project are

clear and stable, and that each phase can be completed before moving to the next one. The waterfall

model helps to ensure that the project deliverables meet the quality standards and specifications,

and that the project is completed within the budget and schedule12. The spiral software

development life cycle is a methodology that combines the iterative and incremental approach with

the risk management and prototyping techniques. The spiral model is a cyclical and evolutionary

approach that follows a series of loops or iterations from the planning to the deployment of the

project. The spiral model assumes that the requirements, scope, and design of the project are

dynamic and complex, and that each iteration can be refined and improved based on the feedback

and learning from the previous ones. The spiral model helps to identify and mitigate the risks and

uncertainties of the project, and to deliver a functional and adaptable product13. The agile software

development life cycle is a methodology that emphasizes the collaboration, communication, and

flexibility among the project stakeholders. The agile model is an adaptive and iterative approach that

follows a series of short and frequent cycles or sprints from the conception to the delivery of the

project. The agile model assumes that the requirements, scope, and design of the project are

emergent and changing, and that each sprint can deliver a working and valuable product

increment. The agile model helps to respond to the changes and feedback of the project, and to

maximize the customer satisfaction and value14. The incremental software development life cycle is

a methodology that breaks down the project into smaller and manageable chunks or modules. The

incremental model is a progressive and modular approach that follows a series of steps from the

analysis to the implementation of each module of the project. The incremental model assumes that

the requirements, scope, and design of the project are partially known and defined, and that each

module can be developed and delivered independently. The incremental model helps to reduce the

complexity and risk of the project, and to provide a gradual and continuous delivery of the

product15. Reference:

CBAP® Handbook

Waterfall Model - iiba.org

Spiral Model - iiba.org

Agile Model - iiba.org

Incremental Model - iiba.org

Requirements are dynamic and may change throughout the project life cycle due to various factors,

such as changing stakeholder needs, new business opportunities, feedback from testing, or

regulatory changes. Business analysis planning and monitoring involves defining the process for

managing changes to requirements, including identifying the roles and responsibilities, the approval

levels, the change control tools, and the communication methods. The business analyst should be

prepared to handle changes to requirements at any time and follow the established change control

process. Reference:

CBAP® Handbook, page 6, section 2.4. Review the Exam Blueprint

BABOK® Guide, page 29, section 2.4. Manage Business Analysis Performance

Tips for Earning a Business Analysis Certification, point 3. Understand the BABOK® Guide

Stakeholders are individuals or groups who have an interest in the outcome of a project and can

influence its success. Stakeholders can be classified into different categories based on their roles,

responsibilities, and perspectives. One common way to categorize stakeholders is by using the RACI

matrix, which stands for Responsible, Accountable, Consulted, and Informed. According to this

matrix, the following stakeholders participate in the prioritization of requirements:

Project team: Responsible for delivering the solution that meets the requirements. They are directly

involved in the prioritization process and provide input on the feasibility, effort, and risk of each

requirement.

Domain subject matter expert: Consulted for their expertise and knowledge of the business domain

and the needs of the end users. They provide input on the importance, value, and urgency of each

requirement.

Project manager: Accountable for the overall success of the project and the alignment of the

requirements with the project scope, schedule, and budget. They facilitate the prioritization process

and ensure that the stakeholders reach a consensus on the priority levels.

The implementation subject matter expert is not a stakeholder who participates in the prioritization

of requirements. They are Informed of the prioritized requirements and the rationale behind them,

but they do not provide input or influence the prioritization process. They are responsible for

implementing the solution according to the requirements and ensuring that it meets the quality

standards and specifications. Reference:

IIBA BABOK Guide v3, p. 30, 176, 264

Five Requirements Prioritization Methods - Business Analyst Articles …

What Is Requirements Prioritization? Definition & Examples - airfocus

Business analysts : How to prioritize requirements - Adaptive US

[5 Popular Requirements Prioritisation Techniques]

Before making a presentation about the requirements for a large software development project,

Gary should determine an appropriate format for the presentation. This means he should consider

the following factors:

The audience: Who are the stakeholders that will attend the presentation? What are their roles,

interests, and expectations? How familiar are they with the project and the requirements? How

much detail do they need to understand the requirements?

The purpose: What is the goal of the presentation? Is it to inform, persuade, or seek feedback from

the stakeholders? What are the key messages and takeaways that Gary wants to convey?

The time: How much time does Gary have to present the requirements? How can he allocate the

time effectively to cover the most important and relevant aspects of the requirements?

The tools: What tools and resources does Gary have to create and deliver the presentation? Does he

have access to a projector, a laptop, a microphone, or a whiteboard? What software or applications

does he need to use to create the presentation slides or documents?

The style: How can Gary make the presentation engaging, clear, and professional? What visual aids,

diagrams, charts, or examples can he use to illustrate the requirements? How can he use colors,

fonts, images, and animations to enhance the presentation? How can he structure the presentation

to have a logical flow and a strong introduction and conclusion?

By determining an appropriate format for the presentation, Gary can ensure that he communicates

the requirements effectively and efficiently to the stakeholders, and that he addresses their needs

and concerns.

Reference:

How to Make Interesting Presentations for Software Projects, paragraphs 1-3

How To Write The Software Development Project Brief, steps 1-7

Complete Guide to Software Development Requirements, paragraphs 1-2

Milestone funding is an approach where the project is funded for enough capital to reach the next

milestone, which is a predefined point in the project where some deliverables are completed or

some criteria are met. Milestone funding helps to reduce the risk of investing too much money in a

project that may not deliver the expected value or benefits. It also helps to monitor the progress and

performance of the project and ensure that the project is aligned with the business objectives and

stakeholder expectations. Milestone funding is a common practice in agile projects, where the

project is divided into short iterations that deliver incremental value and feedback. Reference: CBAP

/ CCBA Certified Business Analysis Study Guide, chapter 5, page 229; CBAP (Certified Business

Analysis Professional): 230+ Exam Practice Questions with Detail Explanations and Case Study Based

Questions,