Agile in a Business to Business relationship
summary
Sony Professional reshapes a broadcaster’s media‑logistics project (tape→file, asset manager, transcoders, ESB) by embedding an agile project approach in the contract, selling work as batches of Ideal Developer Days and running monthly sprint drops with customer in planning poker. Tooling is transparent — JIRA + Zephyr boards and per‑story acceptance criteria — and five iterative releases go live; velocity sometimes slips, requiring extra drops, but the model works where trust, a committed product owner and heavy backlog grooming are present.
AI-written summary · about
chapters (24)
- 0:00Intro
- 3:25Traditional Broadcast-plugging together bits of hardware
- 5:01Headache
- 7:39The System
- 9:41Phase 2A
- 11:47Legal Framework for Fixed Price Fixed Scope contract
- 15:08Project Approach-Key Subjects
- 17:00Project Approach - The Plan
- 18:38Typical Models
- 25:56What do the Project Management methodologius say?
- 28:06Story points abstract effort
- 28:49Story points need an anchor for a commercial basis
- 29:36Define what is and isn't included in an Ideal Developer Day
- 31:18Story Level Fixed Price Fixed Scope
- 34:05Preparation
- 36:17Collaborative Test Tools
- 36:45Use Collaborative Tools
- 37:52What could possibly go wrong?
- 38:51Points Underrun
- 39:55Feeding the Backlog
- 41:40Double Backlog
- 42:14Support versus Project Work
- 44:13the right customer
- 45:10engage and be honest
related talks
05mHow we are building the agile business
35mCase Study: Seven Years of Agile
38mAgile in a Photography Studio (Mango Online)
54mA Practical Experiences implementing Business Agility at Ericsson
29mAgile on Board or How We Do It at Intel
44mCan you be agile and compliant?
50mAgile Outside IT Companies & Departments: Real Stories of Transformations
34mNative Agile Psychology of Teams and Individuals