Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One pager template #11004

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions documentation/specs/proposed/one-pager-draft.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# One Pager Template
*The objective of this one-pager is to provide clear and concise information about a feature or project to foster inclusion and collaboration by enabling anyone who is interested to learn the essential information, such as the project's goals, motivation, impact, and risks. The points and questions in each section are illustrative, they are not intended as a definite list of questions to be answered.*

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FOR THE DEV TEAM- THE DOCUMENT SERVES TO JUSTIFY THE INVESTMENT TO DELIVER THE GIVEN FEATURE.


## Description
- Short summary of the feature or effort.

## Goals and Motivation
- What are we trying to achieve and why?

## Impact
Guidance: This document should not be an OKR. Let's keep the impact general here.
Questions to consider:
- What is the impact?
- Who will benefit from the feature?
- How does success look like?
- Are there any metrics or key results that could be quantified?

## Stakeholders
Questions to consider:
- Who are the stakeholders?
- For projects with concrete stakeholders, once the project is done how does a successful handover to the stakeholder look like?

## Risks
Questions to consider:
- Will the effort or feature cause breaking changes for existing consumers?
- Are there any unknowns that might derail the effort?
- Are there any dependencies we don’t have control over?
- Is there a hard deadline that needs to be met?
- What threatens completion of the feature?
- What is the impact of failing to deliver the feature?

## Cost
Questions to consider:
- What is the estimated cost of the end-to-end effort?
- How accurate is the cost?

## Plan
- High-level milestones, with estimate effort for tasks.