You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.
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.
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.
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
.
.
Resources/Instructions
Webinar: How to Write Great Product Requirements by Amazon Sr PM, Elly Newell
HfLA's Website Team DS
The text was updated successfully, but these errors were encountered: