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

Collect and analyse priority information from a service #3633

Open
Tracked by #3574
kellylee-gds opened this issue Mar 5, 2024 · 1 comment
Open
Tracked by #3574

Collect and analyse priority information from a service #3633

kellylee-gds opened this issue Mar 5, 2024 · 1 comment

Comments

@kellylee-gds
Copy link
Contributor

kellylee-gds commented Mar 5, 2024

What

Following completion of #3571, we can now collect information on how the Design System is being used by services. By the end of the cycle we will have collected priority information from a selected service and analysed the findings. We should also begin the procurement process for any paid tooling if needed.

Why

To do a first run of this activity as a small story. We'll do this synchronously at first until we get a better idea of the methodology we apply to the process.

Who needs to work on this

Ollie, Ciandelle + another

Who needs to review this

Team leads

Done when

  • [ ]
@kellylee-gds kellylee-gds added the epic Epics are used in planning project boards to group related stories label Mar 5, 2024
@kellylee-gds kellylee-gds added small story and removed epic Epics are used in planning project boards to group related stories labels Mar 18, 2024
@kellylee-gds
Copy link
Contributor Author

Summary of our chat about processes we use to collect information on services:

  • collection of information and analysis will be a small story, not another brief (ie 3 week cycle of work)
  • we'll start small with only a handful of services explored
  • we'll do this synchronously at first until we get a better idea of the methodology we apply to the process — we'll document this
  • it'll be a triad that runs the first collection of data — developer (Ollie) + designer (Ciandelle) + another TBD
  • we'll collect all data at first then refine over time — we might find that there's data we don't use so we can delete it / stop collecting it
  • there'll be an analysis at the end of the first tranche and we'll play back the findings to the team
  • the triad will have a mini-retro to reflect on the process and suggest changes for next time
  • Ollie will further configure the tool we use so it's ready for the first set of information to be added

@kellylee-gds kellylee-gds changed the title Collect and analyse priority information from services Collect and analyse priority information from a service Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog 🏃🏼‍♀️
Development

No branches or pull requests

3 participants