Add docs on agile roles | Agile handbook

src/content/docs/agile-handbook/guide/agile-roles.mdx

@@ -0,0 +1,48 @@
+---
+title: "Agile roles"
+template: basicDoc
+topics:
+  - Docs agile handbook
+---
+Like most agile teams, we divide the team into team members, scrum masters, and managers. Because a content team has different needs than an engineering team, though, we ask somewhat different things of each of those roles:
+
+- We combine the role of team manager and product manager into one person.
+- Each writer is responsible for "liaisonships" where they track work across a particular product or feature and bring in appropriate stories.
+- We don't expect scrum masters to clear blockers (that's a manager's job), and scrum mastering is not a full-time job.
+
+## Team member [#team_member]
+
+Team members are responsible for:
+
+- Doing writing work.
+- Improving the team's processes and how we work together.
+- Writing stories for sprints in accordance with their work (via laisionships, SME conversations, hero work, etc.). The person who nominates a story will also present it during sprint planning. Each story should have a [complete list of criteria, SMEs, and resources](3379_INSERT_LINK_HERE). See [Jira best practices](3379_INSERT_LINK_HERE) for additional story best practices.
+- Most team members will be assigned one or more [Liaisonships](3379_INSERT_LINK_HERE) (project assignments). Liaisons are responsible for nominating stories for sprints from other teams.
+
+## Scrum master [#scrum_master]
+
+The scrum master is a custodian of the sprint process, and the MC for sprint meetings.
+
+- **In [sprint planning](3379_INSERT_LINK_HERE)**: Scrum master leads conversation, tracks discussion time, adds point values to stories, and organizes/ranks sprint candidates in real time. All stories in sprint planning should be presented to the team by the story reporter or the person who nominated the story for a sprint, not the scrum master. 
+- **In [retros](3379_INSERT_LINK_HERE)**: The scrum master puts together the retro slide deck, facilitates discussion, and takes notes. The scrum master may also compile sprint metrics. 
+- **In [backlog grooming](3379_INSERT_LINK_HERE)**: Ideally, both the scrum master and manager are always present for backlog grooming, and all other team members are optional. If either the manager or scrum master are out of office, the other attends grooming with at least one other team member. If both are out of office, backlog grooming may be postponed.
+
+Each squad has a scrum master. The scrum master is not responsible for unblocking stories or communicating with stakeholders on behalf of the team (this work belongs to individual writers and their manager). We believe this lets the business have a single point of accountability (managers) for decisions, and ensures scrum masters have hands-on experience of what it's like to be a writer.
+
+## Tech Docs managers (and product owner) [#team_managers]
+
+Each squad has a manager---or perhaps you could say each manager has a squad. Either way, the manager's role is to prioritize the right work for the business, maintain a healthy workload, and help escalate when a writer needs help.
+
+The managers are responsible for understanding how our entire body of work serves the organization, and making informed decisions about our velocity and workload. The manager engages with other teams to know which features may be coming into the pipeline and has a general understanding of work that may be in future sprints. This lets them make final priority decisions for the team and be accountable to the business for those tradeoffs. 
+
+The manager is also responsible for assigning liaisonships and ensuring we're covering the portfolio. They'll also work with other teams to unblock writers when needed. 
+
+## Key stakeholders [#key_stakeholders]
+
+Key stakeholders include executives, PMs, engineering, and designers. Writers work with the stakeholders to know when new work is coming, and to communicate documentation needs/timelines. 
+
+We should ensure our stakeholders know that we work in two week sprints, so that they can give us adequate lead time and get their documentation needs met.
+
+## For more help
+
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).

src/nav/docs-agile-handbook.yml

@@ -11,3 +11,5 @@ pages:
       path: /docs/agile-handbook/guide/agile-sprints-profusion-of-terms
     - title: "Key agile principles"
       path: /docs/agile-handbook/guide/key-agile-principles
+    - title: "Agile roles"
+      path: /docs/agile-handbook/guide/agile-roles