Closing the Handoff Gap.Foundations
A free course for anyone who leads a team that builds an app: the shared words, the ideal loop at three team sizes, and one real feature run through it.
Every app team has a gap between what was asked for and what actually ships. This free course teaches the foundations for closing it. You will learn the shared words and industry standards that quality work rests on. These include quality, QA, testing, definition of done, defects, severity and priority. You will see what a good workflow looks like for one person building with AI coding assistants, for a small team, and for a large organisation. Then we compare that ideal with what most teams really live with, and why the two drift apart. The course ends with you running one feature through a simple loop on your own team. You can do that with a document or a spreadsheet. Only the final lesson shows tools you can use to practise it, and the course works without any of them.
By the end.What you'll be able to do.
- Explain the core quality terms (quality, QA, QC, testing, verification, validation, defect, severity, priority, definition of done) and tell them apart in real team situations.
- Compare the ideal workflow from "ask" to "release" for a solo builder, a small team and a large team, and name who is accountable for each step.
- Diagnose where your own team's workflow departs from the ideal, using a list of common friction points and three baseline numbers.
- Report an issue so it can be acted on, rate its severity and priority separately, and confirm the fix by retesting before you make a release decision.
- Choose one small first change to your team's workflow and a way to tell if it worked.
Every lesson.20 videos in 6 sections.
Open a section to see its lessons and how long each video runs.
- Welcome to the course2 min
- Part 1 introduction1 min
- Lesson 1: The handoff gap4 min
- Lesson 2: What "quality" means, and who looks after it4 min
- Lesson 3: How testing actually works5 min
- Lesson 4: Requirements you can test, and one meaning of done4 min
- Lesson 5: Defects, severity and priority, and "fixed" vs confirmed4 min
- Part 2 introduction1 min
- Lesson 6: Roles and accountability4 min
- Lesson 7: The ideal loop for a solo builder using AI tools4 min
- Lesson 8: The ideal loop for a small team4 min
- Lesson 9: The ideal loop for a large organisation4 min
- Part 3 introduction1 min
- Lesson 10: What teams are really living with4 min
- Lesson 11: Why the ideal drifts, and what keeps it alive4 min
- Part 4 introduction1 min
- Lesson 12: Find your gap and take a baseline4 min
- Lesson 13: Run one feature through the loop4 min
- Lesson 14: Practising the loop with tools4 min
- Closing and your final task1 min
Questions.Asked before starting.
- Is it really free?
- Yes. Create an account and every lesson, template and self-check is open. No card needed.
- Do I need a testing background?
- No. Every term is explained in the lesson where it is first used.
- Do I need any tools?
- No. A document or a spreadsheet is enough for every exercise and the final task. The last lesson shows tools you can practise with, as one option among several.
- How long does it take?
- About an hour of video in 14 short lessons, plus 5 to 20 minutes per exercise. The final task takes about 90 minutes over two weeks.