Product analysis is a technique for translating a high-level product description into the tangible deliverables, features, and requirements the project must produce. It is used on projects whose main output is a product rather than a service or result.
How it is used in practice
Product analysis breaks a product down into its parts and characteristics so the team understands exactly what has to be built. Common methods include product breakdown, requirements analysis, systems analysis, systems engineering, and value analysis. The result is a clearer definition of scope and a shared understanding of what “done” means for the product.
Where it fits in the PMBOK Guide 8th Edition
Product analysis supports scope definition within the Planning performance domain. It turns the intent captured in the product vision and requirements documentation into a decomposed set of deliverables that can feed the work breakdown structure.
Frequently asked questions
When do you use product analysis? On projects delivering a physical or software product, to convert an abstract description into concrete requirements.
What techniques does it include? Product breakdown, systems analysis, systems engineering, requirements analysis, and value analysis.
By Tom, PMP-certified since 2004. Last updated: July 2026.