• /
  • ログイン
  • 無料アカウント

Project scoping cheatsheet

We use this cheatsheet to help us scope projects in a consistent way.

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

  • 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

  • Who will write first drafts?
  • Do you need any templates?
  • Does this need a liaison?

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

  • 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

  • Who is writing?
  • When is it due?
  • Do we need tickets?
  • Who is following up with who?
← Appendix: Ticket best practices

ヒント

We welcome thoughts or questions on our handbook! The easiest way to get in touch is to file a GitHub issue.

その他のヘルプ

さらに支援が必要な場合は、これらのサポートと学習リソースを確認してください:

問題を作成する
Copyright © 2020 New Relic Inc.