Skip to content

Commit 604b380

Browse files
sayuru-akashsayuru-akash
committed
feat: Initialize comprehensive PM/BA lifecycle repository including curriculum, example project, toolkit, and career resources.
0 parents  commit 604b380

57 files changed

Lines changed: 15367 additions & 0 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.github/ISSUE_TEMPLATE/01-user-story.md‎

Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
---
2+
name: User Story
3+
about: Propose a new feature from the user's perspective
4+
title: "[STORY] "
5+
labels: user-story, needs-refinement
6+
assignees: ""
7+
---
8+
9+
## User Story
10+
11+
**As a** [type of user],
12+
**I want** [goal/desire],
13+
**So that** [benefit/value].
14+
15+
---
16+
17+
## Acceptance Criteria
18+
19+
- [ ] **GIVEN** [context/precondition],
20+
**WHEN** [action],
21+
**THEN** [expected outcome]
22+
23+
- [ ] **GIVEN** [another scenario],
24+
**WHEN** [action],
25+
**THEN** [expected outcome]
26+
27+
---
28+
29+
## Business Value
30+
31+
**Why is this important?** [Describe the business impact or user pain point this solves]
32+
33+
**Target Users:** [Who benefits from this? E.g., diners, restaurant managers, both]
34+
35+
**Success Metric:** [How will we measure if this is successful? E.g., "Increase booking conversion by 5%"]
36+
37+
---
38+
39+
## Design/UX Notes
40+
41+
[Optional: Attach Figma links, wireframes, or describe expected user flow]
42+
43+
**User Flow:**
44+
45+
1. User navigates to...
46+
2. User sees...
47+
3. User clicks...
48+
49+
---
50+
51+
## Technical Notes (For Engineering)
52+
53+
[Optional: Mention API endpoints, database changes, third-party integrations]
54+
55+
**Dependencies:**
56+
57+
- [ ] New API endpoint needed?
58+
- [ ] Database migration required?
59+
- [ ] Third-party service (SMS, payment, etc.)?
60+
61+
**Estimated Complexity:** [Small / Medium / Large]
62+
63+
---
64+
65+
## Open Questions
66+
67+
[List any unknowns that need clarification before this can be built]
68+
69+
1. Should this work for guest users or only logged-in users?
70+
2. What happens if [edge case]?
71+
72+
---
73+
74+
## INVEST Checklist
75+
76+
Before marking this story as "ready for development," verify it meets INVEST criteria:
77+
78+
- [ ] **I**ndependent - Can be developed without dependencies on other stories
79+
- [ ] **N**egotiable - Details can be discussed/refined
80+
- [ ] **V**aluable - Delivers clear value to users or business
81+
- [ ] **E**stimable - Engineering team can estimate effort (story points)
82+
- [ ] **S**mall - Can be completed in one sprint (1-2 weeks)
83+
- [ ] **T**estable - Has clear pass/fail criteria
84+
85+
---
86+
87+
## Related Issues/PRs
88+
89+
[Link to related user stories, epics, bugs, or pull requests]
90+
91+
- Related to #
92+
- Blocks #
93+
- Blocked by #

‎.github/ISSUE_TEMPLATE/02-bug-report.md‎

Lines changed: 164 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,164 @@
1+
---
2+
name: Bug Report
3+
about: Report a defect or issue
4+
title: "[BUG] "
5+
labels: bug, needs-triage
6+
assignees: ""
7+
---
8+
9+
## Bug Summary
10+
11+
[One-sentence description of the problem]
12+
13+
---
14+
15+
## Severity
16+
17+
- [ ] **Critical** - System down, data loss, security vulnerability
18+
- [ ] **High** - Major feature broken, impacts many users
19+
- [ ] **Medium** - Feature partially broken, workaround exists
20+
- [ ] **Low** - Cosmetic issue, minimal impact
21+
22+
---
23+
24+
## Environment
25+
26+
**Where did this occur?**
27+
28+
- [ ] Production
29+
- [ ] Staging
30+
- [ ] Local development
31+
32+
**Browser/Device:** [e.g., Chrome 118, Safari iOS 17, Android Chrome]
33+
**Operating System:** [e.g., macOS 14.0, Windows 11, iOS 17]
34+
**User Type:** [e.g., logged-in user, guest, restaurant partner]
35+
36+
---
37+
38+
## Steps to Reproduce
39+
40+
[Provide exact steps to consistently reproduce the issue]
41+
42+
1. Navigate to [URL]
43+
2. Click on [button/element]
44+
3. Enter [data] into [field]
45+
4. Observe [unexpected behavior]
46+
47+
---
48+
49+
## Expected Behavior
50+
51+
**What should have happened?**
52+
53+
[Describe the correct/intended behavior]
54+
55+
---
56+
57+
## Actual Behavior
58+
59+
**What actually happened?**
60+
61+
[Describe the bug/error]
62+
63+
**Error Message (if any):**
64+
65+
```
66+
[Paste exact error text or screenshot]
67+
```
68+
69+
---
70+
71+
## Screenshots/Videos
72+
73+
[Attach screenshots or screen recordings to help illustrate the issue]
74+
75+
**Before:** [What it should look like]
76+
**After:** [What it looks like now (broken)]
77+
78+
---
79+
80+
## Impact
81+
82+
**Who is affected?**
83+
84+
- [ ] All users
85+
- [ ] Specific user segment: [e.g., only iOS users, only restaurant partners]
86+
- [ ] Internal team only
87+
88+
**How many users?** [Estimate if possible, e.g., "~500 users/day hit this page"]
89+
90+
**Workaround available?**
91+
92+
- [ ] Yes - [Describe workaround]
93+
- [ ] No
94+
95+
---
96+
97+
## Technical Details (For Engineering)
98+
99+
**Browser Console Errors:**
100+
101+
```
102+
[Paste JavaScript errors from browser console]
103+
```
104+
105+
**Network Request (if API-related):**
106+
107+
- **Endpoint:** `POST /api/v1/bookings`
108+
- **Status Code:** `500 Internal Server Error`
109+
- **Request Body:**
110+
111+
```json
112+
{
113+
"restaurant_id": 123,
114+
"booking_date": "2026-02-15"
115+
}
116+
```
117+
118+
- **Response:**
119+
120+
```json
121+
{
122+
"error": "Database connection timeout"
123+
}
124+
```
125+
126+
**Server Logs (if available):**
127+
128+
```
129+
[Paste relevant backend logs with timestamp]
130+
```
131+
132+
---
133+
134+
## Root Cause (If Known)
135+
136+
[Optional: If you have insights into why this is happening, note them here]
137+
138+
**Suspected Issue:** [e.g., race condition, null pointer, timeout]
139+
140+
---
141+
142+
## Suggested Fix (Optional)
143+
144+
[If you have ideas on how to fix it, share them]
145+
146+
---
147+
148+
## Related Issues/PRs
149+
150+
- Duplicate of #
151+
- Related to #
152+
- Introduced in PR #
153+
154+
---
155+
156+
## Checklist for QA/Engineering
157+
158+
- [ ] Bug confirmed (can reproduce)
159+
- [ ] Severity assigned
160+
- [ ] Owner assigned
161+
- [ ] Target fix version set
162+
- [ ] Fix verified in staging
163+
- [ ] Fix deployed to production
164+
- [ ] Regression test added

