A 2 Z Terminologies

Business Analysts

a
Criteria associated with requirements, products, or the delivery cycle
acceptance criteria
that must be met in order to achieve stakeholder acceptance.
A human, device, or system that plays some specified role in
actor (business analysis)
interacting with a solution.
An approach where the solution evolves based on a cycle of learning
adaptive approach and discovery, with feedback loops which encourage making decisions
as late as possible.
A standard on the practice of business analysis in an agile context.
Agile Extension to
The Agile Extension to the BABOK® Guide version 1 was published in
the BABOK® Guide
2013 by IIBA®, in partnership with the Agile Alliance.
allocation Requirement – Resource allocation
The design, structure, and behaviour of the current and future states of
a structure in terms of its components, and the interaction between
architecture
those components. See also business architecture, enterprise
architecture, and requirements architecture.
Any solution-relevant object that is created as part of business analysis
artifact (business analysis)
efforts.
An influencing factor that is believed to be true but has not been
assumption confirmed to be accurate, or that could be true now but may not be in
the future.
b
A business rule that places an obligation (or prohibition) on conduct,
action, practice, or procedure; a business rule whose purpose is to
behavioural business rule
shape (govern) day-to-day business activity. Also known as operative
rule.
A comparison of a decision, process, service, or system's cost, time,
benchmarking quality, or other metrics to those of leading peers to identify
opportunities for improvement.
The aggregated knowledge and generally accepted practices on a
body of knowledge
topic.
BPM Business Process Management
A team activity that seeks to produce a broad or diverse set of options
brainstorming
through the rapid and uncritical generation of ideas.

An economic system where any commercial, industrial, or professional

business (business world)
activity is performed for profit.
The practice of enabling change in the context of an enterprise by
business analysis defining needs and recommending solutions that deliver value to
stakeholders.

Lomesh Detroja | Agile Analyst

 Any kind of information at any level of detail that is used as an input to
business analysis information
business analysis work, or as an output of business analysis work.
A document, presentation, or other collection of text, matrices,
business analysis package
diagrams and models, representing business analysis information.
Any person who performs business analysis, no matter their job title or
business analyst
organizational role.
The set of processes, rules, guidelines, heuristics, and activities that
business analysis approach
are used to perform business analysis in a specific context.
A description of the types of communication the business analyst will
business analysis communication perform during business analysis, the recipients of those
plan communications, and the form and frequency of those
communications.
The scope of activities a business analyst is engaged in during the life
business analysis effort
cycle of an initiative.
A description of the planned activities the business analyst will execute
business analysis plan in order to perform the business analysis work involved in a specific
initiative.
The design, structure, and behaviour of the current and future states of
an enterprise to provide a common understanding of the organization.
business architecture
It is used to align the enterprise’s strategic objectives and tactical
demands.
A justification for a course of action based on the benefits to be
business case realized by using the proposed solution, as compared to the cost,
effort, and other considerations to acquire and live with that solution.
A decision that can be made based on strategy, executive judgment,
business decision consensus, and business rules, and that is generally made in response
to events or at defined points in a business process.
business domain Domain
A state or condition that an organization is seeking to establish and
business goal
maintain, usually expressed qualitatively rather than quantitatively.
A problem or opportunity of strategic or tactical importance to be
business need
addressed.
An objective, measurable result to indicate that a business goal has
business objective
been achieved.
A non-practicable directive that controls and influences the actions of
business policy
an enterprise.
An issue of strategic or tactical importance preventing an enterprise or
business problem
organization from achieving its goals.
An end-to-end set of activities which collectively responds to an event,
and transforms information, materials, and other resources into outputs
business process
that deliver value directly to the customers of the process. It may be
internal to an organization, or it may span several organizations.
business process management A management discipline that determines how manual and automated
(BPM) processes are created, modified, cancelled, and governed.
Rethinking and redesigning business processes to generate
business process re-engineering
improvements in performance measures.
A representation of goals, objectives and outcomes that describe why
business requirement
a change has been initiated and how success will be assessed.

