Leantime/app/Domain/ContentTemplates/Library/wiki/prd.yaml

key: "prd"
title: "t:templates.prd.title"
description: "t:templates.prd.description"
appliesTo: "wiki"
icon: "fa-file-lines"
author: "Leantime"
version: "1.0.0"
license: "CC0"
sector: "t:templates.documents"

wiki:
  articles:
    - title: "Product Requirements Document"
      # Inline {{ t:KEY }} substitutions handled by TranslationResolver at
      # consume time. Author / Date placeholders dropped — the hardcoded
      # version baked $author/$today into the HTML, but for a registry-
      # served template those need to be editable affordances, not baked.
      content: |
        <h1><strong>{{ t:templates.prd.title_for_prd }}<br /></strong></h1>
        <p>{{ t:templates.author }} <br />
        {{ t:templates.dates }} <br />
        {{ t:templates.status }} <span class="label label-default">{{ t:templates.status.draft }}</span><br />

        <table style="border-collapse: collapse; width: 100%;" border="1">
        <thead>
        <tr>
        <td style="width: 23.3025%;">{{ t:templates.prd.responsible }}</td>
        <td style="width: 23.3025%;">{{ t:templates.prd.approve }}</td>
        <td style="width: 23.3025%;">{{ t:templates.prd.consulted }}</td>
        <td style="width: 23.3025%;">{{ t:templates.prd.informed }}</td>
        </tr>
        </thead>
        <tbody>
        <tr>
        <td style="width: 23.3025%;">&nbsp;</td>
        <td style="width: 23.3025%;">&nbsp;</td>
        <td style="width: 23.3025%;">&nbsp;</td>
        <td style="width: 23.3025%;">&nbsp;</td>
        </tr>
        </tbody>
        </table>
        <h1>{{ t:templates.summary }}</h1>
        <h2>{{ t:templates.overview }}</h2>
        <p>{{ t:templates.prd.overview_description }}</p>

        <h2>{{ t:templates.problem }}</h2>
        <p>{{ t:templates.prd.problem_description }}</p>

        <h2>Goals (What are we working towards?)</h2>
        <p>1. Goal</p>
        <p>2. Goal</p>
        <p>3. Goal</p>
        <h2>Risks (Things that could get in the way or stop progress)</h2>
        <p>1. Risk</p>
        <p>2. Risk</p>
        <p>3. Risk</p>
        <h2>Who is the Customer &amp; Description</h2>
        <p>Who are the target personas for this product, and which is the key persona?</p>
        <table style="border-collapse: collapse; width: 50%;" border="1">
        <tbody>
        <tr style="height: 17px;">
        <td style="width: 11.8519%; height: 17px;">Customer</td>
        <td style="width: 88.1481%; height: 17px;">Description (interests, likes, demographics, where to find them)</td>
        </tr>
        <tr style="height: 17px;">
        <td style="width: 11.8519%; height: 17px;">Customer</td>
        <td style="width: 88.1481%; height: 17px;">Description (interests, likes, demographics, where to find them)</td>
        </tr>
        <tr>
        <td style="width: 11.8519%;">Customer</td>
        <td style="width: 88.1481%;">Description (interests, likes, demographics, where to find them)</td>
        </tr>
        </tbody>
        </table>
        <h2>How will the customer use the product?</h2>
        <p>Instances where various personas will use the product, in context.</p>
        <h3>Use case</h3>
        <p>Describe the use case</p>
        <h3>Use case</h3>
        <p>Describe the use case</p>
        <h3>Use case</h3>
        <p>Describe the use case</p>
        <h1>Product Details</h1>
        <p>When you&rsquo;ve locked in your One Pager, build out your PRD. Use the finalized One Pager and the following.</p>
        <h2>Features - Must haves</h2>
        <p>These are the distinct, prioritized features along with a short explanation of why this feature is important. Briefly outline the scope, the goals, and use case.</p>
        <ul>
        <li>Feature</li>
        <li>Feature</li>
        <li>Feature</li>
        </ul>
        <h2>Features - Nice to Haves</h2>
        <ul>
        <li>Feature</li>
        <li>Feature</li>
        <li>Feature</li>
        </ul>
        <h2>Features - Absolutely Not</h2>
        <p>What features have you explicitly decided not to do and why?</p>
        <ul>
        <li>Feature</li>
        <li>Feature</li>
        <li>Feature</li>
        </ul>
        <h2>Design - Any files, images, wireframes or details go here (link to idea board)</h2>
        <p>Include any needed early sketches, and throughout the project, link to the actual designs once they&rsquo;re available.</p>
        <h2>Technical Considerations - (optional)</h2>
        <p>Link to engineering technical approach document.</p>
        <h2>Success Metrics</h2>
        <p class="c8">What are the&nbsp;<a class="c35" href="https://www.google.com/url?q=https://productschool.com/blog/data-analytics/metrics-product-managers-measure/&amp;sa=D&amp;source=editors&amp;ust=1680296200488974&amp;usg=AOvVaw0DDV-fM6FNiXcUAQjmi42e">success metrics</a> that indicate you&rsquo;re achieving your internal goals for the project? How will you measure success?&nbsp;You can use any goal-setting and tracking system you prefer (OKRs, KPIs, etc).</p>
        <p>Note:<span class="c58">&nbsp;Link to Analytics requirements and approach document.</span></p>
        <h2>GTM Approach</h2>
        <p>What&rsquo;s the product messaging that your &nbsp;marketing department will use to describe this product to existing and new customers? How do you plan to launch this product to the market with marketing and sales teams?</p>
        <p>Note:<span class="c20 c63 c56 c58">&nbsp;Link to a larger GTM brief if available.</span></p>
        <h2>Open Issues</h2>
        <p>What factors do you still need to figure out? What problems may arise and how do you plan on addressing them?</p>
        <h2>Q&amp;A</h2>
        <p>What are common questions about the product along with the answers you&rsquo;ve decided? This is a good place to note key decisions.</p>
        <table style="border-collapse: collapse; width: 100.041%;" border="1">
        <thead>
        <tr>
        <td style="width: 23.3025%;">Question</td>
        <td style="width: 23.3025%;">Answer</td>
        <td style="width: 23.3025%;">Asked By</td>
        <td style="width: 23.3025%;">Answered By</td>
        </tr>
        </thead>
        <tbody>
        <tr>
        <td style="width: 23.3025%;">&nbsp;</td>
        <td style="width: 23.3025%;">&nbsp;</td>
        <td style="width: 23.3025%;">&nbsp;</td>
        <td style="width: 23.3025%;">&nbsp;</td>
        </tr>
        </tbody>
        </table>
        <h2>PRD Checklist</h2>
        <p class="c8">Here&rsquo;s a list of topics you must include in your PRD:</p>
        <ul data-type="taskList">
        <li data-type="taskItem" data-checked="false">Title</li>
        <li data-type="taskItem" data-checked="false">Author</li>
        <li data-type="taskItem" data-checked="false">Decision Log</li>
        <li data-type="taskItem" data-checked="false">Change History</li>
        <li data-type="taskItem" data-checked="false">Overview</li>
        <li data-type="taskItem" data-checked="false">Messaging</li>
        <li data-type="taskItem" data-checked="false">Personas</li>
        <li data-type="taskItem" data-checked="false">User Scenarios</li>
        <li data-type="taskItem" data-checked="false">User Stories/Features/Requirements</li>
        <li data-type="taskItem" data-checked="false">Design</li>
        <li data-type="taskItem" data-checked="false">Open Issues</li>
        <li data-type="taskItem" data-checked="false">Q&amp;A</li>
        </ul>