SaaS SaaS Product Management and Development 2 — Questions and Answers
Question 1: What is a 'minimum viable product' (MVP) in the context of SaaS development?
- The cheapest version of a product that can be built
- A product with just enough features to gather validated learning from early customers (Correct answer)
- A product that meets minimum regulatory compliance requirements
- A prototype shared only with internal stakeholders
Correct answer: A product with just enough features to gather validated learning from early customers
An MVP contains only the core features needed to test a hypothesis with real customers and collect actionable feedback efficiently.
Question 2: Which SaaS development approach emphasizes continuous delivery of small increments with frequent customer feedback loops?
- Waterfall
- Agile (Correct answer)
- Big Bang
- V-Model
Correct answer: Agile
Agile development breaks work into short iterations with continuous feedback, making it ideal for SaaS where rapid adaptation to customer needs is critical.
Question 3: What is 'feature creep' and why is it particularly risky in SaaS?
- A security exploit targeting new features
- The uncontrolled growth of product scope that increases complexity and costs (Correct answer)
- A bug introduced when features interact unexpectedly
- A gradual decline in feature usage over time
Correct answer: The uncontrolled growth of product scope that increases complexity and costs
Feature creep—adding scope beyond the original vision—inflates engineering costs, slows delivery, and can make the product harder to use, which is especially damaging in subscription-based SaaS.
Question 4: What role does a 'product roadmap' play in SaaS product management?
- It is a legally binding delivery commitment to customers
- It is a high-level visual plan that communicates product direction and priorities over time (Correct answer)
- It replaces the sprint backlog in agile teams
- It documents the technical architecture of the product
Correct answer: It is a high-level visual plan that communicates product direction and priorities over time
A product roadmap communicates strategic direction and feature priorities to internal and external stakeholders without being a contractual delivery commitment.
Question 5: When measuring SaaS product engagement, what does 'DAU/MAU ratio' indicate?
- The ratio of daily active users to monthly active users, showing product stickiness (Correct answer)
- The ratio of daily app updates to monthly releases
- Daily average usage minutes divided by monthly active users
- The percentage of users who upgrade from daily to monthly billing
Correct answer: The ratio of daily active users to monthly active users, showing product stickiness
DAU/MAU measures how often monthly users return daily; a higher ratio indicates strong product stickiness and habitual usage.
Question 6: In SaaS, what is 'technical debt' and how does it affect product velocity?
- Outstanding invoices from infrastructure vendors
- Accumulated shortcuts in code that make future changes harder and slower (Correct answer)
- The cost of migrating legacy customers to new features
- Bugs that have been logged but not yet fixed
Correct answer: Accumulated shortcuts in code that make future changes harder and slower
Technical debt refers to expedient code decisions that accumulate over time, making the codebase harder to modify and slowing down future feature development.
Question 7: Which of the following best describes 'continuous deployment' in a SaaS context?
- Deploying code to production automatically after passing all automated tests (Correct answer)
- Scheduling releases monthly after manual QA approval
- Deploying to staging environments only until a quarterly release window
- Continuously training deployment engineers on new tooling
Correct answer: Deploying code to production automatically after passing all automated tests
Continuous deployment automatically pushes every code change that passes automated tests directly to production, enabling SaaS teams to ship multiple times per day.
What is a 'minimum viable product' (MVP) in the context of SaaS development?