Business analysis management is the ITIL 4 (and ITIL (Version 5)) practice responsible for working out what an organization or its customers need, then building the case for a solution that meets that need. The ITIL 4 practice guide sets the purpose as identifying needs and recommending solutions that create value for stakeholders.
The Scope of Business Analysis
The scope of business analysis varies by organization. Some run it at the whole-organization level, examining structure, architecture, and process wherever they touch value. Others keep it narrower, tied to a specific product or service and the needs of the people who use it.
The right model depends on how the organization is set up and who it serves. An organization mid-transformation is more likely to want the wider lens, while an external provider working a straightforward contract with a client usually keeps business analysis close to the product itself.
Utility, Warranty, and Experience
The Business Analysis Management practice sorts stakeholder needs into three categories. Utility is what a service does: the functionality that either supports the customer’s performance or removes something holding them back. Warranty is how well it performs against agreed conditions, covering availability, capacity, security, and continuity. Experience covers the sum of a stakeholder’s functional and emotional interactions with the service and the people delivering it.
Business analysts use the split mainly to check that a requirement hasn’t collapsed one category into another, like a change that looks like pure functionality when it is really a warranty problem.
SWOT Analysis and User Story Mapping
SWOT analysis
SWOT analysis weighs internal strengths and weaknesses against external opportunities and threats. It can help decide whether a service is needed and whether to build it internally or buy it.
User story mapping
User story mapping breaks a product or service into fragments a team can build against, with each story kept independent, negotiable, valuable, estimable, small, and testable (INVEST).
The guide covers a much wider field of analysis techniques, and these are only two of them.
Business Analysis Management Practice Success Factors and the Value Chain
Business Analysis Management has two practice success factors.
The first is building and maintaining a consistent, organization-wide approach, one flexible enough to run differently for a new product launch than for a legacy system change.
The second is making sure the organization’s and its customers’ current and future needs are understood and met with solutions delivered on time. Both get tracked through metrics such as stakeholder satisfaction with proposed solutions, the number of misalignments between what’s delivered and the organization’s strategy, and how long analysis takes relative to when the answer was needed.
Business analysis touches every activity in the ITIL service value chain, from plan and engage through to design and transition, obtain and build, deliver and support, and improve. The Business Analysis Management practice guide places its heaviest contribution in design and transition and its lightest in improve.
The Two Business Analysis Processes
The Business Analysis Management practice runs on two processes. The first, designing and maintaining a business analysis approach, is the housekeeping process. It takes the organization’s strategy, structure, and portfolio and turns them into a documented approach covering scope, methods, and who’s responsible for what. Business analysts build this alongside architects, product owners, and portfolio managers, and review it on a cycle using business analysis records, audit reports, and periodic checks against on how well the approach is working.
The second process is business analysis and solution identification. A business analyst gathers information from stakeholders through:
- Interviews
- Workshops
- Observation
- Document review
The analyst then builds a business analysis report that includes a traceability matrix, so requirements can be checked against the delivered solution later. From there, the business analyst:
- Drafts two or more solution options
- Builds a comparison
- Recommends one to the decision owner, typically a service sponsor or product owner
Once a solution is underway, the business analyst supports the delivery teams by translating requirements into a working service, then checks the result against the benefits the solution was meant to produce, feeding anything short of the mark back into the continual improvement register.
The Business Analyst Role
The guide describes the business analyst almost as an investigator, someone who works with the unknown, gathers evidence, questions the people it came from, and arrives at a hypothesis they can test.
It is not a technical or purely process-driven role, and the traits the guide picks out are persistence, comfort with ambiguity, and the ability to spot the important relationships inside a new problem quickly, all of which count for more than any specific tool skill.
The business analyst role isn’t tied to a single team structure anymore. In agile organizations, business analysis increasingly happens inside the product team itself, owned by a product or service owner rather than a specialist function working alongside development. Where that happens, business analysis is part of the team’s day-to-day work rather than a discrete project stage.
Whichever structure an organization runs, the Business Analysis Management practice guide is clear that the business analyst stays the primary source of truth on requirements for the full life of the solution.
Business Analysis Tooling and Information
How well business analysis works depends on the quality of the information going into it, and the Business Analysis Management practice pulls from a wide range of sources, including strategy, portfolios, architecture roadmaps, service configuration data, the organization’s change schedule, and technology trends. The tooling that supports it splits into three groups: office tools for documents and presentations, analysis and modeling tools for diagramming and data work, and communication tools for coordinating everyone who needs to be kept in the loop. Tooling affects how quickly information reaches the analyst, though it does not do the analysis.
Internal or External Business Analysis
Business analysts can sit inside the organization or come in from a supplier. External resources often bring capacity and can move faster against a fixed deadline, and outsourced product development teams often include business analysis in how they work. Internal analysts bring ongoing knowledge of the business and, generally, more motivation to sit with the people whose problems they’re solving, which is hard to write into a contract. Organizations going through digital transformation usually lean internal, because business analysis at that scale becomes tied to the organization’s strategic direction and that is harder to hand off.
Source
This article draws on the ITIL 4 Business Analysis Management practice guide from PeopleCert, where you can find the full set of ITIL 4 and future ITIL (Version 5) practice guides. For more on how this practice connects to the wider framework, see our explainer on what ITIL is and how the practice fits inside the service value chain.
Business Analysis Management FAQs
It’s the ITIL 4 management practice responsible for identifying an organization’s and its customers’ needs and recommending solutions that address them, covering everything from stakeholder requirements gathering through to justifying and supporting the chosen solution.
They’re the three ways the Business Analysis Management practice frames a stakeholder need. Utility covers what a service does, warranty covers how reliably it performs against agreed conditions, and experience covers the functional and emotional impact of using it.
Designing and maintaining a business analysis approach, and business analysis and solution identification, which covers gathering requirements, proposing solutions, supporting delivery, and assessing the result.
It depends on the organization and need. External analysts can add capacity and speed, while internal analysts bring lasting business knowledge and are usually favored by organizations mid-transformation, where the practice becomes tied to strategic direction.
Sophie Danby
Sophie is a freelance ITSM marketing consultant, helping ITSM solution vendors to develop and implement effective marketing strategies.
She covers both traditional areas of marketing (such as advertising, trade shows, and events) and digital marketing (such as video, social media, and email marketing). She is also a trained editor.
