• Skip to main content
  • Skip to primary sidebar

BABLOCKS.COM

The Next Generation of Business Analysis Education

  • BA Spaces™
  • BAPC™
  • PODCAST
  • DICTIONARY
  • LOG IN

emal bariali / August 29, 2020

Minimum Viable Product

The bare minimum set of functions and features that the customer needs to have a useful product delivered to them.

The purpose of going agile is to make sure the project team can get a product out to the customer as early as possible.

At this early stage, the product is nowhere near being complete, but establishing an MVP ensures that this first release of the product gives the customer the features and functions that they can actually start using in their day-to-day work while the project team works their way through the rest of the product backlog to deliver the rest of the product.

As a business analyst, you may be required to determine the MVP for the projects that you work on. This can be a difficult challenge as the customer will naturally want as much of the features and functions as quickly as possible. It will be your job to convince the customer why certain requests they are making are not going to be released and helping your customer plan their business activities around the release schedule that the project team creates for the product you are helping to deliver.

Boost Your BA Career

Join The 3000+ Analysts Who Have Trusted BA BLOCKS To Boost Their BA Careers

JOIN US

Filed Under: Business Analysis Terms and Definitions, Uncategorized

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

A • Agile • Activities

B • Backlog • BACOE • BPM • Business Analyst • Business Architect  • Business Case • Business  Procedures • Business Process • Business Requirements • Business Rules • Business Constraint • Business Process Management • Business Process Modeling

C • Customer • Current State Analysis • Change Request • CBAP • Constraint 

D • Data Dictionary • Data Modeling • Defect • Defect Management • Deliverable • DevOps • Domain Knowledge

E • End-User • Enterprise System

F • Feasibility • Functional Scope • Functional Specification • Future State • Functional Decomposition • Funding

I • IIBA • Impact Assessment • In Scope

J • JIRA

M • Methodology • MVP • Minimum Viable Product

O • Out of Scope

P • Product • Product Backlog • Product Manager • Product Owner • Pre-Project • Project • Project Manager • Project Sponsor • Pilot Project • Proof of Concept • Prototyping • Permissions Matrix • PMI • PMI-PBA • Project Scope • Product Scope

Q • QA • Quality Assurance

R • Requirements • Risk Management •

S • Scope • Scope Creep • Solution • Solution • SPOC • Sponsor • Stakeholder • Stakeholder Analysis • System Interface

T • Traceability Matrix • Technical Constraint •

U • UAT • User Interface • User Interaction • Use Case • User Story • User Role

V • Vendor • Vendor Assessment

W • Workshop • Workplan • WBS

Copyright © 2023 · BA BLOCKS  

  • Terms of Use
  • Privacy Policy
  • Refund Policy
  • About Us