This course examines the relationship between the Agile methodology and the practice of Architecture. It is a mixture of lectures and exercises. The lectures provide instruction on the concepts and open up meaningful discussions; the exercises have students work through a case study to help deepen their knowledge. The course begins with defining what the Agile methodology and the practice of Architecture are and continues by looking at their strengths and weakness. An apparent dichotomy exists, and an exploration of industry practices demonstrate possible ways to resolve the conflict. The course ends by looking at how the best of both may be achievable.
Objectives
At the end of the training, practitioners will be able to:
§ describe the Agile methodology and its relationship to and need for Architecture
§ understand the inherent challenges of Agile and Architecture
§ discuss the ways in which the industry has been connecting Architecture and Agile
§ consider ways in which Architecture can support an Agile environment
Audience
Architects, Software Development Team Leads, Technical leads, Agile team members, Managers
Prerequisites
None.
Duration
2 days.
Outline
ENTERPRISE ARCHITECTURE (EA) PRIMER
§ Architecture
§ Architects
§ Enterprise Architecture Definitions
§ IEEE, TOGAF, & MIT Perspectives
§ Enterprise Architecture Defined
§ Architecture Framework: Foundation for a Common Vocabulary
§ Industry EA Frameworks
§ Dimensions of Architecture Scope
§ Architecture Domains
§ Time: Baseline, Target, and Transition Architectures
§ Various Solution Architecture Definitions
§ Characteristics of a Solution Architecture
§ Example Solution Architecture: SOA for Insurance
§ Solution Architecture Context
§ Solution Architecture & Domains
§ SA Spans All Domains
§ Relationship to EA Architecture Development Process
§ Solution Architecture
§ Solution Architecture Deliverables
§ EA Involvement in SA
§ Architecturally Significant
CHALLENGES WITH TRADITIONAL ARCHITECTURE
§ The Need for Senior Management Support
§ Business People Underestimate the Complexity
§ Role Clarity
§ Governance
§ Variables Outside Architecture’s Control
§ Analysis Paralysis
§ Architecture Dismissed by Agile Teams
§ Scarce Resources
§ The Challenge of Alignment
§ Rogue IT
§ There’s No ROI in Infrastructure
WHAT IS AGILE?
§ Development Methodologies of the ‘80’s and ‘90’s
§ Enterprise Architecture
§ Problems with this Approach
§ Unified Process
§ The Manifesto for Agile Development
§ Don’t Misinterpret…
§ Agile Principles: (1 of 3)
§ Agile Principles: (2 of 3)
§ Agile Principles (3 of 3)
§ Role of a Methodology in Agile
§ Agile Methodologies
§ Scrum
§ Artifact: Product Backlog
§ Artifact: Sprint Backlog
§ Artifact: Product Increment
§ Artifact: Burndown Charts
§ Activity: Sprints
§ Activity: Sprint Planning
§ Activity: Daily Scrum
§ Activities: Sprint Review and Sprint Retrospective
§ Kanban
§ XP Practices (1 of 2)
§ XP Practices (2 of 2)
CHALLENGES WITH AGILE
§ Business’ Need for Predictability
§ Shortsightedness
§ Forest and Trees
§ Difficulties with Securing a Team Member from the Business
§ The Cycle of Formalization
§ Integration Challenges
§ Operations Team Seen as a Blocker
§ Reinventing Standards
§ Possible Security Issues
§ Bias to Build over Buy
§ Team Member Criticality
§ Agile Team Member Qualifications
§ Difficulties Acquiring Proper Support
THE AGILE-ARCHITECTURE CONFLICT
§ The Two Perspectives
§ Class Discussion
HOW ARCHITECTURE FITS IN WITH AGILE
§ Common Ground
§ Building High Quality Systems
§ Solutions of Value
§ Rapid Delivery
§ Maintaining Systems Reliability
§ Design
§ Reuse
§ Discipline
§ Measurement
§ The Core Differences
§ How is Agile Even Possible?
§ Open Source
§ Code Control and Versioning
§ Test Driven Development (TDD)
§ Continuous Delivery Automation
§ Stack Overflow
§ Twitter and GitHub
§ What Does Architecture Produce That an Agile Team Needs?
§ What Should Architecture Provide to an Agile Team?
WHERE AGILE AND ARCHITECTURE CONNECT
§ The Most Popular Frameworks
§ The Zachman Framework
§ IASA
§ The Open Group Architecture Framework
§ TOGAF’s Scope
§ Which Architecture Principles are Non-Agile?
§ Which Business Principles? [2/1]
§ Which Business Principles? [2/2]
§ Which Data Principles?
§ Which Application Principles?
§ Which Technology Principles?
§ TOGAF’s Architecture Development Method
§ Development Activities in TOGAF
§ Activities TOGAF Addresses that SDLC’s Usually Don’t
§ Requirements Gathering in TOGAF
§ Discussion
§ Key TOGAF Deliverables
§ Discussion
§ Roles
§ Discussion
IS THERE AGILE ARCHITECTURE?
§ What is Agile Architecture: Definition 1
§ Agile Architecture: Definition 2
§ Which Definition is Correct?
§ What is the Problem We’re Trying to Solve Again?
§ Prioritization
§ Integration
§ What About How the Environment Has Changed?
§ So What to Do?
§ Can Architecture Be Sprinted?
§ Goals of Agile Architecture
§ Benefits
§ Agile Architecture at Work
§ Agile Architecture for Agile Software Projects
§ Scaled Agile Framework (SAFe)
§ Agile Architecture Up Front (ADUF)
§ Agile Architecture for Software
§ Agile Architecture Research
§ Agile Architecture Research Example 1
§ Agile Architecture Research Example 2
§ Agile Architecture Research Example 3
§ Agile Architecture as an EA Practice
§ Agile Architecture in the Industry
§ Agile Architecture for EA Conclusion
TOWARDS AGILE ARCHITECTURE
§ Pulling Together the Best of All of the Leading Practices
§ Enterprise Architecture [1/2]
§ Enterprise Architecture [2/2]
§ Solution Architecture
§ Agile
§ Portfolio, Program and Project Management
§ Enterprise Packaged Software
§ Open Source
§ Cloud and SaaS
§ Continuous Integration
§ So How Does This All Come Together?
§ Modeling
§ Reference Architecture
§ Organization and Governance
§ Requirements Gathering
§ Requirements Management
§ Portfolio Management
§ Deliverables
§ Architectural Compliance
§ Education
§ Stakeholder Management and Communication