Explore making a 'more agile' release

[calvin-lau-sig7]

Consider a more rapid way to release the most completed and high-value work we've completed so far on Navigation. Decide on what this 'more agile' release would be with some idea of work needed.

Mural workshop to map risks and benefits and help decide best time to release Navigation

What

Current proposal includes:

• an updated Header component
• a new Navigation component
• a new Pattern, with advice on how to use the components together and generally build a good header navigation

A new proposal would

Why

There's many areas of Navigation work we'd like to be more confident on, and releasing things early is the easiest way for us to validate. This should also help us minimise the risk of making such a high-visibility update to services.

Who needs to be involved

Navigation squad

Who needs to review

Tech leads, delivery manager

### Tasks
- [x] Plan a session with the squad to determine 'more agile' release
- [x] Run a session with the squad to determine 'more agile' release
- [ ] Document and summarise next steps from the session

[CharlotteDowns]

The exercise to determine what a 'more agile' release looks like has been captured in this Mural board. We've plotted the elements of our build and guidance that we have confidence and which we have less confidence in. Items we're less confident with but would like to ship have been assigned with a 'beta' icon and we will speak about our uncertainty in the release process.

[CharlotteDowns]

What the release will look like

We are going to release things we are confident about but also include things about the contribution we are less confident about, releasing those with a 'beta' definition in GOV.UK Frontend and providing guidance within the Design System that we would like our users to help us test them.

This work should also be considered when we look at How might we ship things we are unsure about (Google document).

Things we are confident to release

• a grey bar with navigation
• a navigate a service pattern (slightly scaled back)
• a more legible version of the navigation items
• two variations of the blue bar that sit beneath the black header bar, known as 10px border-bottom on the govuk-header__container

Things we are less confident with and would like to release to gain further user insight

• a service name variant to the grey bar navigation
• a grey bar with navigation and slots

Things we are still undecided upon

• whether we should change the name of the 'grey bar' component and any accessibility considerations that will result from this
• whether after refactoring some of the 'active' conditions for navigation items that we restyle them dependant on the parameter of the viewed page (more information in Add conditional styles for different active states of the navigation items)