‎.github/ISSUE_TEMPLATE/03-feature-request.md‎

Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
---
2+
name: Feature Request
3+
about: Suggest a new feature or enhancement
4+
title: "[FEATURE] "
5+
labels: enhancement, needs-review
6+
assignees: ""
7+
---
8+
9+
## Problem Statement
10+
11+
**What problem does this solve?**
12+
13+
[Describe the user pain point or business need that motivates this request]
14+
15+
**Who is affected?**
16+
17+
- [ ] Diners
18+
- [ ] Restaurant partners
19+
- [ ] Internal team
20+
- [ ] Other: ****\_\_****
21+
22+
---
23+
24+
## Proposed Solution
25+
26+
**What do you envision?**
27+
28+
[Describe your ideal solution in detail]
29+
30+
**User Flow:**
31+
32+
1. User starts from...
33+
2. User sees/does...
34+
3. User achieves...
35+
36+
**Example:** [If you have a real-world example from another product, share it]
37+
38+
---
39+
40+
## Alternatives Considered
41+
42+
[What other approaches did you think about? Why did you reject them?]
43+
44+
**Option A:** [Brief description]
45+
**Pros:**
46+
**Cons:**
47+
48+
**Option B:** [Brief description]
49+
**Pros:**
50+
**Cons:**
51+
52+
---
53+
54+
## Success Metrics
55+
56+
**How will we know if this is successful?**
57+
58+
[Define measurable outcomes]
59+
60+
- **Metric 1:** [e.g., "Increase repeat bookings by 15%"]
61+
- **Metric 2:** [e.g., "Reduce support tickets by 10%"]
62+
63+
---
64+
65+
## Priority
66+
67+
**How important is this?**
68+
69+
- [ ] **P0 (Must-Have)** - Critical for business, blocks other work
70+
- [ ] **P1 (Should-Have)** - Important, should be in next quarter
71+
- [ ] **P2 (Nice-to-Have)** - Valuable, but not urgent
72+
- [ ] **P3 (Low Priority)** - Wishlist item
73+
74+
**Justification:** [Why did you choose this priority?]
75+
76+
---
77+
78+
## Effort Estimate (Optional)
79+
80+
[If you have a sense of complexity, share it]
81+
82+
- [ ] Small (1-3 days)
83+
- [ ] Medium (1 week)
84+
- [ ] Large (2-4 weeks)
85+
- [ ] Epic (1-3 months)
86+
87+
---
88+
89+
## Dependencies
90+
91+
**What needs to happen first?**
92+
93+
- [ ] Design mockups needed
94+
- [ ] Legal/compliance review
95+
- [ ] Third-party API integration
96+
- [ ] Database schema changes
97+
- [ ] Other: ****\_\_****
98+
99+
---
100+
101+
## Open Questions
102+
103+
[List any unknowns or items that need discussion]
104+
105+
1. Should this work for guest users or only logged-in users?
106+
2. Do we need A/B testing before full rollout?
107+
3. How does this interact with existing feature X?
108+
109+
---
110+
111+
## Mockups/Designs
112+
113+
[Attach wireframes, screenshots, or Figma links]
114+
115+
[Drag and drop images here]
116+
117+
---
118+
119+
## Related Issues
120+
121+
- Related to #
122+
- Blocks #
123+
- Blocked by #

0 commit comments

Comments
 (0)