Skip to content
Agile Analysis

icon picker
Analysis & Design

Backlog Refinement
Is used to ensure there is enough detail and clarity for items in the backlog so that the delivery team can complete an iteration.
Activities may include: Story Elaboration, Story Decomposition, prioritization, and sequencing.
To split large items into smaller ones that meet the INVEST criteria. Acceptance criteria or additional documentation needed to devlier an item can also be added.
Definition of Ready: a set of criteria the team agrees must be satisfied to consider an item "ready" for the next iteration.
Behavior Driven Development
Is used to increase value, decrease waste, and increase communication between stakeholders and delivery teams by focusing on the intended customer behaviour for the solution to satisfy customer needs.
Gherkin syntax:
Given <a situation>
When <an event>
Then <expected result>
Impact Mapping
Is used to align stakeholders with organizational goals and the creation of customer value.
Job Stories (Job to be Done)
Are used to represent a product backlog item or requirement in terms of a job to be done by a stakeholder.
When <situation> I want to <motivation> so I can <expected outcomes>
Kano Analysis
Is used to understand which product characteristics or qualities will prove to be a significant differentiator in the marketplace and help to drive customer satisfaction.
Minimal Viable Product
Is used to avoid cost and risk associated with developing the wrong product by testing a hypothesis, reducing waste, or increasing speed to customers for feedback and adoption.
MVP identifies the smallest set of features or requirements to deliver value to stakeholders and satisfy early adopters in the shortest time possible.
Personas
Are used to understand and empathise with an intended stakeholder in order to align the solution with the stakeholder need.
Planning Workshops
Are used to determine what value can be delivered over an agreed time period.
Can be used at any planning horizon (strategic, initiative, or delivery).
Portfolio Kanban
Is used to manage the implementation of strategic initiatives by increasing visibility into the process, work-in-progress, decision making criteria, and feedback loops.
Product Roadmap
Is used to communicate direction and progress towards the vision for a solution or initiative, and it measures progress against that vision through achieving the stakeholders' desired outcome.
Purpose Alignment Model
Is used to assess ideas in the context of customer and business value.
Real Options
Is used to help determine when to make decisions.
Relative Estimation
Is used to make future predictions based on past experience, knowledge, complexity, size, and uncertainty required to complete backlog items.
Knowledge: How much information does the team have?
Experience: Has the team done this / similar item before?
Complexity: How difficult is the implementation likely to be?
Size: How big is the story? How long will it take?
Uncertainty: What variables and unknown factors might impact the story?
Retrospectives
Are used to continuously improve by reflecting on what went well, what could be better, and to improve processes.
Reviews
Are used to demonstrate and inspect an increment of the solution with stakeholders in order to elicit feedback to determine if the solution being developed aligns with the need.
All team members working on the initiative are present to facilitate discussion and elicit feedback.
Spikes
Are used to time-box research, design, exploration, investigation, or prototyping activities in order to understand the effort required to deliver a backlog item or an initiative.
Functional: analyses a story and determines how to break it down into smaller stories or tasks, or identify where the risk and complexity exists.
Technical: determines the feasibility or impact of a story or task to understand the technical design necessary.
Exploratory: explores organizational risks or impacts for a particular initiative or backlog item.
Storyboarding / Customer Journey / Navigation Flow / Dialogue Map
Is used to describe a task, scenario, or story in terms of how stakeholders interact with the solution.
Story Decomposition
Is used to represent the requirements for a solution at the appropriate level of detail and are aligned to desired outcomes.
Story Elaboration
Is used to define the detailed design and acceptance criteria for a story as needed to deliver a working solution.
This is completed in a workshop with those who will execute the story: SMEs, the customer representative who needs the story, the person who will test the story, and a business analysis practitioner who facilitates and challenges the story.
Story Mapping
Is used to assist in creating understanding of product functionality, the flow of usage, and to assist with prioritizing product delivery.
User Stories
Are used to convey a customer requirement for the delivery team.
As a <role>, I need to <feature> so that <goal or value>.
In order to <business value>, as a <role>, I need to <behaviour>.
Value Modeling
Is used to focus solution development on value delivery by tracing decisions to the value perspective of the stakeholder.
Value Stream Mapping
Is used to provide a complete, fact-based, time-series representation of the stream of activities required to deliver a product or service to the internal or external customer.
Visioning
Is used to determine the desired outcome of an initiative in a concise and approachable manner.

50 Business Analysis Techniques

Solution Evaluation
Acceptance & Evaluation Criteria #product-management
Metrics and Key Performance Indicators (KPIs) #product-management
Non-functional Requirements Analysis
Process Analysis
Root Cause Analysis
Vendor Assessment

Requirements Lifecycle Management
Backlog Management #product-management
Business Rules Analysis
Glossary
Item Tracking
Lessons Learned
Prioritization
Reviews

Requirements Analysis & Design
Business Rules Analysis
Concept Modeling
Data Dictionary
Data Flow Diagrams
Data Modeling
Decision Analysis
Decision Modeling
Mind Mapping
Process Modeling
Sequence Diagrams
State Modeling
Use Cases & Scenarios
User Stories

Strategy Analysis
Balanced Scorecard
Business Capability Analysis
Business Cases
Business Model Canvas
Financial Analysis
Risk Analysis & Management
SWOT Analysis


Requirements Elicitation
Benchmarking & Market Analysis
Brainstorming
Collaborative Games
Document Analysis
Focus Groups
Interviews
Observation
Prototyping
Survey / Questionnaire
Workshops

Planning
Estimation
Functional Decomposition
Interface Analysis
Organizational Modeling
Scope Modeling
Stakeholder List, Map, or Personas


Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.