Agile is anti-architecture is a Myth. In agile architecture is evolving. It's more an attitude that the best way to build systems is to keep things simple, and only add the complexity when you need it. The level of upfront architecture / design depends on the type of project. Following agile principles are around architecture and design.
Continuous attention to technical excellence and good design enhances agility.
Simplicity--the art of maximizing the amount of work not done--is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
Architecture Runway in SAFe
Architectural Runway exists when the enterprise’s platforms have sufficient, existing technological infrastructure (code) to support the implementation of the highest priority features in a near-term Program increment without excessive, delay inducing, redesign. In order to achieve some degree of runway, the enterprise must continually invest in refactoring and extending existing platform.
Eight Principles of Agile Architecture*
Principle #1: The teams that code the system also design the system.
Principle #2: Build the simplest architecture that can possibly work.
Principle #3: When in doubt, code it or model it out.
Principle #4: They build it, they test it.
Principle #5: The bigger the system, the longer the runway.
Principle #6: System Architecture is a role collaboration.
Principle #7: There is no monopoly on innovation.
Principle #8: Implement Architectural flow.
* Source: “Agile Software Requirements”, Dean Leffingwell
The Simplilearn community is a friendly, accessible place for professionals of all ages and backgrounds to engage in healthy, constructive debate and informative discussions. Get your pressing questions answered,
participate in monthly contests, create polls to get a feel for the market, build your network, and more! Pull up a chair and come join the discussion -today!