Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Analysis includes the processes to examine and document product information in sufficient detail to ensure that it reflects the stakeholders' needs, aligns to their goals and business objectives, and enables the identification of viable solution designs.

The business analysis processes are presented as discrete processes below, although in practice, they overlap and interact :

4.

1 Determine

1 Determine Analysis Approach

4.

2 Create

2 Create and Analyze Models

4.

3 Define

3 Define and Elaborate Requirements

4.

4 Define

4 Define Acceptance Criteria

4.

5 Verify

5 Verify Requirements

4.

6 Validate

6 Validate Requirements

4.

7 Prioritize he

7 Prioritize Requirements

4.8 Identify and Analyze Risks

4.9 Assess Product Design Options

The process of thinking ahead about how analysis will be performed, including what will be analyzed; which models will be most beneficial to produce; and how requirements and other product information will be verified, validated, and prioritized.

The process of creating structured representations, such as diagrams, tables, or structured text, of any product information to facilitate further analysis by identifying gaps in information or uncovering extraneous information.

The process of refining and documenting requirements and other types of product information at the appropriate level of detail, and level of formality required for various audiences.

The process of obtaining agreement as to what would constitute proof that one or more aspects of a solution have been developed successfully.

The process of checking that requirements are of sufficient quality. (Are we building the solution the right way?)

The process of checking that the requirements meet business goals and objectives. (Is this solution right for us?)

The process of understanding how individual pieces of product information achieve stakeholder objectives, and using that information, along with other agreed-upon prioritization factors, to facilitate ranking of the work.

T

The process of uncovering and examining assumptions and uncertainties that could positively or negatively affect success in the definition, development, and the expected results of the solution.

The process of identifying, analyzing, and comparing solution design options based

on

on the business goals and objectives, expected costs of implementation, feasibility, and associated risks, and using the results of this assessment to provide recommendations regarding the design options presented.

Inputs

Inputs

Inputs

Inputs

Inputs

Inputs

Inputs

Inputs

Inputs

  • Project scope

  • Elicitation approach

  • Analysis approach

  • Confirmed requirements elicitation document

  • Analysis approach

  • Analysis models

  • Confirmed elicitation results

  • Stakeholder engagement and  communication approach

  • Analysis approach

  • Analysis models

  • Confirmed elicitation results

  • Solution evaluation approach

  • Program standards

  • Project scope and project needs

  • Business analysis ITS standards 

  • Compliance standards

  • Acceptance criteria

  • Business goals and objectives

  • Verified Requirements 

  • Analysis approach

  • Business goals and objectives

  • Change requests

  • Detailed requirements

  • Business Goals and objectives

  • Product scope

  • Environmental factors

  • Requirements

  • Business Goals and objectives

  • Enterprise Architechture

  • Prioritized requirements

Tools

Tools

Tools

Tools

Tools

Tools

Tools

Tools

Tools

  • Brainstorming

  • Document analysis (to capture prior available information)

  • Retrospectives and Lessons Learned

  • Data dictionary

  • Data flow diagram

  • Decision tree

  • Ecosystem map

  • Event list

  • Entity relationship diagram

  • Prototype 

  • Wireframes

  • Story mapping

  • Use case diagram

  • User interface flow

  • Business rules catalog

  • Definition of 'Ready' 

  • Glossary

  • Product backlog

  • Story elaboration

  • Use case

  • User story

  • Definition of 'Done'

  • Story elaboration

  • Peer Reviews

  • Alignment with INVEST (Independent, negotiable, valuable, estimable, small, testable)

  • Walkthroughs

  • Backlog management

  • Business Goals

  • Kanban board

  • Story mapping

  • Traceability matrix

  • Ecosystem map

  • Estimation techniques

  • Organization charts

  • Process flows

  • SWOT analysis

  • Root cause and opportunity analysis

  • Risk register

  • Risk burndown chart

Brainstorming

Affinity diagrams

Options evaluation

Output(s)

Output(s)

Output(s)

Output(s)

Output(s)

Output(s)

Output(s)

Output

Output

  1. Analysis approach

  1. Analysis models

  1. Further Detailed Requirements

  1. Acceptance criteria

  1. Verified detailed requirements

  1. Validate requirements

  1. Prioritized requirements

  1. Risk Analysis

  1. Viable solution design options

