Kick-off meeting plan
0 to 5 — Why. Why we are testing and what "done" looks like: the three exit criteria. Say the line from the guide's opening.
5 to 15 — One step, live. Walk through one step end to end: find it in My Work, do it in the app, tick it, set Status and Environment in Test Runs. Then deliberately fail one and write the defect row together, pasting the ID back. Seeing it once is worth more than reading this guide twice.
15 to 25 — The statuses. Put the results table on screen and ask for a status for three scenarios: the app shows a stack trace; the project would not publish so export cannot be tried; nobody has an iPad. (Fail, Blocked, Skipped.)
25 to 35 — Roles and dependencies. Who does Setup, Label, Review, Export, and in what order. Agree how tester2 signals "project ready" and tester3 signals "labelled, over to you".
35 to 40 — Builds. Which build each person is on, the phone builds being older, the Windows SmartScreen warning. Confirm everyone can sign in on their surfaces before leaving the call.
40 to 45 — Rhythm. Smoke first, record as you go, defects the same day, one-line end-of-day post, daily numbers from you.
Per-tester onboarding checklist​
Tick every line for every tester before Round 1 starts. The Testers tab has an Onboarded column for exactly this.
- Has account credentials and has signed in on the web.
- Has installed every app they own (phone, desktop) and recorded device, OS and build on the Testers tab.
- Can open My Work with their ID and sees their steps.
- Can open My testing checklist in the app and sees the same suites.
- Has set one Status and one Environment cell in Test Runs.
- Knows where screenshots go and how to paste a link.
- Knows who to ask, and where, when a step is unclear.