Scope Navigation to something deliverable and create a rough proposal

[CharlotteDowns]

Brief

By the end of the cycle

We have just recruited members of the wider Design System community to aid us in our work on Navigation.

Here are some of the tasks that we should aim to do with our newly formed steering group:

• steering group kick off meeting (week 1)
• run spikes to help make decisions (early cycle)
• design crits
• make prototypes and mockups (late cycle)
• write an outline of what the guidance should include (just bullet points) (late cycle)

Here are some tasks we can probably do as a team:

• decide what we're going to do (and not going to do) for v1 (early cycle)
• prepare the 1st working group review document (late cycle)

Aligns with step 3 and 4 of the contribution model:

• Scope to something deliverable
• Create a rough proposal

In the next cycle

We will send the proposal we create to the Design System working group for review. We need to make sure the contribution is useful and unique

Step 2 of the contribution model was completed in the previous cycle, Consolidate designs and form a steering group for a navigation contribution #3567 (https://github.com/alphagov/govuk-design-system/issues/3567)

Epic lead

Charlotte

Driving role(s) as referenced in the team playbook

Trang, Kelly, Mia, Brett, beeps

Supporting role(s) as referenced in the team playbook

Calvin, Anika

Further detail

• We have a squad slack group #ds-navigation, we use the canvas for tracking documents we create
• Folks have signed up to the steering group but we have not yet decided its make up or communicated that to folks who signed up
• We have a slide deck from our community workshop which documents where we are so far
• We have a website of examples that we have collected in cycle 1 (password: NavigateTheNavigation)
• We have a Padlet board of examples that were shared with us by the community
• We have a document with answers to what our community thought of our approach

Tasks

### Epic lead tasks
- [x] Help folks know what their roles are within the squad
- [x] Welcome and support new folks to the squad

### Workshop follow up (Done week 1)
- [ ] https://github.com/alphagov/govuk-design-system/issues/3681
- [ ] https://github.com/alphagov/govuk-design-system/issues/3696
- [ ] https://github.com/alphagov/govuk-design-system/issues/3683

### Steering group and crit
- [ ] https://github.com/alphagov/govuk-design-system/issues/3684
- [x] Recruit a Frontend Developer from GOV.UK One Login team to join steering group (content, design)
- [ ] https://github.com/alphagov/govuk-design-system/issues/3686
- [ ] https://github.com/alphagov/govuk-design-system/issues/3712
- [x] Create a discussion space for steering group members (design)
- [ ] https://github.com/alphagov/govuk-design-system/issues/3710
- [x] Draft discussion points for steering group crit (content)
- [x] Check that the spikes / prototypes don't have any obvious accessibility issues (accessibility, developer)
- [ ] https://github.com/alphagov/govuk-design-system/issues/3678
- [ ] https://github.com/alphagov/govuk-design-system/issues/3714
- [ ] https://github.com/alphagov/govuk-design-system/issues/3715
- [ ] https://github.com/alphagov/govuk-design-system/issues/3716

### Working group review
- [ ] https://github.com/alphagov/govuk-design-system/issues/3680
- [ ] https://github.com/alphagov/govuk-design-system/issues/3679

### Decision making
- [ ] https://github.com/alphagov/govuk-design-system/issues/3711

[trang-erskine]

Risk

• not sure how responsive the steering group will be
• discrepancy between steering group and team scope

How we work

• try and have parallel work going, in the past it was quite linear
• standup everyday
• kickoff on first monday of cycle.

[CharlotteDowns]

End of cycle aim: review feedback from crit, have something ready for a working group review (trial a one week review)

[querkmachine]

Methinks we forgot to close this one when cleaning up. Feel free to reopen if it should be.