-
-
Notifications
You must be signed in to change notification settings - Fork 235
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
55 additions
and
0 deletions.
There are no files selected for viewing
55 changes: 55 additions & 0 deletions
55
.github/ISSUE_TEMPLATE/pitch-for-new-feature--by-the-shape-up-book-.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,55 @@ | ||
--- | ||
name: Pitch for new feature (by the shape-up book) | ||
about: Problem, apetite, solution, drawings, rabbit holes, no-goes | ||
title: '' | ||
labels: '' | ||
assignees: '' | ||
|
||
--- | ||
|
||
### 1. Problem | ||
_What is the core problem we are trying to solve? Why does this matter?_ | ||
|
||
**Describe the problem clearly and concisely.** | ||
|
||
--- | ||
|
||
### 2. Appetite | ||
_How much time do we want to spend on this?_ | ||
|
||
**Define the timebox or effort constraints (e.g., "one cycle," "two weeks," etc.).** | ||
|
||
--- | ||
|
||
### 3. Solution | ||
_How do we imagine solving this problem?_ | ||
|
||
**Provide a high-level description of the solution without going into unnecessary details.** | ||
|
||
--- | ||
|
||
### 4. Basic Drawings | ||
_What rough sketches or wireframes illustrate the concept?_ | ||
|
||
**Include diagrams, mockups, or simple text-based explanations (e.g., ASCII art, links to sketches, or embedded images).** | ||
|
||
--- | ||
|
||
### 5. Rabbit Holes | ||
_What are the potential complexities, unknowns, or risky areas?_ | ||
|
||
**List potential scope risks, technical uncertainties, or areas where deeper investigation might be needed.** | ||
|
||
--- | ||
|
||
### 6. No-Goes | ||
_What explicitly falls outside the scope of this pitch?_ | ||
|
||
**Clarify what we are deliberately avoiding to keep the project focused.** | ||
|
||
--- | ||
|
||
### 7. Success Criteria | ||
_How will we measure success?_ | ||
|
||
**Define what success looks like for this pitch (e.g., user impact, performance improvements, feature adoption).** |