{"id":7838,"date":"2025-11-29T06:57:06","date_gmt":"2025-11-29T05:57:06","guid":{"rendered":"https:\/\/web-dev-weissblau.de\/microconsult\/?p=7838"},"modified":"2026-02-13T15:36:00","modified_gmt":"2026-02-13T14:36:00","slug":"scaling-agile","status":"publish","type":"post","link":"https:\/\/www.microconsult.de\/en\/scaling-agile\/","title":{"rendered":"Scaling Agile!"},"content":{"rendered":"

Agile frameworks at the enterprise level<\/h2>\n

Author: Urs B\u00f6hm, Noser Engineering<\/p>\n

Contribution \u2013 Embedded Software Engineering Congress 2017<\/h3>\n

Agile Teams<\/h2>\n

With the turn of the millennium, the Agile Manifesto and, consequently, agile methods such as Scrum and Kanban became established in software development. Traditional methods like the Waterfall and V-models are increasingly being relegated to the background and niche applications. New, young, and well-trained developers and managers expect agile methods for both projects and line development tasks.<\/p>\n

Scrum explicitly addresses the team size of 7 plus or minus 2. This has proven effective since the time of the Roman legions. Back then, 8 legionaries formed a "contubernium" (tent group), who worked and lived together in a spirit of sworn unity.<\/p>\n

For larger software projects, a team is often too small or cannot represent all the necessary skills. Kanban development groups can grow somewhat larger, but then you lose team benefits and are still somewhat limited.<\/p>\n

This is where scaling comes into play. What do you do when you're building systems that require dozens, hundreds, or more people, but still want to leverage the strengths of individual teams?<\/p>\n

You have to scale!<\/h2>\n

I will discuss three different proven frameworks:<\/p>\n