Culture and Norms - department-of-veterans-affairs/abd-vro GitHub Wiki

Veteran's first - always consider if what you are working on provides value to Veterans.
Help others - how can you elevate others?
Be a thoughtful and trusted partner to the VA and their contractors - treat others as you would like to be treated.
Look to make small, incremental improvement - fail (learn) fast if needed.
Enjoy your work - be proactive, flexible, resourceful and curious.
Make the team be a safe place - demonstrate kindness, empathy, respect, trust, care and assume best intentions.

Be proactive - don't wait for someone to tell you what to do.
Pair on tasks often - offer and ask to pair.
Follow Slack protocols - use threads, tag people as needed and change your status if you are away for more than a couple of hours.
Include summaries of links when adding links in tickets.
Keep documentation in Wiki - the Wiki should be the source of truth.
Create user stories for tasks that are more than a half day of work.
Create a ticket for each sprint where small ad-hoc tasks can be added for tracking and visibility.
Start with Slack threads and move to huddles if there is a lot of back and forth.

We produce quality deliverables and are proud of our work.
We have good balance.
We are always learning - we experiment and learn from each other.
We have delivered value to Veteran's - we have delivered capabilities to OCTO that other teams can benefit from.
We collaborate - we build good relationships within and outside of our team.
We work as a team towards a common goal.
VRO is deployed and is providing value.

The deliverable provides value.
The Product Manager has signed off on the deliverable after all acceptance criteria have been completed and demonstrated.
PRs have been reviewed by XXXX people and revisions based on feedback completed.
Be proud of your work - self QA/test.
Documentation is updated and can easily be followed by others.

Starting some proposals for consensus:

Document Coding Patterns that should be followed, especially if it follows best practices. The LHDI Starter Kit provides some initial code but we don't have to follow it if it causes undue friction.
Document DevOps How-To's for developers, such as Deploy to Dev and Deploy to Prod. Application developers don't need to know all the details; provide a "Quickstart" guide with references to relevant code, script, and/or configuration files. Document it once and reference it so you don't have to re-explain.
Document DevOps details that may be useful for others or demonstrate how to get the details, such as Kubernetes clusters.
Document available tools, such as DataDog monitoring, for diagnostics, monitoring, or reporting.
Document learnings or tips that takes a while to figure out, such as Docker containers (because it is involved in development and deployment) or your Development process, to help your teammates learn and include notes to remind your future self.
Radiate intent because we want to get things done quickly and openly.