B
BrainBOK
PricingStudy GuideFAQ
DashboardITTO ExplorerQuizFlashcardsExamsStudy Guide
DashboardITTO ExplorerQuizFlashcardsExamsStudy Guide
Guide Index
  • Business Analysis Overview
  • Business Analysis to Project Initiation
  • Business Analysis and Project Management
  • Skillset and Expertise for BA Role
  • BA and PM - The Big Picture
  • Business Analysis Processes - Overview
  • Needs Assessment
  • Business Analysis Planning
  • Requirements Elicitation and Analysis
  • Traceability and Monitoring
  • Solution Evaluation
  • Business Analysis Plan
  • Business Case
  • Product Scope
  • Situation Statement
  • Brainstorming
  • Collaborative Games
  • Document Analysis
  • Facilitated Workshops
  • Focus Groups
  • Interviews
  • Observation
  • Prototyping
  • Questionnaires and Surveys
  • Buy a Feature
  • Delphi
  • Minimum Viable Product (MVP)
  • MoSCoW
  • Multivoting
  • Purpose Alignment Model
  • Timeboxing
  • Weighted Ranking
  • Weighted Shortest Job First (WSJF)
  • Overview
  • Feature Model
  • Kano Model
  • System Interface Table
  • Use Case
  • User Story
  • Competitive Analysis
  • Iteration Planning
  • Peer Reviews
  • Product Visioning
  • Story Mapping
  • SWOT Analysis
  • Traceability Matrix
  • Business Analysis Plan vs Requirements Management Plan
  • Creative Thinking
  • Requirement Types
Business Analysis

Artifacts

Product Scope

An explanation of the product scope in business analysis

Product scope refers to the features and functions that characterize a solution. It is created along with the business case as an output of the Assemble Business Case process, which integrates inputs from identifying the problem or opportunity, determining the future state, evaluating viable options, and developing the product roadmap. If the business case is approved, the initial product scope is established based on the chosen solution approach.

Business Documents Relationship

The product scope, understood at a high level at this stage, is used alongside the business case to develop the project charter. The charter formally authorizes the project, outlining the initial requirements and high-level scope, which helps guide the project's direction and ensures alignment with stakeholder expectations. The business case provides the rationale for the project, highlighting the benefits, costs, and potential risks, while the product scope defines what the solution will deliver in terms of features and capabilities.

As the project progresses, the product scope continues to be refined through detailed analysis. It may be revised in response to changing business needs, emerging risks, or constraints imposed by budget or schedule. This iterative refinement process ensures that the product remains aligned with strategic goals and stakeholder requirements, adapting to any changes in the business environment or project context.

Throughout the initiative, the defined product scope is used as an input in several key business analysis processes. These include preparing for transition to the future state, determining and conducting elicitation, managing requirements, and evaluating the solution. By maintaining a clear and updated product scope, business analysts ensure a consistent and focused approach, facilitating effective communication, risk management, and alignment with the overall project objectives.

PreviousBusiness Analysis Processes - OverviewNextBrainstorming