Artefact | Purpose |
---|---|
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 | |
Business Objectives | Business Objectives is the desired direction that the business wishes to pursue in order to achieve the future state. |
Business Requirements | Business Requirements is the problem, opportunity, or constraint which is defined based on an understanding of the current state. |
Change Strategy | Change Strategy is the approach that the organization will follow to guide change. |
Current State Description | Current State Description is the context of the enterprise’s scope, capabilities, resources, performance, culture, dependencies, infrastructure, external influences, and significant relationships between these elements. |
Design Options | Design Options describe various ways to satisfy one or more needs in a context. They may include solution approach, potential improvement opportunities provided by the option, and the components that define the option. |
Designs | Designs may be traced to other requirements, solution components, and other work products. |
Designs (approved) | Designs (approved) are designs which are agreed to by stakeholders and are ready for use in subsequent business analysis or solution development efforts. |
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 |
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 | Elicitation Results are used to define and understand the current state. |
Elicitation Results (any state) | Elicitation Results (any state) are used to begin modelling and may lead to the need for more elicitation to clarify or expand upon requirements. Elicitation and modelling may occur sequentially, iteratively, or concurrently. |
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. |
Enterprise Limitation | Enterprise Limitation is a description of the current limitations of the enterprise including how the solution performance is impacting the enterprise. |
Future State Description | Future State Description is the future state description includes boundaries of the proposed new, removed, and modified components of the enterprise and the potential value expected from the future state. The description might include the desired future capabilities, policies, resources, dependencies, infrastructure, external influences, and relationships between each element. |
Governance Approach | |
Implemented Solution (external) | Implemented Solution (external) is a solution (or component of a solution) that exists in some form. It may be an operating solution, a prototype, or a pilot or beta solution. |
Influences | Influences are factors inside of the enterprise (internal) and factors outside of the enterprise (external) which will impact the realization of the desired future state. |
Information Management Approach | |
Needs | The business analysis approach is shaped by the problem or opportunity faced by the organization. |
Performance Objectives (external) | |
Potential Value | Potential Value is the value that may be realized by implementing the proposed future state. |
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. |
Recommended Actions | Recommended Actions are recommendation of what should be done to improve the value of the solution within the enterprise. |
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 (approved) | Requirements (approved) are requirements which are agreed to by stakeholders and are ready for use in subsequent business analysis efforts. |
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 (specified and modelled) | Requirements (specified and modelled) is any combination of requirements and/or designs in the form of text, matrices, and diagrams. |
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 (validated) | Requirements (validated) are those requirements and designs that can be demonstrated to deliver benefit to stakeholders and align with the business goals and objectives of the change. If a requirement or design cannot be validated, it either does not benefit the organization, does not fall within the solution scope, or both. |
Requirements (verified) | Requirements (verified) is a set of requirements that have been verified to be of sufficient quality to be used as a reliable body of work for further specification and development. |
Requirements Architecture | Requirements Architecture is the requirements and the interrelationships among them, as well as any contextual information that is recorded. |
Requirements Change Assessment | Requirements Change Assessment is the recommendation to approve, modify, or deny a proposed change to requirements. |
Risk Analysis Results | Risk Analysis Results is an understanding of the risks associated with achieving the future state, and the mitigation strategies which will be used to prevent those risks, reduce the impact of the risk, or reduce the likelihood of the risk occurring. |
Solution Limitation | Solution Limitation is a description of the current limitations of the solution including constraints and defects. |
Solution Performance Analysis | Solution Performance Analysis is results of the analysis of measurements collected and recommendations to solve performance gaps and leverage opportunities to improve value. |
Solution Performance Measures | Solution Performance Measures are measures that provide information on how well the solution is performing or potentially could perform. |
Solution Recommendation | Solution Recommendation identifies the suggested, most appropriate solution based on an evaluation of all defined design options. The recommended solution should maximize the value provided to the enterprise. |
Solution Scope | Solution Scope is the solution scope that will be achieved through execution of the change strategy. |
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 |
This is the list of artefacts that a Business Analyst produces