To download the mindmap output: click on the image below

• Agile Architecture
  
  • Agility vs software architecture
    
    • Focus:
      
      • software architecture
  • What
    
    • Given 'agile architecture'
      
      • architecture own by a typical scrum team of 5 to 9
    • How much up front?
      
      • How much do you know / can you know up front?
    • What's enough to get started?
    • When do we start?
    • When do we stop?
      
      • It stops when the last development ends
      • Key: you can come back on your decision
      • In some teams so has to take the decision?
    • When do we go too far?
  • What is architecture?
    
    • In general
      
      • If sth is hard to change, then it must be architecture
      • Architecture is on all levels
    • Software architecture
    • ?
      
      • Urgency, trigger, vision
      • Analysis
        
        • Start with high-level acceptance criteria
    • Categories
      
      • Functional (principal building components)
      • Technology level
        
        • Enterprise
        • Software design
          
          • classify as "architecture"?
        • Hardware
  • What go we home with?
    
    • The idea that there are a lot of ideas on this topic depending on everyone's perspective
    • Insight: architecture = what's hard to change in the system
    • A stronger feeling that it's not compatible, that agile is a paradigm
    • There are different sorts of architects, depending on the context
    • Is architecture given enough attention?
    • Architect can improve agility instead of withholding it
    • I expected an answer. Even more looking for the answer
    • No real difinition of types of architectures
    • Everything comes down to communication
    • Interesting: all those different views on architecture
      
      • there is no single definition
    • Learned about architecture and the concerns of architects
      
      • remarkable: there is no definition of 'architecture'
    • It's the team that takes care of architecture, not one person
    • Topic scope not well defined? (Architecture, agile architecture, scale, what is agile, how should you do it, ...?)
      
      • It's a difficult topic
    • It's a shared responsibility
    • Interesting thought: being agile given an architecture?
    • I think - even thought it looks like there was a lot of different disagreement - there was a general agreement
    • "The team is the architect"
    • Architecture = long term vision <-> team/development = short term, tasks at hand
    • You should deliver as fast as you can, and architecture should grow along.
      
      • Should be changeable at all times
      • Refactoring -> architecture
    • Whatever beautiful idea, if you can't communicate it ...
  • Agile architecture
    
    • Does the issue resolve when we're talking about a small team that owns the architecture?
    • Can you consider yourself being agile when accepting an architectural constraint from your boss?
      
      • (no)
    • Is there a place for "traditional" architecture in agile context?
      
      • "traditional"
        
        • UML documents, ...
        • is a constraint
        • so "dictates"
        • "thrown over the wall"
  • The agile architecture role
    
    • The human aspect
      
      • Link between hierarchy and agile architecture
        
        • Association with status
          
          • remark: if you accept hierarchy on administrative level (e.g. 'team leader') you can should accept it on a technical level (e.g. 'architect')
        • Not sharing knowledge
      • There should be a lot of communication around architecture
    • Whom do you communicate architecture to?
    • Is there an architectural role in an agile team?
      
      • Not in a sense one has the title, but in a sense that one might be more competent
      • As the sole communicator to the external world?
      • Pair architecturing?
• not agile