Scribd
Upload
5 views2 pages

Section 1

The document discusses various frameworks for prioritizing product features, including RICE, MoSCoW, Kano Model, and AARRR. It distinguishes between a product roadmap, which outlines long-term vision and strategy, and a release plan, which focuses on short-term execution. Additionally, it highlights common pitfalls in product development such as poor communication and unclear expectations, and emphasizes the importance of usability testing and the benefits and risks of low-cost user acquisition.

Uploaded by

uxrajeev
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views2 pages

Section 1

The document discusses various frameworks for prioritizing product features, including RICE, MoSCoW, Kano Model, and AARRR. It distinguishes between a product roadmap, which outlines long-term vision and strategy, and a release plan, which focuses on short-term execution. Additionally, it highlights common pitfalls in product development such as poor communication and unclear expectations, and emphasizes the importance of usability testing and the benefits and risks of low-cost user acquisition.

Uploaded by

uxrajeev
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Section 1

Answer 1 : a) RICE

a) RICE: An acronym for Reach, Impact, Confidence, and Effort. It is used to rank features by
computing a score that combines potential value (Reach × Impact × Confidence) with effort, which
makes it suitable for measuring effort against value.

b) MoSCoW: Classifies features as Must have, Should have, Could have, and Won't have, which is
concerned with priority levels but doesn't measure effort or value.

c) Kano Model: Prioritizes customer satisfaction by categorizing features as Basic, Performance, or


Exciters, independent of implementation effort.

d) AARRR: A framework of growth metrics measuring Acquisition, Activation, Retention, Referral,


and Revenue, not for prioritization.

Answer 2:

A product roadmap is a long-term, strategic perspective of the vision, goals, and themes of the
product for quarters or years. It responds to what and why.

A release plan is short-term and tactical, specifying when particular features or updates are to be
delivered, normally coordinated with sprints or deadlines.

In summary:

Roadmap = vision + strategy (long-term)

Release plan = timelines + execution (short-term)

Answer 3:

Poor Communication

Failure pitfall: Lack of alignment and mistrust.

Prevent by: Open communication channels, regular updates, and clear documentation.

Unclear Expectations

Failure pitfall: Ambiguity regarding roles and deliverables.

Prevent by: Establishing clear roles and responsibilities in advance, employing tools such as RACI
matrices.

Ignoring Feedback

Pitfall: Stakeholders are not heard; product can lose important requirements.

Avoid by: Actively listening, where possible, and revealing decisions clearly.

Answer 4:
Usability testing with a moderator is ideal for early prototypes because:

Early prototypes tend to be low-fidelity or incomplete, and need guidance.

A moderator is able to observe user behavior, ask questions to clarify, and probe deeper into
confusion or problems.

Quick feedback helps identify usability issues before large development investment.

Answer 5:

Benefits:

Quick user acquisition at low costs.

Faster penetration in the market and competitive edge.

More users offer greater feedback on product refinement.

Risks:

Thin or negative margins initially, jeopardizing sustainability.

Customers may link low price to low quality.

Risk of churn when prices are raised subsequently if not handled properly.

You might also like