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

Add page on GovPress ways of working #1221

Merged
merged 2 commits into from
Nov 9, 2023
Merged

Conversation

snim2
Copy link
Contributor

@snim2 snim2 commented Nov 7, 2023

This follows some work we did earlier this year to move away from the 'squad' model to a more flexible approach to organising the unit.

Copy link

netlify bot commented Nov 7, 2023

Deploy Preview for laughing-payne-b9fbd2 ready!

Name Link
🔨 Latest commit 9278679
🔍 Latest deploy log https://app.netlify.com/sites/laughing-payne-b9fbd2/deploys/654d202a8a415e000808a0ea
😎 Deploy Preview https://deploy-preview-1221--laughing-payne-b9fbd2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@RobjS RobjS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One minor suggestion, otherwise this LGTM


Where we have larger pieces of work (>1day) that are too small for a sprinting team, these are taken on by a minimum of two developers, one of which will usually be a Tech Lead.

The team takes overall responsibility for the maintenance of our products and internal tooling. However, everyone is encouraged and expected to resolve maintenance issues when they come across them, or raise Trello cards for this team where tasks are too large to be completed in the course of other work.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion:

...for the development and maintenance of our products and internal tooling...

Hopefully we're creating new things as well as stopping the existing things breaking!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, pushed a change for that

This follows some work we did earlier this year to move away from
the 'squad' model to a more flexible approach to organising the
unit.
@snim2 snim2 force-pushed the feature/govpress-ways-of-working branch from 5f6ab82 to 9278679 Compare November 9, 2023 18:08
@snim2 snim2 merged commit c90a7ca into main Nov 9, 2023
5 checks passed
@snim2 snim2 deleted the feature/govpress-ways-of-working branch November 9, 2023 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants