Upload files to ".github/ISSUE_TEMPLATE"

2026-08-26 12:45:27 +02:00
parent f3525f3fc4
commit cef056f433
5 changed files with 128 additions and 0 deletions
@@ -0,0 +1,34 @@
+---
+name: "1. Define value stream goals"
+about: "First step for a new project — map the current process and set value stream goals."
+title: "Define value stream goals"
+labels: ["setup", "planning"]
+assignees: ""
+---
+
+## Task
+
+Produce the **current state** value stream map (and future state, if the target process is
+already known) for this project, using
+[`docs/value-stream-mapping/value_stream_map_template.odp`](../../docs/value-stream-mapping/value_stream_map_template.odp).
+
+## Steps
+
+- [ ] Identify the process boundaries: where does the value stream start and end?
+- [ ] Walk the current process step by step with the people who actually do the work
+- [ ] Fill in the current state map: process steps, cycle time, wait time, %C&A, inventory
+      between steps
+- [ ] Calculate total lead time and total cycle time
+- [ ] Identify bottlenecks, waste, and improvement opportunities
+- [ ] Draft the future state map reflecting the target process
+- [ ] Record improvement actions with an owner and a due date
+- [ ] Summarize headline metrics and actions on the
+      [Value Stream Mapping wiki page](../../wiki/Value-Stream-Mapping.md)
+- [ ] Share the map with stakeholders for feedback
+
+## Definition of done
+
+- [ ] Current (and, if applicable, future) state maps are complete in the `.odp` file
+- [ ] Metrics and action items are summarized on the wiki page
+- [ ] Stakeholders have reviewed the map
+- [ ] Findings feed into the [project specification issue](02-write-project-specification.md)
@@ -0,0 +1,38 @@
+---
+name: "2. Write project specification"
+about: "First step for a new project — complete and get approval on the project specification."
+title: "Write project specification"
+labels: ["setup", "planning"]
+assignees: ""
+---
+
+## Task
+
+Complete [`docs/PROJECT_SPECIFICATION.md`](../../docs/PROJECT_SPECIFICATION_TEMPLATE.md)
+(copied from the project specification template) for this project, and get it reviewed and
+approved by stakeholders.
+
+## Steps
+
+- [ ] Copy `docs/PROJECT_SPECIFICATION_TEMPLATE.md` to `docs/PROJECT_SPECIFICATION.md`
+- [ ] Write the summary and problem statement
+- [ ] List goals and — just as importantly — non-goals
+- [ ] Identify stakeholders and their roles
+- [ ] Define scope (in scope / out of scope)
+- [ ] Write functional and non-functional requirements
+- [ ] Sketch the architecture & design section (can stay high-level at this stage)
+- [ ] List constraints, assumptions, and risks
+- [ ] Draft milestones and a timeline
+- [ ] Define success metrics / acceptance criteria
+- [ ] Incorporate findings from the
+      [value stream mapping issue](01-define-value-stream-goals.md), if applicable
+- [ ] Circulate for review and log open questions in Section 15
+- [ ] Get sign-off from the stakeholders listed in Section 5 and set status to "Approved"
+
+## Definition of done
+
+- [ ] `docs/PROJECT_SPECIFICATION.md` exists and every section is filled in or deliberately
+      removed
+- [ ] Specification status is "Approved" and the revision history is up to date
+- [ ] Summary is copied onto the
+      [Project Specification wiki page](../../wiki/Project-Specification.md)
@@ -0,0 +1,26 @@
+---
+name: "3. Set up project wiki"
+about: "First step for a new project — publish the wiki template pages."
+title: "Set up project wiki"
+labels: ["setup", "documentation"]
+assignees: ""
+---
+
+## Task
+
+Publish the pages from [`wiki/`](../../wiki/) to the repository's actual wiki (or your team's
+wiki tool), and fill each one in for this project.
+
+## Steps
+
+- [ ] Copy `wiki/Home.md`, `Getting-Started.md`, `Architecture.md`, `Project-Specification.md`,
+      `Value-Stream-Mapping.md`, and `FAQ.md` into the live wiki
+- [ ] Fill in Home with real links (repo, issue tracker, CI) and conventions
+- [ ] Fill in Getting Started with real install/run/test instructions
+- [ ] Link the approved project specification and value stream map from their wiki pages
+- [ ] Remove the "how to use this template" notes once pages are populated
+
+## Definition of done
+
+- [ ] Wiki is live and linked from the README
+- [ ] Getting Started page is accurate enough that a new contributor can follow it unaided
@@ -0,0 +1,29 @@
+---
+name: "4. Complete new project checklist"
+about: "First step for a new project — work through the full repo/project setup checklist."
+title: "Complete new project checklist"
+labels: ["setup"]
+assignees: ""
+---
+
+## Task
+
+Work through [`docs/NEW_PROJECT_CHECKLIST.md`](../../docs/NEW_PROJECT_CHECKLIST.md) end to
+end. This issue is the tracking wrapper for that checklist — paste its sections in below (or
+just check them off in the file itself and link to the commit).
+
+## Checklist
+
+- [ ] Repository setup complete
+- [ ] Value stream map complete (see [issue 1](01-define-value-stream-goals.md))
+- [ ] Project specification approved (see [issue 2](02-write-project-specification.md))
+- [ ] Planning complete: milestones set, setup issues created, board in place
+- [ ] Environment & tooling configured (Python version, linting, tests, CI)
+- [ ] Documentation complete: README, wiki (see [issue 3](03-set-up-project-wiki.md))
+- [ ] Kickoff held with stakeholders
+
+## Definition of done
+
+- [ ] Every item in `docs/NEW_PROJECT_CHECKLIST.md` is checked or explicitly marked N/A with
+      a reason
+- [ ] The project is ready for regular development work to begin
@@ -0,0 +1 @@
+blank_issues_enabled: true