القائمة
Master product backlog management with prioritization frameworks, refinement techniques, estimation, and continuous backlog optimization for maximum value delivery.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Master business documentation including BRD, FRD, specifications, and technical documentation for clear communication and requirements management.
Master process modeling with BPMN, flowcharts, swimlane diagrams, and process optimization techniques for business process improvement.
Master requirements gathering techniques including interviews, workshops, observation, and documentation for effective requirement elicitation.
Master use case development with actors, scenarios, preconditions, postconditions, and detailed specifications for comprehensive requirements.
Master data visualization with chart selection, dashboard design, Tableau, Power BI, and effective data storytelling.
Master Excel for data analysis with pivot tables, formulas, Power Query, and advanced Excel techniques.
| name | product-backlog-management |
| description | Master product backlog management with prioritization frameworks, refinement techniques, estimation, and continuous backlog optimization for maximum value delivery. |
Effectively manage and prioritize product backlogs using proven frameworks and techniques to maximize value delivery and team productivity.
MoSCoW Method:
WSJF (Weighted Shortest Job First):
WSJF Score = Cost of Delay / Job Size
Cost of Delay = User/Business Value + Time Criticality + Risk Reduction
Job Size = Estimated effort (story points)
Example:
| Story | User Value | Time Critical | Risk Reduction | Total CoD | Size | WSJF |
|---|---|---|---|---|---|---|
| A | 8 | 5 | 3 | 16 | 5 | 3.2 |
| B | 10 | 8 | 5 | 23 | 13 | 1.8 |
| C | 7 | 9 | 8 | 24 | 8 | 3.0 |
RICE Scoring:
RICE Score = (Reach × Impact × Confidence) / Effort
Reach: How many users affected per time period
Impact: Impact on individual users (0.25, 0.5, 1, 2, 3)
Confidence: How certain are we (0-100%)
Effort: Person-months required
Hierarchy:
Theme (Strategic Goal)
├── Epic (Large Feature)
│ ├── User Story
│ │ ├── Task
│ │ └── Sub-task
│ └── User Story
└── Epic
Backlog Grooming Agenda:
## Priority Matrix (Value vs Effort)
High Value, Low Effort (Do First):
- User login with OAuth
- Add product rating system
- Implement email notifications
High Value, High Effort (Plan Carefully):
- Multi-language support
- Advanced analytics dashboard
- Mobile app development
Low Value, Low Effort (Do Later):
- Update footer links
- Add company logo to emails
- Minor UI tweaks
Low Value, High Effort (Avoid):
- Custom reporting engine
- Build proprietary CMS
- Complex permission system
## Release 1.0 Backlog (Target: Q2)
### Must Have (Critical Path)
1. User authentication (8 pts) - WSJF: 4.0
2. Product catalog (13 pts) - WSJF: 3.5
3. Shopping cart (8 pts) - WSJF: 3.2
4. Checkout process (13 pts) - WSJF: 3.0
5. Payment integration (13 pts) - WSJF: 2.8
**Total Must Have:** 55 points
### Should Have (High Value)
6. Wishlist (5 pts) - WSJF: 2.5
7. Product reviews (8 pts) - WSJF: 2.3
8. Order tracking (5 pts) - WSJF: 2.0
**Total Should Have:** 18 points
### Could Have (Nice to Have)
9. Recommended products (8 pts)
10. Email notifications (3 pts)
### Technical Debt
- Refactor authentication module (5 pts)
- Database optimization (3 pts)
Planning Poker Example:
Story: Implement password reset functionality
Team estimates: 3, 5, 5, 5, 8
Discussion:
- Why 3? "Simple email flow"
- Why 8? "Security concerns, token expiration, edge cases"
Consensus: 5 story points
- Email template creation
- Token generation and validation
- Security best practices
- Error handling
T-Shirt Sizing:
## Technical Debt Register
| Item | Impact | Effort | Priority | Target Sprint |
|------|--------|--------|----------|---------------|
| Upgrade to React 18 | High | 8 | P1 | Sprint 12 |
| Add unit test coverage | High | 13 | P1 | Sprint 13-14 |
| Refactor API layer | Medium | 5 | P2 | Sprint 15 |
| Update dependencies | Low | 3 | P3 | Sprint 16 |
**Rule:** Allocate 20% of sprint capacity to technical debt
## Story Dependencies
Story A: User Registration
└── Dependency: Email service integration
└── Status: In Progress
Story B: Email Verification
├── Dependency: User Registration (blocked)
└── Dependency: Email template design
└── Status: Complete
Story C: User Profile
└── Dependency: User Registration (blocked)
## [ID]: [Story Title]
**Type:** Feature | Bug | Tech Debt | Spike
**Priority:** P0 | P1 | P2 | P3
**Status:** Backlog | Ready | In Progress | Done
**User Story:**
As a [user], I want [feature], so that [value]
**Acceptance Criteria:**
- [ ] Criterion 1
- [ ] Criterion 2
**Estimation:** [points]
**Dependencies:** [List]
**Labels:** [tags]