Lomesh Detroja | Agile Analyst

 A specific, practicable, testable directive that is under the control of the
business rule business and that serves as a criterion for guiding behaviour, shaping
judgments, or making decisions.
c
The set of activities the enterprise performs, the knowledge it has, the
capability products and services it provides, the functions it supports, and the
methods it uses to make decisions.
cause-and-effect diagram: Route Cause Analysis
change The act of transformation in response to a need.
change agent One who is a catalyst for change.
Controlling changes to requirements and designs so that the impact of
change control requested changes is understood and agreed-to before the changes
are made.
Planned activities, tools, and techniques to address the human side of
change management change during a change initiative, primarily addressing the needs of
the people who will be most affected by the change.
A plan to move from the current state to the future state to achieve the
change strategy
desired business objectives.
A cross-functional group of individuals who are mandated to implement
a change. This group may be comprised of product owners, business
change team analysts, developers, project managers, implementation subject matter
experts (SMEs), or any other individual with the relevant set of skills
and competencies required to implement the change.
A standard set of quality elements that reviewers use for requirements
checklist (business analysis)
verification.
The act of two or more people working together towards a common
collaboration
goal.
A prepackaged solution available in the marketplace which address all
or most of the common needs of a large group of buyers of those
commercial off-the-shelf (COTS)
solutions. A commercial off-the-shelf solution may require some
configuration to meet the specific needs of the enterprise.
A structured assessment which captures the key characteristics of an
competitive analysis industry to predict the long-term profitability prospects and to
determine the practices of the most significant competitors.
A uniquely identifiable element of a larger whole that fulfills a clear
component
function.
An analysis model that develops the meaning of core concepts for a
concept model problem domain, defines their collective structure, and specifies the
appropriate vocabulary needed to communicate about it consistently.
An influencing factor that cannot be changed, and that places a limit or
constraint (business analysis)
restriction on a possible solution or solution option.
The circumstances that influence, are influenced by, and provide
context
understanding of the change.
One of six ideas that are fundamental to the practice of business
core concept (business analysis)
analysis: Change, Need, Solution, Context, Stakeholder, and Value.

Lomesh Detroja | Agile Analyst

 An analysis which compares and quantifies the financial and non-
cost-benefit analysis financial costs of making a change or implementing a solution
compared to the benefits gained.
COTS Commercial Off the Shelf
A two-dimensional matrix showing which user roles have permission to
access specific information entities, and to create new records in those
create, read, update, and delete entities, view the data in existing records, update or modify the data in
matrix (CRUD matrix) existing records, or delete existing records. The same type of matrix
can be used to show which processes, instead of users, have the
create, read, update and delete rights.
CRUD matrix Create, Read, Update, Delete
A stakeholder who uses or may use products or services produced by
customer the enterprise and may have contractual or moral rights that the
enterprise is obliged to meet.
d
An approach to decision making that examines and models the
decision analysis possible consequences of different decisions, and assists in making an
optimal decision under conditions of uncertainty.
A technique that subdivides a problem into its component parts in
decomposition
order to facilitate analysis and understanding of those components.
A deficiency in a product or service that reduces its quality or varies
defect
from a desired attribute, state, or functionality.
A rule that indicates something is necessarily true (or untrue); a rule
definitional business rule that is intended as a definitional criterion for concepts, knowledge, or
information. Also known as a structural rule.
Any unique and verifiable work product or service that a party has
deliverable
agreed to deliver.
design A usable representation of a solution.
document analysis (business An examination of the documentation of an existing system in order to
analysis) elicit requirements.
The sphere of knowledge that defines a set of common requirements,
domain terminology, and functionality for any program or initiative solving a
problem.
A stakeholder with in-depth knowledge of a topic relevant to the
domain subject matter expert
business need or solution scope.
DSDM Dynamic System Development Method
A project delivery framework which focuses on fixing cost, quality, and
dynamic systems development
time at the beginning while contingency is managed by varying the
method (DSDM)
features to be delivered.
e
Iterative derivation and extraction of information from stakeholders or
elicitation
other sources.
end user A stakeholder who directly interacts with the solution.
A system of one or more organizations and the solutions they use to
enterprise
pursue a shared set of common goals.

