Course · Build
Sprint planning & requirements gathering
User stories, acceptance criteria, and Kanban — so you understand what to build before you touch the keyboard.
Talk to us · we'll help you
Planning · Product thinking
Story · Criteria · Done
01
What
02
Why
03
Outcome
What this course is
You learn how engineers break work into sprints: user stories (“As a user I want…”), acceptance criteria, and a Kanban board (e.g. GitHub Projects). You apply this to real tasks — homework or personal projects — so each item has a clear definition of done.
Why it exists
Junior students often jump straight into coding and discover halfway that they misunderstood the goal. Freelancers who build “what was said” instead of “what was meant” lose clients. Sprint planning is the mental model shift: understand the outcome first, then write code.
What you do
- Write user stories and acceptance criteria
- Set up a Kanban board and move work through columns
- Define “done” before starting a task
- Treat each assignment or feature as a sprint ticket
You leave with
A live project board and your first clear user story tied to real work.
