Business Analysis Frameworks · Topic 3 of 4
Product Roadmaps and Business Analysis in Each Approach
CAPM product roadmaps and releases, deciding which features go in which release, and how the business analyst role differs in predictive and adaptive work.
- 4 min
- A roadmap shows vision, themes, releases and timing at a high level.
- A roadmap is a plan of intent and changes as the team learns.
- Release content depends on value, dependencies, risk, MVP, capacity and constraints.
What it is
A product roadmap is a high-level view of how a product is expected to evolve over time: the goals, major features and approximate timing of releases. It connects the product vision to the work the teams will do.
How a business analyst works depends on the project approach. In predictive projects, most requirements are defined up front. In adaptive projects, requirements are refined continuously, close to when they are built.
How it works
What a roadmap is for
- Communicating direction to stakeholders and teams.
- Aligning work with business goals and strategy.
- Showing what is planned now, next and later.
- Supporting decisions about funding and priorities.
A roadmap is a plan of intent, not a fixed commitment. It is reviewed and updated as the team learns and the market changes.
| Roadmap element | Example |
|---|---|
| Vision or goal | "Customers can manage their account fully online" |
| Theme | "Self-service payments" |
| Release | Release 2, planned for the second quarter |
| Features | Saved cards, payment history, automatic payments |
Deciding which components go to which release
| Factor | Question |
|---|---|
| Value | Which features give users the most value soonest? |
| Dependencies | Which features need others to exist first? |
| Risk and learning | Which uncertain ideas should be tested early? |
| Minimum viable product (MVP) | What is the smallest set that delivers value and lets us learn? |
| Capacity | What can the teams realistically deliver in the timeframe? |
| Constraints | Are there fixed dates, such as a regulation or a trade show? |
A worked example: an online shop plans three releases. Release 1 (the MVP) has browsing, cart and card payment, because nothing works without them. Release 2 adds saved cards and order tracking. Release 3 adds a loyalty scheme, valuable but not essential.
The business analyst in predictive and adaptive approaches
| Predictive | Adaptive | |
|---|---|---|
| When requirements are defined | Mostly up front, before design and build | Continuously, just in time for each iteration |
| Main documentation | Requirements specification, use cases, RTM | Product backlog, user stories, acceptance criteria |
| Change | Controlled through change requests against a baseline | Expected; backlog reordered as needs change |
| BA's typical activities | Detailed elicitation, analysis, sign-off, traceability | Refining the backlog with the product owner, writing stories and acceptance criteria, working daily with the team |
| Who often does BA work | A dedicated business analyst | A business analyst, the product owner or team members |
In hybrid projects, the BA may write a formal specification for a fixed regulated part and keep a backlog for the parts that change.
If a question describes a team refining requirements every iteration with a product owner, it is an adaptive approach. If it describes a signed-off requirements document before design, it is predictive.
How the exam asks about this
- "What is the purpose of a product roadmap?" To show the planned direction and evolution of the product over time.
- "Which features go in the first release?" Usually the minimum viable product: the highest value, most essential features.
- "In an adaptive project, when are detailed requirements defined?" Just in time, during backlog refinement before the iteration.
What to remember for the exam
- A roadmap shows vision, themes, releases and timing at a high level.
- A roadmap is a plan of intent and changes as the team learns.
- Release content depends on value, dependencies, risk, MVP, capacity and constraints.
- Predictive BA: up-front, documented, signed off, traced.
- Adaptive BA: continuous refinement, user stories, acceptance criteria, close to the team.
Do not treat a roadmap as a contract with fixed dates. Answers that refuse any change because "it is on the roadmap" are usually wrong.
Common mistakes
Putting nice-to-have features in the first release. Essentials and the MVP come first.
Assuming agile needs no business analysis. The work is done continuously, not skipped.
Confusing a roadmap with a detailed schedule. A roadmap is high level.
Check yourself
What is a product roadmap?
A high-level plan showing how a product is expected to evolve over time, with goals, major features and approximate release timing.
What is a minimum viable product?
The smallest version of a product that delivers value and lets the team learn from real users.
How does the business analyst's work differ in an adaptive project?
Requirements are refined continuously, usually as user stories and acceptance criteria in the backlog, working closely with the product owner and team.
Topic 3 of 4 in Business Analysis Frameworks
Test yourself on Business Analysis Frameworks
The full PMI CAPM question bank has 1,049 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by PMI. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.