Agile is Anti-Architecture, Do you believe in this? or feel it is a myth?

Discussion in 'Agile and Scrum' started by Bernadette Underwood, Feb 9, 2015.

  1. Bernadette Underwood

    Joined:
    Nov 25, 2014
    Messages:
    7
    Likes Received:
    0
    Was looking into the topic, and wanted to know your viwes on same... keep posting your views please!
     
    #1
  2. Ambily Panchen Ullas

    Staff Member

    Joined:
    Jan 30, 2015
    Messages:
    29
    Likes Received:
    2
    If Architecture is complex, expensive, and hard to maintain, then I would say Agile is Anti-Architectural as Agile is simple and easy to handle.
     
    #2
  3. Om Prakash Bang

    Om Prakash Bang Well-Known Member
    Alumni

    Joined:
    Feb 18, 2015
    Messages:
    92
    Likes Received:
    39
    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.

    Agile Principles
    • 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
     
    #3
    zajakie, Shruti and MukeshShende like this.

Share This Page