Lomesh Detroja | Agile Analyst

 A description of the business processes, information technology,
enterprise architecture people, operations, information, and projects of an enterprise and the
relationships between them.
An assessment that describes the enterprise is prepared to accept the
enterprise readiness assessment
change associated with a solution and is able to use it effectively.
A graphical representation of the entities relevant to a chosen problem
entity-relationship diagram
domain and the relationships between them.
A quantitative assessment of a planned outcome, resource
estimate requirements, and schedule where uncertainties and unknowns are
systematically factored into the assessment.
The systematic and objective assessment of a solution to determine its
evaluation status and efficacy in meeting objectives over time, and to identify
ways to improve the solution to better meet objectives.
An occurrence or incident to which an organizational unit, system, or
event (business analysis)
process must respond.
A prototype that is continuously modified and updated in response to
evolutionary prototype
feedback from stakeholders.
Elicitation performed in a controlled manner to make a discovery, test a
experiment
hypothesis, or demonstrate a known fact.
An interaction that is outside the proposed solution. It can be another
external interface hardware system, software system, or a human interaction with which
the proposed solution will interact.
f
The art of leading and encouraging people through systematic efforts
facilitation toward agreed-upon objectives in a manner that enhances
involvement, collaboration, productivity, and synergy.
An evaluation of proposed alternatives to determine if they are
technically, organizationally, and economically possible within the
feasibility study
constraints of the enterprise, and whether they will deliver the desired
benefits to the enterprise.
A distinguishing characteristic of a solution that implements a cohesive
feature
set of requirements and which delivers value for a set of stakeholders.
A diagramming technique used in root cause analysis to identify
fishbone diagram underlying causes of an observed problem, and the relationships that
exist between those causes. Also known as an Ishikawa or cause-and-
effect diagram.
A group formed to to elicit ideas and attitudes about a specific product,
service, or opportunity in an interactive group environment. The
focus group
participants share their impressions, preferences, and needs, guided
by a moderator.
A graphical method for depicting the forces that support and oppose a
change. Involves identifying the forces, depicting them on opposite
force field analysis
sides of a line (supporting and opposing forces) and then estimating
the strength of each set of forces.
A capability that a solution must have in terms of the behaviour and
functional requirement
information the solution will manage.
g

Lomesh Detroja | Agile Analyst

 A comparison of the current state and desired future state of an
gap analysis
enterprise in order to identify differences that need to be addressed.
goal Business Goal – Sprint Goal
A process by which appropriate decision makers use relevant
governance process (change) information to make decisions regarding a change or solution,
including the means for obtaining approvals and priorities.
guideline (business analysis) An instruction or description on why or how to undertake a task.
h
A prototype that is used to explore requirements and designs at one
horizontal prototype level of a proposed solution, such as the customer-facing view or the
interface to another organization.
i
An assessment of the effects a proposed change will have on a
impact analysis
stakeholder or stakeholder group, project, or system.
implementation subject matter A stakeholder who has specialized knowledge regarding the
expert implementation of one or more solution components.
A specific numerical measurement that indicates progress toward
indicator
achieving an impact, output, activity, or input. See also metric.
A specific project, program, or action taken to solve some business
initiative
problem(s) or achieve some specific change objective(s).
Information consumed or transformed to produce an output. An input is
input (business analysis)
the information necessary for a task to begin.
A formal review of a work product by qualified individuals that follows a
inspection predefined process, and uses predefined criteria, for defect
identification and removal.
A shared boundary between any two persons and/or systems through
interface
which information is communicated.
interoperability Ability of systems to communicate by exchanging data or services.
Eliciting information from a person or group of people in an informal or
interview formal setting by asking relevant questions and recording the
responses.
Ishikawa diagram Fishbone Diagram
A single instance of progressive cycles of analysis, development,
iteration (business analysis)
testing, or execution.
k
knowledge area (business An area of expertise that includes several specific business analysis
analysis) tasks.
l
A process improvement technique used to learn about and improve on
a process or project. A lessons learned session involves a special
lessons learned process meeting in which the team explores what worked, what didn't work,
what could be learned from the just-completed iteration, and how to
adapt processes and techniques before continuing or starting anew.
A series of changes an item or object undergoes from inception to
life cycle
retirement

