This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
DEFINE: Inspect and Refine GitHub API: Scope, Constraints and Assumptions for the groundwork on Epics, Features, and User Stories #49
Labels
ADR: Any Decision Record
#Agile
Activity: Agile
#Concept
Activity: Concept | Readme Header
#Design
Activity: Design | Readme Header
Flow: Agile Plan
#Problem
Activity: Problem Statement | Readme Header
#Project
Activity: Project Manage | Readme Header
Readme: 02 Problem
Problem Statement, Domain Driven Scenarios, Problem Concern, Motivations
Readme: 04 Concept
Concept, Real World Domain, Target Audience, App Capabilities, User Fustrastion, Solution & Idea
Readme: 05 Scope
Pre-conditions, Assumption, Constraints, Browser Compatibility
Readme: 06 Plan
Planning Tool, Sprints, Workflows, Decisions (Projects, Solutions, Developer)
Readme: 08 Design
#Scope
Activity: Scope, Constrains, Assumptions | Readme Header
W/E: Aug 04
Sprint 04: Enď
W/E: Aug 11
Sprint 05: Enď
Milestone
[DEFINE]()
: Inspect, Refine and Define GitHub API as a Candidate Datasource for Dash & Do GitHub.Idea
Context and Problem
Theme | Initiative | Epic | Story
Theme
Inspect the GitHub API
Initiative
ADR: Any Decision Records
Epic
Features
User Use Cases
App Use Cases
Stories
Dev Stories
User Stories
Research
Readme
Proof
Editorial
The text was updated successfully, but these errors were encountered: