Open Spark450 opened 6 hours ago
Acceptance criteria
Updates on the FSOS - Design System collaboration in our monthly design system newsletter
Proposed structure
(First month) Initial Announcement:
Introduce the partnership, including the goals and expected outcomes.
Provide a brief overview of the roles each team will play in the project.
(Every month) Progress Updates:
Monthly updates on milestones reached, including but not limited to:
Sprint deliverables
User testing
Accessibility testing
Iterations
Highlight any significant challenges encountered and how they were addressed.
Feature any collaborative efforts, such as:
Cross-team meetings
Workshops
Drop-in hours
Working sessions
Pair programming (or similar)
(Every month) Team Spotlights:
Introduce members from both teams with short interviews or profiles.
Share their contributions and perspectives on the project.
(Every month) Product team takeaways:
Offer insights into the design/development process, usability/accessibility testing, decisions made, and tools or approaches used.
Showcase prototypes, code, sketches, and design iterations.
(As we start to get feedback) Impact Stories:
Highlight how the project is expected to benefit end-users.
Include any early feedback or success stories from testing or stakeholder reviews.
(At the end) Closing and Reflection:
Summarize the partnership's journey as the project nears completion.
Reflect on lessons learned and how the partnership has evolved both teams' practices.
Jira issue
Spark450
commented
6 hours ago Spark450
commented
6 hours ago
Acceptance criteria
Updates on the FSOS - Design System collaboration in our monthly design system newsletter
Proposed structure
(First month) Initial Announcement:
Introduce the partnership, including the goals and expected outcomes.
Provide a brief overview of the roles each team will play in the project.
(Every month) Progress Updates:
Monthly updates on milestones reached, including but not limited to:
Sprint deliverables
User testing
Accessibility testing
Iterations
Highlight any significant challenges encountered and how they were addressed.
Feature any collaborative efforts, such as:
Cross-team meetings
Workshops
Drop-in hours
Working sessions
Pair programming (or similar)
(Every month) Team Spotlights:
Introduce members from both teams with short interviews or profiles.
Share their contributions and perspectives on the project.
(Every month) Product team takeaways:
Offer insights into the design/development process, usability/accessibility testing, decisions made, and tools or approaches used.
Showcase prototypes, code, sketches, and design iterations.
(As we start to get feedback) Impact Stories:
Highlight how the project is expected to benefit end-users.
Include any early feedback or success stories from testing or stakeholder reviews.
(At the end) Closing and Reflection:
Summarize the partnership's journey as the project nears completion.
Reflect on lessons learned and how the partnership has evolved both teams' practices.