Analysis includes the processes to examine and document product information in sufficient detail to ensure that it reflects the stakeholders' needs, aligns to their goals and business objectives, and enables the identification of viable solution designs.

The business analysis processes are presented as discrete processes below, although in practice, they overlap and interact :

4.

1 Determine

1 Determine Analysis Approach

4.

2 Create

2 Create and Analyze Models

4.

3 Define

3 Define and Elaborate Requirements

4.

4 Define

4 Define Acceptance Criteria

4.

5 Verify

5 Verify Requirements

4.

6 Validate

6 Validate Requirements

4.

7 Prioritize

7 Prioritize Requirements

4.8 Identify and Analyze Risks

4.9 Assess Product Design Options

The process of thinking ahead about how analysis will be performed, including what will be analyzed; which models will be most beneficial to produce; and how requirements and other product information will be verified, validated, and prioritized.

The process of creating structured representations, such as diagrams, tables, or structured text, of any product information to facilitate further analysis by identifying gaps in information or uncovering extraneous information.

The process of refining and documenting requirements and other types of product information at the appropriate level of detail, and level of formality required for various audiences.

The process of obtaining agreement as to what would constitute proof that one or more aspects of a solution have been developed successfully.

The process of checking that requirements are of sufficient quality. (Are we building the solution the right way?)

The process of checking that the requirements meet business goals and objectives. (Is this solution right for us?)

The process of understanding how individual pieces of product information achieve stakeholder objectives, and using that information, along with other agreed-upon prioritization factors, to facilitate ranking of the work.

The

The process of uncovering and examining assumptions and uncertainties that could positively or negatively affect success in the definition, development, and the expected results of the solution.

The process of identifying, analyzing, and comparing solution design options based

on

on the business goals and objectives, expected costs of implementation, feasibility, and associated risks, and using the results of this assessment to provide recommendations regarding the design options presented.

Inputs

Inputs

Inputs

Inputs

Inputs

Inputs

Inputs

Inputs

Inputs

  • Project scope

  • Elicitation approach

  • Analysis approach

  • Confirmed requirements elicitation document

  • Analysis approach

  • Analysis models

  • Confirmed elicitation results

  • Stakeholder engagement and  communication approach

  • Analysis approach

  • Analysis models

  • Confirmed elicitation results

  • Solution evaluation approach

  • Program standards

  • Project scope and project needs

  • Business analysis ITS standards 

  • Compliance standards

  • Acceptance criteria

  • Business goals and objectives

  • Verified Requirements 

  • Analysis approach

  • Business goals and objectives

  • Change requests

  • Detailed requirements

  • Business Goals and objectives

  • Product scope

  • Environmental factors

  • Requirements

  • Business Goals and objectives

  • Enterprise Architechture

  • Prioritized requirements

Tools

Tools

Tools

Tools

Tools

Tools

Tools

Tools

Tools

  • Brainstorming

  • Document analysis (to capture prior available information)

  • Retrospectives and Lessons Learned

  • Data dictionary

  • Data flow diagram

  • Decision tree

  • Ecosystem map

  • Event list

  • Entity relationship diagram

  • Prototype 

  • Wireframes

  • Story mapping

  • Use case diagram

  • User interface flow

  • Business rules catalog

  • Definition of 'Ready' 

  • Glossary

  • Product backlog

  • Story elaboration

  • Use case

  • User story

  • Definition of 'Done'

  • Story elaboration

  • Peer Reviews

  • Alignment with INVEST (Independent, negotiable, valuable, estimable, small, testable)

  • Walkthroughs

  • Backlog management

  • Business Goals

  • Kanban board

  • Story mapping

  • Traceability matrix

  • Ecosystem map

  • Estimation techniques

  • Organization charts

  • Process flows

  • SWOT analysis

  • Root cause and opportunity analysis

  • Risk register

  • Risk burndown chart

Brainstorming

Affinity diagrams

Options evaluation

Output(s)

Output(s)

Output(s)

Output(s)

Output(s)

Output(s)

Output(s)

Output

Output

  1. Analysis approach

  1. Analysis models

  1. Further Detailed Requirements

  1. Acceptance criteria

  1. Verified detailed requirements

  1. Validate requirements

  1. Prioritized requirements

  1. Risk Analysis

  1. Viable solution design options

Templates: All tools above can be used to conduct the analysis. Depending on the need of the project, the deliverable for the analysis vary (no standard templates).