---
title: Project scoping cheatsheet
source: https://docs.newrelic.com/docs/agile-handbook/appendices/project-scoping-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" (limited preview, public preview, or general availability)?
-   If limited preview, 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 tickets?
-   Who is following up with who?

[← Appendix: Ticket best practices](https://docs.newrelic.com/docs/agile-handbook/appendices/ticket-best-practices/)

[Appendix: Backlog review →](https://docs.newrelic.com/docs/agile-handbook/appendices/backlog-review/)