Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Defining Master Documents #1386

Open
3 tasks
amejiamesinas opened this issue May 6, 2024 · 0 comments
Open
3 tasks

Defining Master Documents #1386

amejiamesinas opened this issue May 6, 2024 · 0 comments
Labels
feature: team operations issues relating to team processes and operations issue level I: request Smallest type of issue; Typically can be completed by one person priority: high role: product management size: 2pt Can be done in 7-12 hours
Milestone
06. Team Workflow

Comments

@amejiamesinas
Copy link
Member

amejiamesinas commented May 6, 2024 •
edited by sylvia-nam
Loading

Overview

In preparation for stakeholder review, our teams have identified the need to establish mutual understandings and definitions of documents used. We would like to discuss these at upcoming collab meetings, and establish/document official definitions (and parameters for each:

  • Source of Truth
  • UXR Glossary
  • Content Guidelines
  • Information architecture
  • Information architecture audit

Action Items

- [ ] Add this item to Fri collab meeting (Collab meeting paused in June 2024)

  • Discuss and develop definitions
  • Document definitions (in this issue)
  • Add definitions to respective team wiki pages
@amejiamesinas amejiamesinas added priority: high role: product management size: missing size: 2pt Can be done in 7-12 hours issue level II: main issue tracking level I issues; often will be tracking cross-fuctional teams tasks feature: team operations issues relating to team processes and operations labels May 6, 2024
@amejiamesinas amejiamesinas added this to the Team Workflow milestone May 6, 2024
@mariaweissman mariaweissman mentioned this issue May 7, 2024
Open
@sydneywalcoff sydneywalcoff added issue level I: request Smallest type of issue; Typically can be completed by one person and removed issue level II: main issue tracking level I issues; often will be tracking cross-fuctional teams tasks labels May 15, 2024
@sylvia-nam sylvia-nam mentioned this issue May 16, 2024
Closed
@ExperimentsInHonesty ExperimentsInHonesty moved this to Prioritized Backlog in P: EA: Project Board Jun 14, 2024
Open
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature: team operations issues relating to team processes and operations issue level I: request Smallest type of issue; Typically can be completed by one person priority: high role: product management size: 2pt Can be done in 7-12 hours
Projects
P: EA: Project Board
Status: Prioritized Backlog
Milestone
06. Team Workflow
Development

No branches or pull requests
3 participants
@sydneywalcoff @amejiamesinas @sylvia-nam