EPIC: Design system backlog prioritisation exercise

[davidhunter08]

What

Run a design system backlog prioritisation exercise with the NHS Digital user centred design community.

Why

We need to know where to focus our efforts as a community.

When

Every 6 months

Where

TBC

How

Workshop and/or online form.

Session notes and outcomes to be documented in the GitHub community backlog.

Desired outcomes

1. A shared understanding amongst the community of the items in the backlog
2. A prioritised ‘To do’ list of of design components and patterns
3. An increase in contribution to the community backlog

To do

Discover

• Speak to Sara about content style guide backlog prioritisation exercise
• Speak to product owners / delivery managers at NHS Digital
• Research prioritisation methods and tools
• Speak to users of the design system
• Speak to GOV.UK Design System team (Imran)
• Review findings from community contribution research
• Document and share findings

Plan / prepare

• Use findings from 'discover' to create and test a proof of concept
• Review and prep the backlog items
• Plan the session (set date, agenda etc)

Deliver

• Facilitate backlog prioritisation exercise
• Write-up and share outcomes and next steps
• Sort design system community backlog according to agreed priority #1621
• Mark design system community backlog tickets as priorities #1622

[davidhunter08]

Possible criteria for prioritising:

Impact “How many designers/teams need this thing?”
v
Effort “How ready is this thing?”

[davidhunter08]

Design system backlog prioritisation (with the community)

Some early thoughts on how we could structure the sessions.

Session 1: Backlog introduction

Purpose

1. Create a shared understanding of the purpose and benefits of the backlog
2. Get the community familiar with the backlog and backlog items
3. Gather evidence for the backlog items
4. Identify what's missing from the backlog

Agenda

• Introduction
  • What is the backlog and why do we have it
  • A quick tour of the backlog
• Exercise
  • Create a GitHub account (if you’ve not got one already)
  • Add evidence to the backlog items (eg: screenshots, key findings, links to pages)
  • Create issues for any components or patterns that are missing (playback newly created items to the group)
  • Feedback / questions
• Next steps

Session 2: Prioritisation exercise

Purpose

1. Prioritise the backlog (based on the needs of the community)

Agenda

TBD

Session 3: Prioritisation exercise playback

Purpose

1. Playback results of the prioritisation exercise to the community
2. Encourage contribution

Agenda

TBD

[henocookie]

Would be great if @ambchang, @teodorastraianu1, @danjohnstonUX and myself could get a catch-up once @karlgoldstraw is back from leave on the latest around this EPIC 😀

[sarawilcox]

Would be good to mark priorities in the backlog. We have a "priority" label. A couple of items are already marked as priorities after the content backlog prioritisation exercise.

[henocookie]

@karlgoldstraw is this something you could have a key focus on to create handover notes or schedule some time with me, @ambchang @danjohnstonUX and @sarawilcox so we know what work has happened and what might still be needed to be done?

[sarawilcox]

Yes please, it would be good to have a record of how you went about it (with links) in case we want to run the exercise again.

[georginaplatt]

Confluence notes on the exercise: - Community prioritisation exercise