Skip to content
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.

Draft a PRD for "Universal Design System Template" #489

Closed
7 of 9 tasks
allthatyazz opened this issue Feb 21, 2023 · 3 comments
Closed
7 of 9 tasks

Draft a PRD for "Universal Design System Template" #489

allthatyazz opened this issue Feb 21, 2023 · 3 comments
Assignees
Labels
! high priority B: DS Team Initatives 👤 PM Role: product manager tasks

Comments

@allthatyazz
Copy link
Contributor

allthatyazz commented Feb 21, 2023

Overview

We need to create a concrete document including key decisions and Stakeholder's requirement to build a successful design systems template for other HfLA's project to adopt.

Background

Action Items

  • Start a google doc Draft
  • Project Overview
  • Key features based on Stakeholder requirements
  • Project goals
  • Target Audience
  • Identify other useful sections and add them to the action items below
    .
    .
  • Share the Draft with the team to receive feedback
  • Share the Draft with the Stakeholder to make sure we are fully aligned with the organization's needs
  • Add the content to Wiki

Resources/Instructions

Webinar: How to Write Great Product Requirements by Amazon Sr PM, Elly Newell
HfLA's Website Team DS

@allthatyazz allthatyazz self-assigned this Feb 21, 2023
@allthatyazz allthatyazz added ! high priority 👤 PM Role: product manager tasks labels Feb 21, 2023
@allthatyazz allthatyazz added this to the Figma UI Library milestone Feb 21, 2023
@sandraberjan
Copy link

sandraberjan commented Mar 2, 2023

@allthatyazz I spent some time with the stakeholder interview from 2021. I made a document to extract some info that is clarifying for me. Thought I'd share in case it is helpful to you. Extracting Information from Stakeholder Interview

@allthatyazz
Copy link
Contributor Author

@sandraberjan thanks so much! The document is very helpful.

@allthatyazz
Copy link
Contributor Author

  • The created PRD draft has met the minimum requirements of the stakeholder to document the key features, intended audience, purposes, and goals. PMs (future PMs or other PMs across the organization) can reference this document for future use.
  • For internal usage and consensus building among team members, the content team has suggested an alignment document or project charter/scope table Draft an "Alignment Doc" / "Project Scope Table" template #496 . The new proposed format documents the key aspects of the product in each release cycle and has the potential to be added to our Wiki so we can have an archive of them over time.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
! high priority B: DS Team Initatives 👤 PM Role: product manager tasks
Projects
No open projects
Status: ✅ DONE ✅
Development

No branches or pull requests

3 participants