Watch the Video
Or watch it directly on YouTube: Click here
Video Description
"This can't be split any further." I hear this in every refinement session. And sometimes it's true. But usually? It's not. This video gives you six diagnostic questions to unlock requirements that seem unsplittable — plus some controversial advice about spikes.
What you'll learn:
- Why teams say "can't split" (and what they really mean)
- Think team, not solo — if it's too big for one person, that's a collaboration problem
- Six questions that unlock splitting:
- What are the acceptance criteria?
- What's the core ask?
- Can we reduce scope?
- What are the unknowns?
- What would you demo?
- Technical or functional split?
- Why spikes guarantee zero value (and what to do instead)
- Technical splits vs. functional splits — and why it matters
- What "unsplittable" reveals about your team
Key insights:
- "Can't split" usually means "haven't figured out how to split yet"
- If a requirement is too big for one person, think TEAM — why are you a team if you're not delivering as a team?
- Acceptance criteria often reveal hidden requirements — six criteria might be three requirements
- Spikes by definition deliver zero value. Try "low confidence, but let's go" instead — you might actually succeed
- If it's not working after a day or two, pull the eject handles — Git feature branches protect you
- Prefer functional splits (end-to-end value) over technical splits (layer by layer)
- If chewability problems keep coming up, maybe the team composition is wrong
Previous Video: Features vs. Requirements vs. Things That Never End Next Video: What Is a Team? ► Full Playlist: https://www.youtube.com/playlist?list=PLGxFXI4dC2shCJwhTY-P2726zts26_AKF
Subscribe and enable notifications — we're building practical project management skills from the ground up.
Chapters
- 0:00 "This Can't Be Split Any Further"
- 0:30 Remember: Chewing the Apple
- 0:48 First, Let's Be Fair
- 1:25 Why Teams Say "Can't Split"
- 2:17 Think Team, Not Solo
- 3:11 Question #1: What Are the Acceptance Criteria?
- 3:58 Splitting by Acceptance Criteria
- 4:34 Question #2: What's the Core Ask?
- 5:17 Question #3: Can We Reduce Scope?
- 5:59 Question #4: What Are the Unknowns?
- 7:07 Question #5: What Would You Demo?
- 7:50 Question #6: Technical vs. Functional Split
- 9:08 The Splitting Questions Cheat Sheet
- 9:28 After You Split: The Product Owner Decision
- 10:10 When It Really Can't Be Split
- 10:56 What "Unsplittable" Reveals
- 11:45 Key Takeaways
Video Info
- Duration: 12:50
- Published: December 09, 2025