Lomesh Detroja | Agile Analyst

m
A textual form of modelling used to represent information that can be
matrix
categorized, cross-referenced, and represented in a table format.
A description of data to help understand how to use that data, either in
metadata terms of the structure and specification of the data, or the description
of a specific instance of an object.
A body of methods, techniques, procedures, working concepts, and
methodology
rules used to solve a problem.
A quantifiable level of an indicator measured at a specified point in
metric
time.
A formal declaration of values and goals that expresses the core
mission statement
purpose of the enterprise.
A representation and simplification of reality developed to convey
model information to a specific audience to support analysis, communication,
and understanding.
Collecting data on a continuous basis from a solution in order to
monitoring determine how well a solution is implemented compared to expected
results.
n
need A problem or opportunity to be addressed.
A type of requirement that describes the performance or quality
attributes a solution must meet. Non-functional requirements are
non-functional requirement
usually measurable and act as constraints on the design of a solution
as a whole.
o
objective Business Objectives
Studying and analyzing one or more stakeholders in their work
observation (business analysis)
environment in order to elicit requirements.
OLAP Online Analytical Processing – Client Portals See
online analytical processing A business intelligence approach that allows users to analyze large
(OLAP) amounts of data from different points of view.
A stakeholder who is responsible for the day-to-day management and
operational support
maintenance of a system or product.
operative rule Behavioural Rule
An autonomous group of people under the management of a single
organization
individual or board, that works towards common goals and objectives.
A function inside the enterprise, made up of components such as
organizational capability processes, technologies, and information and used by organizations to
achieve their goals.
organizational change
Change Management
management
The analysis technique used to describe roles, responsibilities and
Organizational modelling
reporting structures that exist within an enterprise.
Any recognized association of people within an organization or
organizational unit
enterprise.

Lomesh Detroja | Agile Analyst

p
A formal or informal review of a work product to identify errors or
peer review
opportunities for improvement.
A detailed scheme for doing or achieving something usually comprising
a set of events, dependencies, expected sequence, schedule, results
plan
or outcomes, materials and resources needed, and how stakeholders
need to be involved.
policy Business Policy
An approach where planning and baselines are established early in the
predictive approach
life cycle of the initiative in order to maximize control and minimize risk.
Determining the relative importance of a set of items in order to
prioritization
determine the order in which they will be addressed.
A set of activities designed to accomplish a specific objective by taking
process
one or more defined inputs and turning them into defined outputs.
A set of diagrams and supporting information about a process and
process model factors that could influence the process. Some process models are
used to simulate the performance of the process.
product (business analysis) A solution or component of a solution that is the result of an initiative.
A set of user stories, requirements, or features that have been
product backlog identified as candidates for potential implementation, prioritized, and
estimated.
product scope Solution Scope
A brief statement or paragraph that describes the goals of the solution
product vision statement
and how it supports the strategy of the organization or enterprise.
A temporary endeavour undertaken to create a unique product,
project
service, or result.
A stakeholder who is responsible for managing the work required to
deliver a solution that meets a business need, and for ensuring that the
project manager
project's objectives are met while balancing the project constraints,
including scope, budget, schedule, resources, quality, and risk.
The work that must be performed to deliver a product, service, or result
project scope
with the specified features and functions.
A model created to validate the design of a solution without modelling
proof of concept the appearance, materials used in the creation of work, or processes
and workflows ultimately used by the stakeholders.
A partial or simulated approximation of the solution for the purpose of
prototype
eliciting or verifying requirements with stakeholders.
q
quality The degree to which a set of inherent characteristics fulfills needs.
A set of activities performed to ensure that a process will deliver
quality assurance
products that meet an appropriate level of quality.
quality attributes A set of measures used to judge the overall quality of a system.
A set of defined questions, with a choice of answers, used to collect
questionnaire
information from respondents.
r
RACI matrix Responsible, Accountable, Consulted, Informed

