Appendix B. Essential Artifacts Your Team Needs
AS YOU MANAGE YOUR product development, you’ll produce many documents, guides, checklists, and other artifacts. This list is a summary of the artifacts you should expect to produce throughout your product life cycle. You will probably need them all, so they’re presented in no particular order. You can find templates for some of these artifacts available for download from www.shippinggreatness.com.
An on-call rotation—copied into a wallet-sized list of pagers and cell phone numbers.
A wiki on “Who to contact” in the case of problems, emergencies, or questions. This should include owners and contact information for legal, PR, marketing, the product team, engineering, and network operations (or whatever your production infrastructure equivalent is).
A mission statement.
A clear strategy for the next two years.
A one-page document that summarizes the who/what/why/when/ how of your product.
A product requirements document, also known as a functional spec.
A press release.
Wireframe mocks or napkin sketches.
An internal FAQ with a subset of questions tagged for an external FAQ as preliminary support content.
A communications document that covers your key message, potential dangerous questions, and responses to those questions.
T-shirts for when you launch.
A development schedule that includes testing time.
A two-year roadmap.
For infrastructure projects, an internal customer list and schedule of adoption.
For externally facing products, a trusted tester ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access