Agile Architecture in Swift

<p>Over the last decade, I have worked as an iOS developer in many different teams. While basically all teams described themselves as being agile, it never felt so. For most, &ldquo;agile&rdquo; had become a meaningless word, just describing a marketing term for a certification industry.</p> <p>But &ldquo;agile&rdquo; has meaning. Agility is the ability to respond to change rapidly. This means that all software projects start out agile, but we&rsquo;ve all witnessed this ability decaying. But why does this decay happen? Why did management send all of you to expensive workshops so that you are certifiable agile, and still: It doesn&rsquo;t feel agile? Your development speed is only accelerating in decreasing. Your team&rsquo;s estimates are so off that it might be more useful to develop with random story points. Who is to blame, or what is to blame?</p> <p>Maybe it is your architecture, the lack of it, or the multitude of half-baked architectural ideas in one codebase. I met a team that hadn&rsquo;t been able to release a new version of their iOS app in response to breaking changes due to an OS update &mdash; even roughly a year after the initial developer preview and ten months after the public release. Yet the team would still describe them as agile, as they were employing certain techniques usually tagged &ldquo;agile.&rdquo; But wearing Air Jordans doesn&rsquo;t transform you into Michael Jordan. Being able to buy a brush doesn&rsquo;t make you Michelangelo. And if you can&rsquo;t react to changed requirements rapidly, you aren&rsquo;t agile &mdash; no matter the certification or tooling you use. So, how can architecture help a team to become agile?</p> <p><a href="https://betterprogramming.pub/agile-architecture-in-swift-a7b5a4fc9773">Visit Now</a></p>