Lomesh Detroja | Agile Analyst

 A stakeholder from outside the organization who is responsible for the
regulator
definition and enforcement of standards.
A real or virtual facility where all information on a specific topic is
repository
stored and is available for retrieval.
A formal elicitation method intended to collect information regarding a
request for information (RFI) vendor's capabilities or any other information relevant to a potential
upcoming procurement.
A requirements document issued when an organization is seeking a
formal proposal from vendors. An RFP typically requires that the
request for proposal (RFP)
proposals be submitted following a specific process and using sealed
bids which will be evaluated against a formal evaluation methodology.
A procurement method of soliciting price and solution options from
request for quote (RFQ)
vendors.
An open invitation to vendors to submit a proposal for goods or
request for tender (RFT)
services.
requirement A usable representation of a need.
A characteristic or property of a requirement used to assist with
requirements attribute
requirements management.
The process of assigning requirements to be implemented by specific
requirements allocation
solution components.
The requirements of an initiative and the interrelationships between
requirements architecture
these requirements.
A business analysis artifact containing information about requirements
requirements artifact
such as a diagram, matrix, document or model.
A problem or error in a requirement. Defects may occur because a
requirements defect requirement is poor quality (see requirements verification) or because
it does not describe a need that, if met, would provide value to
stakeholders (see requirements validation).
requirements document Requirements
requirements The stages through which a requirement progresses from inception to
life cycle retirement.
Planning, executing, monitoring, and controlling any or all of the work
associated with requirements elicitation and collaboration,
requirements management
requirements analysis and design, and requirements life cycle
management.
A subset of the business analysis plan for a specific change initiative,
describing specific tools, activities, and roles and responsibilities that
requirements management plan
will be used on the initiative to manage the requirements. See
business analysis plan.
Special-purpose software that provides support for any combination of
the following capabilities: elicitation and collaboration, requirements
requirements management tool modelling and/or specification, requirements traceability, versioning
and baselining, attribute definition for tracking and monitoring,
document generation, and requirements change control.
An abstract (usually graphical) representation of some aspect of the
requirements model
current or future state.

Lomesh Detroja | Agile Analyst

 A specialized form of a business analysis package primarily concerned
