Skip to content

Latest commit

 

History

History
98 lines (66 loc) · 3.08 KB

team-charter-template.md

File metadata and controls

98 lines (66 loc) · 3.08 KB
Raw

[Team Name] Charter

Why we're here

Product Crew (if applicable):

i.e. Sitewide, Platform, Account Experience, Benefits Tools, Health Tools, etc - ask Chris J or your VA Product Lead if you're unsure!

Team Mission Statement:

Lorem ipsum

Product Portfolio:

List of products within your team's perview - make sure the list of products here aligns to what's captured in the List of VA.gov Products doc

Responsibilities:

High level problem space and user goals for this team

Roadmap:

Link to agile roadmap

Who we are

Team Members:

  • DSVA Product Lead: person’s name
  • Team Product Manager: person’s name
  • Additional Team Role: person’s name

How we work

Workflow + Cadence

Stand-up

Check in on people and product progress

  • Daily @ time
  • 15 min
  • 3 Question Format: What I did yesterday? What will I do today? Any impediments?

Sprint Planning

Outline work to be done this sprint in order to accomplish the team's goals

  • 1st Wednesday of every sprint @ time
  • 1 hour
  • any other notes you have

Retro

Review accomplishments from prior sprint, what went well, what can be improvemed, what questions people have, and any action items

  • 1st Wednesday of every sprint @ time
  • 30 min
  • any other notes you have

Grooming

Assess and update workload for remainder of sprint

  • 2nd Thursday of every sprint
  • 1 hour
  • any other notes you have

Issue Etiquette

For an issue to go into the Current Sprint column, it must have the following (created using the “Standard Issue Template”):

  • Estimate
  • Title that explains task
  • Description with Background and Acceptance Criteria
  • Labels: your team's labels
  • User Story (if applicable), Goal, and Acceptance Criteria
  • Nested in an Epic

All work should be validated either in staging or production, as defined by the acceptance criteria. Each ticket's last comment before closing should reflect whether validation has occurred, and by whom. By default, assign your PM to validate any tasks you are unable to validate yourself.

If there is a new RED LIGHT URGENT work request, contact the Product Manager and ask for help to work it into the sprint

Team Norms

Update as you see fit! These are some starter norms for you to consider

  • Be respectful, both online and off
  • Show your face (Webcam) at meetings / calls
  • Speak up! - everyone’s voice matters
  • We are flexible, but intentional in the way we work
  • Let’s have fun and do great work!

Slack:

This is our main means of communication with each other. Keep as much conversation in public channels as possible, to minimize duplicative and extraneous communication.

GitHub

GitHub is the single source of truth. Every body of work should be documented for tracking and capacity planning.

General things

  • Update tickets regularly. If conversations happen in Slack that are pertinent to a product or initiative, copy the useful info into GitHub/ZenHub.
  • Extra time? Explore the "Ready" column in ZenHub.