feat(agile handbook): Add cheatsheet on how we scope projects

src/content/docs/agile-handbook/appendices/project-scoping-cheatsheet.mdx

@@ -4,4 +4,51 @@ template: basicDoc
 topics:
   - Docs agile handbook
 ---
-We use this cheatsheet
+We use this cheatsheet to help us scope projects in a consistent way.
+
+## What is this [#what_is_this]
+
++ What's the elevator pitch for the feature? What's the user value?
++ What are the most exciting tasks/stories we can tell for this feature?
++ Who is the primary audience?
++ Any docs deliverables you already have in mind?
+
+## Dates [#dates]
+
++ What are you working on right now?
++ When does this "release" (private beta, public beta, GA, etc.)?
++ If private beta, how many customers and do they need docs?
+
+## Scope [#scope]
+
++ Who will write first drafts?
++ Do you need any templates?
++ Does this need a liaison?
+
+## Resources [#resources]
+
++ Is there a test account/is this in staging?
++ Are there mockups or other resources?
++ Do you have any other collateral to share?
+
+## People [#people]
+
++ Who is the primary reviewer (and backups)?
++ Who is product manager?
++ Who is lead dev?
++ Who is the designer?
++ Who is program manager?
++ Who is the researcher? Are we doing any user research?
++ Who is the PMM?
++ Who is the support point person?
+
+## Before meeting ends [#before_meeting_ends]
+
++ Who is writing?
++ When is it due?
++ Do we need JIRAs?
++ Who is following up with who?
+
+## For more help
+
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).