requirements
with requirements. A requirements package may represent a baseline
package
of a collection of requirements.
The ability for tracking the relationships between sets of requirements
and designs from the original stakeholder need to the actual
implemented solution. Traceability supports change control by
requirements traceability
ensuring that the source of a requirement or design can be identified
and other related requirements and designs potentially affected by a
change are known.
Work done to evaluate requirements to ensure they support the
requirements validation
delivery of the expected benefits and are within the solution scope.
Work done to evaluate requirements to ensure they are defined
correctly and are at an acceptable level of quality. It ensures the
requirements verification requirements are sufficiently defined and structured so that the solution
development team can use them in the design, development, and
implementation of the solution.
A structured meeting in which a carefully selected group of
requirements workshop stakeholders collaborate to define and/or refine requirements under the
guidance of a skilled neutral facilitator.
The risk remaining after action has been taken or plans have been put
residual risk
in place to deal with the original risk.
A tool used to identify the responsibilities of roles or team members
responsible, accountable, and the activities or deliverables in which they will participate, by being
consulted, and informed matrix responsible (doing the work), accountable (approving the results),
(RACI matrix) consulted (providing input) or informed of the completed item after it
has been completed.
retrospective Lessons Learned
return on investment (ROI)
A measure of the profitability of a project or investment.
(business analysis)
RFI Request for Information
RFP Request for Proposal
RFQ Request for Quote
RFT Request for Tender
The effect of uncertainty on the value of a change, a solution, or the
risk (business analysis)
enterprise.
risk assessment: Identifying,
analyzing and evaluating risks. Return on Investment
ROI
The cause of a problem having no deeper cause, usually one of
root cause
several possible causes.
A structured examination of an identified problem to understand the
root cause analysis
underlying causes.
s
scope The boundaries of control, change, a solution, or a need.
scope model A model that defines the boundaries of a business domain or solution.
An actor external to the system under design that supports the
secondary actor
execution of a use case.

Lomesh Detroja | Agile Analyst

 A type of diagram that shows objects participating in interactions and
sequence diagram
the messages exchanged between them.
The performance of any duties or work for a stakeholder, from the
service (business analysis)
perspective of the stakeholder.
SIPOC See suppliers, inputs, process, outputs and customers.

solution A specific way of satisfying one or more needs in a context.

A sub-part of a solution that can be people, infrastructure, hardware,
solution component software, equipment, facilities, and process assets or any combination
of these sub-parts.
solution option: One possible way to satisfy one or more needs in a context.
A capability or quality of a solution that meets the stakeholder
requirements. Solution requirements can be divided into two sub-
solution requirement
categories: functional requirements and non-functional requirements or
quality of service requirements.
The stages through which a solution progresses from inception to
solution life cycle
retirement.
The set of capabilities a solution must deliver in order to meet the
solution scope
business need.
SOW Statement of Work
A stakeholder who is responsible for initiating the effort to define a
business need and develop a solution that meets that need. They
sponsor
authorize the work to be performed and control the budget and scope
for the initiative.
A group or individual with a relationship to the change, the need, or the
stakeholder
solution.
Identifying and analyzing the stakeholders who may be impacted by
stakeholder analysis the change and assess their impact, participation, and needs
throughout the business analysis activities.
A catalogue of the stakeholders affected by a change, business need,
stakeholder list or proposed solution, and a description of their attributes and
characteristics related to their involvement in the initiative.
stakeholder proxy (business The role a business analyst takes when representing the needs of a
analyst) stakeholder or stakeholder group.
A description of the needs of a particular stakeholder or class of
stakeholders that must be met in order to achieve the business
stakeholder requirement
requirements. They may serve as a bridge between business
requirements and the various categories of solution requirements.
state diagram An analysis model showing the life cycle of a data entity or class.
A requirement articulated by a stakeholder that has not been analyzed,
stated requirement verified, or validated. Stated requirements frequently reflect the desires
of a stakeholder rather than the actual need.
A written description of the services or tasks that are required to be
statement of work (SOW)
performed.
A description of the chosen approach to apply the capabilities of an
strategy
enterprise in order to reach a desired set of goals or objectives.

Lomesh Detroja | Agile Analyst

