Task | Purpose |
---|---|
Analyze Current State | The purpose of Analyze Current State is to understand the reasons why an enterprise needs to change some aspect of how it operates and what would be directly or indirectly affected by the change. |
Analyze Performance Measures | The purpose of Analyze Performance Measures is to provide insights into the performance of a solution in relation to the value it brings. |
Analyze Potential Value and Recommend Solution | The purpose of Analyze Potential Value and Recommend Solution is to estimate the potential value for each design option and to establish which one is most appropriate to meet the enterprise’s requirements. |
Approve Requirements | The purpose of Approve Requirements is to obtain agreement on and approval of requirements and designs for business analysis work to continue and/or solution construction to proceed. |
Assess Enterprise Limitations | The purpose of Assess Enterprise Limitations is to determine how factors external to the solution are restricting value realization. |
Assess Requirements Changes | The purpose of Assess Requirements Changes is to evaluate the implications of proposed changes to requirements and designs. |
Assess Risks | The purpose of Assess Risks is to understand the undesirable consequences of internal and external forces on the enterprise during a transition to, or once in, the future state. An understanding of the potential impact of those forces can be used to make a recommendation about a course of action. |
Assess Solution Limitations | The purpose of Assess Solution Limitations is to determine the factors internal to the solution that restrict the full realization of value. |
Communicate Business Analysis Information | The purpose of Communicate Business Analysis Information is to ensure stakeholders have a shared understanding of business analysis information. |
Conduct Elicitation | The purpose of Conduct Elicitation is to draw out, explore, and identify |
Confirm Elicitation Results | The purpose of Confirm Elicitation Results is to check the information gathered during an elicitation session for accuracy and consistency with other information. |
Define Change Strategy |
|
Define Design Options | The purpose of Define Design Options is to define the solution approach, identify opportunities to improve the business, allocate requirements across solution components, and represent design options that achieve the desired future state. |
Define Future State | The purpose of Define Future State is to determine the set of necessary conditions to meet the business need. |
Define Requirements Architecture | The purpose of Define Requirements Architecture is to ensure that the requirements collectively support one another to fully achieve the objectives. |
Identify Business Analysis Performance Improvements | The purpose of Identify Business Analysis Performance Improvements is to assess |
Identify Business Analysis Performance Improvements | The purpose of Identify Business Analysis Performance Improvements is to assess business analysis work and to plan to improve processes where required. |
Maintain Requirements | The purpose of Maintain Requirements is to retain requirement accuracy and consistency throughout and beyond the change during the entire requirements life cycle, and to support reuse of requirements in other solutions. |
Manage Stakeholder Collaboration | The purpose of Manage Stakeholder Collaboration is to encourage stakeholders to work towards a common goal. |
Measure Solution Performance | The purpose of Measure Solution Performance is to define performance measures and use the data collected to evaluate the effectiveness of a solution in relation to the value it brings. |
Plan Business Analysis Approach | The purpose of Plan Business Analysis Approach is to define an appropriate method to conduct business analysis activities. |
Plan Business Analysis Governance | The purpose of Plan Business Analysis Governance is to define how decisions are made about requirements and designs, including reviews, change control, approvals, and prioritization. |
Plan Business Analysis Information Management | The purpose of Plan Business Analysis Information Management is to develop an approach for how business analysis information will be stored and accessed. |
Plan Stakeholder Engagement | The purpose of Plan Stakeholder Engagement is to plan an approach for establishing and maintaining effective working relationships with the stakeholders. |
Prepare for Elicitation | The purpose of Prepare for Elicitation is to understand the scope of the elicitation activity, select appropriate techniques, and plan for (or procure) appropriate supporting materials and resources. |
Prioritize Requirements | The purpose of Prioritize Requirements is to rank requirements in the order of relative importance. |
Recommend Actions to Increase Solution Value | The purpose of Recommend Actions to Increase Solution Value is to understand the factors that create differences between potential value and actual value, and to recommend a course of action to align them. |
Specify and Model Requirements | The purpose of Specify and Model Requirements is to analyze, synthesize, and refine elicitation results into requirements and designs. |
Trace Requirements | The purpose of Trace Requirements is to ensure that requirements and designs at different levels are aligned to one another, and to manage the effects of change to one level on related requirements. |
Validate Requirements | The purpose of Validate Requirements is to ensure that all requirements and designs align to the business requirements and support the delivery of needed value. |
Verify Requirements | The purpose of Verify Requirements is to ensure that requirements and designs specifications and models meet quality standards and are usable for the purpose they serve. |
A task is a discrete piece of work that may be performed formally or informally as part of business analysis. The definition of a given task is universally applicable to business analysis efforts, independent of the initiative type. A business analyst may perform other activities as assigned by their organization, but these additional activities are not considered to be part of the business analysis profession. Tasks are grouped into knowledge areas. Business analysts perform tasks from all knowledge areas sequentially, iteratively, or simultaneously. Tasks may be performed in any order, as long as the necessary inputs to a task are present. A business analysis initiative may start with any task, although likely candidates are Analyze Current State or Measure Solution Performance.