design-systems
design-systems copied to clipboard
Draft an "Alignment Doc" / "Project Scope Table" template
We need to have a template for an easy-to-scan document where we define a project and align on its purpose, scope, timeline, and ultimate goals.
To be successful we need to answer these questions:
-
What are the main things we all need to understand about a project before we start it?
-
What are ways we can avoid misunderstanding?
-
How can we best capture any changes in a project's direction?
Tasks:
- [x] Desk research to see what is out there that's similar
- [x] Choose a few aspects from the research that would work well for us
- [x] Draft a template of the document
- [x] Share with content design team and get feedback
- [x] Iterate based on content team feedback
- [ ] Share with entire DS team and get feedback
- [ ] Iterate based on entire DS team feedback
- [ ] Give the document a name (possible: "alignment table"; "project specs"; "Do we agree? Check")
- [ ] Use the template to help define our two projects clearly (1. Figma Kit and 2. Universal Design System)
Relevant Links: FigJam Content Brainstorm Figma Project Scope Template
@ryayyychel @michyeh I had created this issue prior to today's meeting. Would you like to use this issue for your to-do's on the "project scope table with visuals" task? Or would it be easier to start a new issue?
I don't mind either way, as long as your work is being documented and you are getting more comfortable with GitHub! :)
If you want to use this issue, just edit it to add any action steps that you want to include.
Renamed the alignment doc/project scope to: ONE PAGER
@ryayyychel @sandraberjan via the one-pager doc in my sandbox, I'm moving forward with renaming the projects:
FIGMA FOUNDATIONS: the ultimate Figma file layout guide that serves to streamline organization processes.
COMPONENT LIBRARY: a catalog of ui components, buttons, fonts created to ensure design alignment across HfLA teams.
@sandraberjan @michyeh
Updated comments on Michelle's sandbox & added comments to updated component library comment in my own sandbox.
We are moving in the right direction but need to reach consensus before officially renaming products.
Tomorrow, we will discuss:
- [x] Sandra's revision of the "project scope" design as a Project Charter
- [x] the possibility of adding the content I cut as a second section
Should I make a new issue if there's already an existing one? @sandraberjan
Should I make a new issue if there's already an existing one? @sandraberjan
Good question @michyeh ! I say go for it just to get more Github practice. You can even link to this issue :)