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.

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

Speak to Sara about content style guide backlog prioritisation #1128

Closed
3 tasks done
Tracked by #951
davidhunter08 opened this issue Apr 14, 2021 · 2 comments
Closed
3 tasks done
Tracked by #951

Speak to Sara about content style guide backlog prioritisation #1128

davidhunter08 opened this issue Apr 14, 2021 · 2 comments
Assignees
Labels
🕙 hours A well understood issue which we expect to take less than a day to resolve 🔍 investigation meeting

Comments

@davidhunter08
Copy link
Contributor

davidhunter08 commented Apr 14, 2021

What

Speak to Sara about the recent content style guide backlog prioritisation exercise that was done with the content design community.

Why

Learning more about how the content backlog prioritisation exercise will help shape the design system backlog prioritisation exercise.

EPIC

#951

Related work

#684

Done when

  • Arrange meeting with Sara
  • Have meeting with Sara
  • Document insights on this GitHub issue
@davidhunter08 davidhunter08 added 🕙 hours A well understood issue which we expect to take less than a day to resolve 🔍 investigation meeting labels Apr 14, 2021
@davidhunter08 davidhunter08 changed the title Speak to Sara about content style guide backlog prioritisation exercise Speak to Sara about content style guide backlog prioritisation Apr 14, 2021
@davidhunter08
Copy link
Contributor Author

Agenda for the content style guide backlog prioritisation exercise:

Content style guide _community backlog prioritisation.pdf

@nancyhalladay24
Copy link
Contributor

nancyhalladay24 commented Apr 14, 2021

Notes:
The prioritisation exercise was conducted during a content style council meeting:

  • 1 1/2 hours long
  • 30ish people attended

Two stage agenda:

  • Familiarisation: ensure participants are familiar with the service manual backlog on GitHub
    • Participants viewed the backlog on their own browser whilst Sara or Tosin spoke through the items
    • Opportunity for participants to mention if there was anything missing
    • Questions
  • Prioritisation: find out the how the participants would prioritise each item in the "proposed" and "to do" columns
    • Tosin created a Qualtrics survey with all backlog items on
    • Participants were asked to complete the survey by ranking each back log item and also listing their top 5

After the meeting Sara and Tosin plotted the highest ranking items on a matrix:
IMG_0802

Readiness = how much work is already done
Impact = what participants thought had the most impact on our users

Evaluation of process:

  • they struggled to make strategic decisions ie to incorporate business needs
  • participants didn't properly understand each ticket
  • would work better if participants had longer to review and get familiar with the backlog
  • we could have done with exploring 'impact' further in retrospect. What would have a bit impact on the community, in terms of their work and needs? What would have a big impact on our end users - the people we're creating content for?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕙 hours A well understood issue which we expect to take less than a day to resolve 🔍 investigation meeting
Projects
None yet
Development

No branches or pull requests

3 participants