Technical scoping like a pro to build the right thing & be a superhero- Chandeep Khosa - PHP UK 2022
summary
Claims that rigorous technical scoping prevents late nights and broken projects by forcing concrete outputs: a written brief, a short discovery phase, named project owner, monthly milestones, and clear responsibilities (pen testing, UAT, content). Uses UX research, MoSCoW prioritisation and PHP/Drupal/Laravel stacks; cites 13% productivity uplift from happier teams and 38% who lower quality when treated uncivilly. Gives a real outcome: a messy brief becomes an extra 20 days statement of work to fix architecture and the demoed option wins.
AI-written summary · about
chapters (12)
- 0:00Start
- 4:16Projects I've worked on
- 6:11Unhappy people do not follow process
- 7:02Freedom & autonomy value to clients
- 7:22Our principles
- 8:56A successful partnership
- 9:58Technical scoping
- 13:36The high-level steps
- 17:11Allocate a key project owner
- 19:31Build in a discovery phase
- 21:43Build in flexibility
- 25:04UX Discovery: your partners
related talks
36mDEVELOPER ORIENTED PROJECT MANAGEMENT
29mDriving clarity in ambiguous projects
51mHow Not to Break a Simple Idea
21mNeed for speed - Moving fast as a software engineer
59mTechniques for writing high-quality code
40mHow to be a Happy Developer. Now!
32mDeveloper productivity 2.0
06mInterview to Sven Peters