How to Win and Start Contract Development Projects That Leverage Agile Values
summary
Explains how to win and start contract software projects that actually deliver Agile value by requiring a one-month assessment phase, insisting the client product owner commits about three half-days per week, and forming an initial MVP backbone team that delivers a runnable spine with CI/CD before scaling. Describes a successful mobile order-and-pay rollout using one-week sprints and staged handovers to a Vietnam/Da Nang team, and recounts failures such as scope ballooning (example: 260 points over 9 sprints with velocity dropping to 30), gaps in team building, and rewrite-versus-refactor choices that led to burnout.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:02Agile home development
- 7:14Good vs bad projects
- 14:56Convenience store chain case
- 17:04Failed home center project
- 19:08Discount chain renewal
- 26:33Ten rules for winning contracts
- 30:46Assessment phase importance
- 35:22Refactoring vs renewal
- 36:24Phase separation for new projects
- 40:15Left-wing approach for first release
- 42:25Kano model for quality
- 44:52Handing over to teams
- 45:55Summary
- 47:18Q&A
related talks
40mAgile Software Development: Practice and Analytics
57mAgile Contracts for Software Consultants
11mLeading Agile Teams to Success: Lessons from the Trenches
41mProduct Owner & Developer: An Unexpected Journey
26mGet agile and don't die trying
39mScrum at Scale
32mA Tale of Two Cities - Early Adoption Stories
51mWhy Scaling Agile Doesn't Work