Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 41 views

    Goal: Product Requirements Document - Paytm QR Scan (Hypothetical)

    Uploaded by

    Hritik Lal
    This product requirements document outlines the goals, success metrics, user personas, user stories, and timeline for developing a Paytm QR scan feature. It includes tables for metrics, user personas prioritizing pain points, user stories and acceptance criteria, and a release plan timeline. Open issues and future scope are also documented. The goal is to make QR code payments quick by optimizing the camera scan and API response times.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Goal: Product Requirements Document - Paytm QR Scan (Hypothetical)

    Uploaded by

    Hritik Lal
    41 views2 pages
    This product requirements document outlines the goals, success metrics, user personas, user stories, and timeline for developing a Paytm QR scan feature. It includes tables for metrics, user personas prioritizing pain points, user stories and acceptance criteria, and a release plan timeline. Open issues and future scope are also documented. The goal is to make QR code payments quick by optimizing the camera scan and API response times.

    Original Description:

    Original Title

    Do

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This product requirements document outlines the goals, success metrics, user personas, user stories, and timeline for developing a Paytm QR scan feature. It includes tables for metrics, user personas prioritizing pain points, user stories and acceptance criteria, and a release plan timeline. Open issues and future scope are also documented. The goal is to make QR code payments quick by optimizing the camera scan and API response times.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    41 views2 pages

    Goal: Product Requirements Document - Paytm QR Scan (Hypothetical)

    Uploaded by

    Hritik Lal
    This product requirements document outlines the goals, success metrics, user personas, user stories, and timeline for developing a Paytm QR scan feature. It includes tables for metrics, user personas prioritizing pain points, user stories and acceptance criteria, and a release plan timeline. Open issues and future scope are also documented. The goal is to make QR code payments quick by optimizing the camera scan and API response times.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    Template Created by Doremon Den

    www.linkedin.com/company/doremon-den

    Product Requirements Document - Paytm QR Scan


    (Hypothetical)

    1. Goal
    1-2 lines in precise words.
    2. Background
    Why pursue this product? Why this goal?
    3. Success metrics
    ● Metrics list table (User activity & Business metrics).
    ● Mention North star metric (NSM).
    ● NSM can be defined at the beginning.
    ● Detailed metrics list can be defined after step 4,5,6,7.
    Metric Baseline Target Timeframe

    – – – –

    4. User persona Table


    ● As taught in the class
    ● Prioritise top pain points
    5. User story, Features & Acceptance Criteria Table

    SNo User story Feature Acceptance criteria


    1 As a busy person, I Bigger camera scan & quicker api Avg image scan should
    want to make quick call to recognise the QR code. take less than 5 seconds.
    QR code payments Max time for acceptance =
    so that I can save 8 seconds.
    time.
    2 QR scan CTA on homepage near A blindfolded test user
    thumb action. should be able to
    successfully click on the
    cta 95%+ times.

    3 – – –
    Template Created by Doremon Den
    www.linkedin.com/company/doremon-den

    6. User Journey Flow


    ● A diagram to show the user journey through all features mentioned
    7. Wireframes/Mockups
    ■ Figma link also works.
    8. Timeline/Release plan

    Feature Priority Sprint


    A 0 15th March

    B 0

    C 1

    D 2 30th March

    9. GTM (Optional)
    ● What
    ● For whom
    ● Where
    ● When

    10. Open issues


    ● Eg: Shall we change max time to 9 seconds? Close by 27th Feb.

    11. Future scope

    Feature Purpose Priority Timeframe


    Accept greater than 0 30th April
    User customisable
    95% criteria
    position of QR code
    scanner CTA.

    You might also like