{"title": "Agile Development and SAFe | Rami Sirkiä | Negotiator 95", "titleOriginal": "Ketterä kehitys ja SAFe | Rami Sirkiä | Neuvottelija 95", "episodeNumber": "95", "guest": "Rami Sirkiä", "publishedAt": "2021-08-20", "duration": "29:47", "durationIso": "PT29M47S", "youtube": "https://www.youtube.com/watch?v=VnM39rHB67A", "fiCanonical": "https://www.neuvottelija.fi/fi/episodes/107-kettera-kehitys-ja-safe-rami-sirkia-neuvottelija-95", "originalLanguage": "fi", "format": "full", "topics": ["saas_software", "leadership_governance"], "description": "Nitor's Rami Sirkiä has been taking large companies into agile operating models since the Nokia Mobile Phones era, without ever having written a line of code. The episode's load-bearing observation is counter-intuitive: the hardest part of agility is not in the teams but in management, because management no longer gets to launch large programmes and is instead asked what matters today. Sirkiä describes SAFe as a nautical chart rather than a recipe, and stresses repeatedly that it takes no position on release cadence, feedback channels or who does the work — you could in principle run waterfall with SAFe. The conversation covers the limits of the pizza team, the Agile Release Train as a team of teams, the quarterly rhythm of PI planning, DevOps as a shared culture, and flow efficiency in place of utilisation. It closes with advice that runs against his own firm's sales pitch: hire the developers yourselves.", "chapters": [{"t": "00:00", "title": "Shortening the planning horizon is the hardest thing for management", "seconds": 0}, {"t": "00:51", "title": "Rami Sirkiä of Nitor, and a father's machine-code background", "seconds": 51}, {"t": "02:43", "title": "The waterfall model, and the agile manifesto's answer to it", "seconds": 163}, {"t": "04:43", "title": "Resources, time, quality, and the cadence of sprints", "seconds": 283}, {"t": "06:11", "title": "The pizza team, and the problem of coordinating many teams", "seconds": 371}, {"t": "07:49", "title": "The Agile Release Train, a team of teams", "seconds": 469}, {"t": "08:48", "title": "SAFe's big picture is a nautical chart for management", "seconds": 528}, {"t": "09:20", "title": "OP's tribe model, and scaling SAFe into a conglomerate", "seconds": 560}, {"t": "10:31", "title": "Lean simplification, and Bosch's three hundred developers", "seconds": 631}, {"t": "12:01", "title": "PI planning and a quarterly rhythm in place of annual planning", "seconds": 721}, {"t": "13:43", "title": "A shared platform: flow efficiency against utilisation", "seconds": 823}, {"t": "15:08", "title": "DevOps is a shared culture and a shared responsibility", "seconds": 908}, {"t": "17:23", "title": "A Release Train does not dictate the release cadence", "seconds": 1043}, {"t": "19:15", "title": "How to get business people involved in development", "seconds": 1155}, {"t": "22:20", "title": "Nitor Delta, training, and business agility", "seconds": 1340}, {"t": "24:22", "title": "Service design brought code closer to the business", "seconds": 1462}, {"t": "27:49", "title": "Own capability or outsourced: the insourcing message", "seconds": 1669}, {"t": "29:19", "title": "Closing words, and SAFe version 5", "seconds": 1759}], "sourceTranscriptType": "none", "subtitleMethod": "none", "provenance": "Owner page assembled from YouTube metadata, the neuvottelija.fi episode record and the publisher's own chapter marks, translated one for one. The marks are genuine: eighteen of them, with gaps from 28 to 210 seconds, tracking the recording rather than a grid. No transcript is published here — the channel has no English caption track for this episode and the Finnish one is YouTube's automatic track. The guest is a consultant at a firm that sells agile transformation work and a named service of it is discussed, which makes parts of the episode promotional; the closing advice runs the other way. The long-form write-up in the Neuvottelija AI editions reads the 2021 argument from the far side of AI coding and finds it intact, because the case for agility rests on uncertainty rather than on the price of writing code. Recorded 20 August 2021.", "coreTheses": ["The hard part of agility is management's, not the teams': the shortened planning horizon takes away the large programme launch, which is what leadership had to hold onto.", "SAFe is a chart rather than a recipe — it takes no position on cadence, feedback or staffing, and you could run waterfall inside it.", "Flow efficiency and utilisation are different targets, and optimising the second reliably damages the first.", "A consultant telling a client to hire its own developers is advice against his own firm's interest, which is what makes it worth recording."], "slug": "ep95-kettera-kehitys-ja-safe-rami-sirkia", "guestsCanonical": ["Rami Sirkiä"], "guestPages": ["https://www.neuvottelija.com/podcast/guests/rami-sirkia/"], "page": "https://www.neuvottelija.com/podcast/episodes/ep95-kettera-kehitys-ja-safe-rami-sirkia/", "markdown": "https://www.neuvottelija.com/podcast/episodes/ep95-kettera-kehitys-ja-safe-rami-sirkia/index.md", "captions": null, "transcript": null, "videoId": "VnM39rHB67A", "dbId": null, "qaCoveragePct": 0.0, "qaSemanticVerdict": "metadata_only", "aiArticleEn": "https://www.neuvottelija.com/ai/ep95-kettera-kehitys-ja-safe-rami-sirkia/", "aiArticleFi": "https://www.neuvottelija.fi/tools/ep95-kettera-kehitys-ja-safe-rami-sirkia/"}