Artefacts

This is the list of artefacts that a Business Analyst produces
ArtefactPurpose
Business Analysis Approach
Business Analysis Information

Business Analysis Information is any kind of information at any level of detail that is used as an input or output of business analysis work. Business analysis information becomes an input for this task when the need is discovered to communicate the information to additional stakeholders.


Business Analysis Information (communicated)

Business Analysis Information (communicated) is business analysis information that the target stakeholders have reached an understanding of its content and implications.


Business Analysis Performance Assessment
Designs

Designs may be traced to other requirements, solution components, and other work products.


Designs (maintained)

Designs (maintained) may be reusable once defined. For example, as a self-contained component that can be made available for possible future use.


Designs (prioritized)

Designs (prioritized): prioritized or ranked designs are available for additional

work, ensuring that the highest valued designs are addressed first.


Designs (traced)

Designs (traced) clearly defined relationships to other requirements, solution components, or releases, phases, or iterations, within a solution scope, such that coverage and the effects of change are clearly identifiable.


Designs Change Assessment

Designs Change Assessment is the recommendation to approve, modify, or deny a proposed change to one or more design components.


Elicitation Activity Plan
Elicitation Results (confirmed)

Elicitation Results (confirmed) is integrated output that the business analyst and other stakeholders agree correctly reflects captured information and confirms that it is relevant and useful as an input to further work.


Elicitation Results (unconfirmed)

Elicitation Results (unconfirmed) is captured information in a format that is specific to the elicitation activity.


Governance Approach
Information Management Approach
Needs
Performance Objectives (external)
Proposed Change

Proposed Change can be identified at any time and impact any aspect of business analysis work or deliverables completed to date. There are many triggers for a proposed change including business strategy changes, stakeholders, legal requirements, or regulatory changes.


Requirements

Any combination of requirements and/or designs in the form of text, matrices, and diagrams. May be traced to other requirements (including goals, objectives, business requirements, stakeholder requirements, solution

requirements, and transition requirements), solution components, visuals, business rules, and other work products.


Requirements (maintained)

Requirements (maintained) are defined once and available for long-term usage by the organization. They may become organizational process assets or be used in future initiatives. In some cases, a requirement that was not approved or implemented may be maintained for a possible future initiative.


Requirements (prioritized)

Requirements (prioritized): prioritized or ranked requirements are available for additional work, ensuring that the highest valued requirements are addressed first.


Requirements (traced)

Requirements (traced) have clearly defined relationships to other requirements, solution components, or releases, phases, or iterations, within a solution scope, such that coverage and the effects of change are clearly identifiable.


Requirements Change Assessment

Requirements Change Assessment is the recommendation to approve, modify, or deny a proposed change to requirements.


Stakeholder Engagement

Stakeholder Engagement is the willingness from stakeholders to engage in business analysis activities and interact with the business analyst when necessary. This is not an artefact that is produce but rather the result of the Stakeholder Engagement activities.


Stakeholder Engagement Approach