This is video 11 of 15 in the Scrum with GitHub Projects series.
← Previous: Sprint Planning: Add User Stories to the Sprint · Next: Sprint Planning: The Case of the Missing Sub-Issues →
Shameless plug: Already running your team in GitHub Projects? Honest Cheetah adds test management and "when will it be done?" forecasting right inside GitHub, using the data you already have. It measures the system, not the people.
Watch the Video
Or watch it directly on YouTube: Click here
Video Description
This video is part 3 of the sprint planning process demos. In this demo, we'll start breaking the PBIs (requirements) down into actionable tasks that describe how the team plans to turn the requirements into done, working software. We'll do this using a feature in GitHub Projects called sub-issues.
BTW, this video was made using SlideSpeaker (https://www.slidespeaker.ai))
Video Info
- Duration: 4:43
- Published: February 05, 2025
Links
Scrum with GitHub Projects: The Full Series
Written series
Video series
- 1. Introduction: Scrum with GitHub Projects
- 2. Create Your First Project
- 3. The Product Backlog
- 4. Requirement Details, Markdown, and Estimates
- 5. Prioritizing Your Backlog
- 6. Demystifying Issues vs. Draft Issues
- 7. Converting Draft to "Real" Issues + Issue Types
- 8. Sprint Planning Overview
- 9. Sprint Planning & Creating Iterations
- 10. Sprint Planning: Add User Stories to the Sprint
- 11. Sprint Planning: Creating Tasks with Sub-Issues (you are here)
- 12. Sprint Planning: The Case of the Missing Sub-Issues
- 13. The Daily Scrum
- 14. Reporting & Charts
- 15. Custom Project Templates
Related:
- What's New in GitHub Projects & Issues (2026 Q4): what GitHub has shipped since this series was recorded
- Agile-ish: Lightweight Project Management with GitHub Projects (VSLive Vegas 2026)
