The Agile Scaling Model (ASM): Be as Agile as You Need to Be
summary
The Agile Scaling Model maps exactly when to extend agile from construction into a full delivery lifecycle and how to tailor practices for team size, distribution, compliance, legacy and enterprise disciplines. It claims the average sprint is two weeks while project initiation averages four weeks and transition 4.5 weeks, and that 90% do upfront modeling. Recommends automated CI dashboards (see jazz.net), static analysis, and an independent test team for pre-production integration — these reduce late defects and speed governance.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 2:50Agile Development
- 3:55Small and Colocated Teams
- 4:50The Problem
- 7:00Governance
- 11:30Scrum Life Cycle
- 14:30Scaling Factors
- 15:20Cube Walls
- 17:10Large Teams
- 18:55Compliancy
- 19:40Regulations
- 23:20Domain Complexity
- 25:30Legacy Code
- 30:20Scrum Meetings
- 36:30SelfOrganization
- 37:30Agile Modeling
- 40:05Continuous Documentation
- 41:10Appropriate Governance
- 42:50Making it Easy
- 46:30Being Polite
- 47:20Parallel Independent Testing
- 49:35Security Testing
- 50:40Independent Testing
- 51:30Large Team Stuff
- 53:15Product Owners
related talks
01h 08mAgile Scalability — Comparing Models
26mAgile Transformations are not about software
48mHow to Win and Start Contract Development Projects That Leverage Agile Values
51mWhy We Need Architects (and Architecture) on Agile Projects
01h 00mAgile Architecture
37mAre projects agile?
39mAgility in Software Architecture
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World