KDE has evolved from one small team nearly 15 years ago to dozens of small to medium sized teams with well over a thousand people working in concert on over 5 million lines of code. This presentation looks at the processes and practices that go into keeping both the larger KDE community vibrant as well as individual teams, such as the Plasma project, moving. From legal (e.g. copyright attribution) concerns to logistics (e.g. release scheduling) to community health (e.g. events, developer sprints, codes of conduct) and of course technical excellence (e.g. peer review and design): how does a F/OSS behemoth remain agile and connected?