strengths, weaknesses,
An analysis model used to understand influencing factors and how
opportunities, and threats analysis
they may affect an initiative. Also known as SWOT analysis.
(SWOT)
structural rule Business Rules
subject matter expert (SME) Subject Matter or Domain Expert.
A stakeholder outside the boundary of a given organization or
organizational unit who provides products or services to the
supplier
organization and may have contractual or moral rights and obligations
that must be considered.
A tool used to describe relevant high-level elements of a process. May
suppliers, inputs, process, outputs,
be used in conjunction with process mapping and ‘in/out of scope’
and customers (SIPOC)
tools, to provide additional detail.
Collecting and measuring the opinions or experiences of a group of
survey
people through a series of questions.
A horizontal or vertical section of a process diagram that shows which
swimlane
activities are performed by a particular actor or role.
SWOT analysis Strengths, Weakness, Opportunities, Threats
A set of interdependent components that interact in various ways to
system
produce a set of desired outcomes.
t
A discrete piece of work that may be performed formally or informally
task (business analysis)
as part of business analysis.
A manner, method, or style for conducting a business analysis task or
technique
for shaping its output.
An event based on time that can trigger the initiation of a process,
temporal event
evaluation of business rules, or some other response.
An individual responsible for determining how to verify that the solution
tester meets the requirements defined by the business analyst, and
conducting the verification process.
A prototype used to quickly uncover and clarify requirements or
throw-away prototype designs using simple tools, sometimes just paper and pencil. It is
intended to be discarded when the final system has been developed.
An agreed-upon period of time in which an activity is conducted or a
time-box
defined deliverable is intended to be produced.
traceability Requirement Traceability
A requirement that describes the capabilities the solution must have
and the conditions the solution must meet to facilitate transition from
transition
the current state to the future state, but which are not needed once the
requirement
change is complete. They are differentiated from other requirements
types because they are of a temporary nature.
u
UAT User Acceptance Test
UML Unified Modelling Language
A notation specified by the Object Management Group for describing
unified modelling language™ software application structure, behaviour, and architecture. It can also
be used for describing business processes and data structures. The

Lomesh Detroja | Agile Analyst

 most common UML® diagrams used by business analysts are use case
diagrams, activity diagrams, state machine diagrams (also known as
state diagrams), and class diagrams.
A description of the observable interaction between an actor (or actors)
use case and a solution that occurs when the actor uses the system to
accomplish a specific goal.
A type of diagram defined by UML® that captures all actors and use
use case diagram
cases involved with a system or product.
user End Users
Assessing whether the delivered solution meets the needs of the
user acceptance test (UAT) stakeholder group that will be using the solution. The assessment is
validated against identified acceptance criteria.
user requirement Stakeholder Requirements
A small, concise statement of functionality or quality needed to deliver
user story
value to a specific stakeholder.
v
The process of checking that a deliverable is suitable for its intended
validation (business analysis)
use.
validated A requirement that has been reviewed and is determined to support
requirement the delivery of the expected benefits, and is within the solution scope.
The worth, importance, or usefulness of something to a stakeholder in
value (business analysis)
a context.
value stream A complete, fact-based, time-series representation of the stream of
mapping activities required to deliver a product or service.
The process of determining that a deliverable or artifact meets an
verification (business analysis)
acceptable standard of quality.
A requirement that has been reviewed and is determined to be defined
verified requirement correctly, adheres to standards or guidelines, and is at an acceptable
level of detail.
A prototype that is used to drill down into a proposed solution to
uncover requirement and design considerations through multiple layers
vertical prototype of a solution that are not easily understood or that are not discernible
on the surface. It may include interaction between several solution
components.
A set of conventions that define how requirements will be represented,
viewpoint how these representations will be organized, and how they will be
related.
VSM Value Stream Mapping
w
A review in which participants step through an artifact or set of artifacts
with the intention of validating the requirements or designs, and to
walkthrough
identify requirements or design errors, inconsistencies, omissions,
inaccuracies, or conflicts.
WBS Work Breakdown Structure

Lomesh Detroja | Agile Analyst

 A deliverable-oriented hierarchical decomposition of the work to be
work breakdown structure (WBS) executed to accomplish objectives and create the required
deliverables. It organizes and defines the total scope of the project.
A document or collection of notes or diagrams used by the business
work product (business analysis)
analyst during the requirements development process.
A facilitated and focused event attended by key stakeholders for the
workshop
purpose of achieving a defined goal.

Lomesh Detroja | Agile Analyst