TP2780
Architecture for Agile Projects - Extended Training
This course starts with the story of how Agile arose to set the stage for understanding the motivation behind its continued pervasiveness. It then walks through the details of what is affected by doing Agile and who is involved with a focus on the role of the architect.
Course Details
Duration
3 days
Prerequisites
- Knowledge of and experience with architecture programs is required
- Experience with the software development process is assumed
- Familiarity with the Agile manifesto and principles is recommended
Target Audience
Those involved in Agile projects: Architects, Software Development Team Leads, Technical leads, Agile team members, Business stakeholders.
Skills Gained
- Describe where and how Agile is best used
- Identify what resources are needed
- Discuss the relationship between Agile software development and architecture
- Explain the role and deliverables of the Agile Architect
- Manage Agile architecture requirements
- Manage Agile architecture stakeholders
- Create an Agile architecture governance plan for continued success
Course Outline
- Agile in the Enterprise
- Overview
- Agile in the Enterprise
- The Beginning – Late 1960s, Early 1970s
- The Beginning – Mid 1980s
- EA Frameworks
- Today
- State of Enterprise Architecture (EA)
- Arrival of Agile
- The Stage is set – The 1990s
- The Agile Manifesto
- Software Methodologies Timeline
- Agile Characteristics
- Evolution of Agile Architecture
- Agile Needs Architecture
- Agile Projects
- Architectural Concerns
- Does Architecture Restrict Agile?
- Architecture Needs to be Agile
- Continuously Evolving Sustainable
- Overview
- Scope of Agile Architecture
- Overview
- Scope of Agile Architecture
- Look Up!
- Where to Start?
- Urgent: System and Support Structures
- The Agile Fit
- Agile Needs a Plan
- Start at the Top
- Indicators for Agile
- When Agile Does Not Work
- False Starts
- Connecting the Dots
- EA Has a Vision
- Involvement of the EA Program
- Agile Solution Architecture
- Agile Solution Architecture Vision
- Need for Agile Solution Architecture
- Architecture Domains and Agile
- Spanning Domains for Agile
- Application Architecture Vision
- Application Architecture Agile Vision
- At the Project Level
- "Traditional" Agile Team Members
- Example: Scrum Team Roles
- "Empowered" Agile Teams
- Collaboration of Architect and Team Lead
- Agile Architects as Team Players
- Architecture Challenges for Agile Teams
- Agile Solution Resource Coordination
- Overview
- Who is the Agile Architect?
- Overview
- It's All About Attitude
- Thinking in Agile
- Behaving in Agile
- Communicating in Agile
- More on Communication
- Implications of Agile on the Architect
- The Balancing Act of the Agile Architect
- Knights of the Round Table
- Teamwork
- Involvement is Ongoing
- Shared Experience
- Going on Missions
- What is Needed?
- Requirements Management
- The Big Picture
- Know the EA Vision
- Agile Requires Solution Architecture
- Work with the SA Vision
- Agile Work Updates the Enterprise
- Determine the Agile Vision
- Practice Good Architecture
- Overview
- How to do Architecture in an Agile Way
- Overview
- The Agile Manifesto and Architecture
- What is the Agile Manifesto?
- Individuals and interactions
- Working software
- Customer collaboration
- Responding to change
- Enable People to Create Success
- Agile Principles and Architecture
- What are the Agile Principles?
- Agile Principles Need Policies
- Standards Support Policies
- Agile Principles, Policies and Standards
- Principles, Policies, Standards: Connect
- Architecture Examination of the Agile Principles
- Agile Principles Make the Way Clear
- Architecture in an Agile Way
- Overview
- Agile Architecture Requirements Management
- Overview
- What is Requirements Management?
- Definition of Requirements Managements
- Architecture Requirements Management
- What is Different with Agile?
- Agile Architecture Supports Emergent Design
- Incremental or Emergent Architecture?
- Intentional Architecture!
- At the Agile Project Level
- Requirement Management and Agile
- Techniques for Agile Requirements
- Agile Architecture Requirements Process
- Architecture Comes First
- Pre-project Requirements Discovery
- Project Requirements Discovery
- New Discoveries
- Follow Through on Requirements
- Leverage the Backlog
- Backlog: Prioritized Style
- Backlog: Pool Style
- Agile Backlogs
- Agile Requirements Management Tools
- Overview
- Agile Architecture Stakeholder Management
- Overview
- What is Stakeholder Management?
- Stakeholder Management Defined
- Stakeholder Management for Architecture
- Implications of Agile Stakeholder Management
- Agile Cultures
- What is needed to make Agile work
- When Agile does not work
- Agile Teams
- Agile's Needs vs Enterprise Realities
- Agile Team Composition
- Agile Teams for the Enterprise
- Architecture Driven
- Feature Driven
- Reuse Driven
- Hybrid
- Agile Stakeholder Management Techniques
- Agile Stakeholder Challenges
- Working Together
- Schedules
- Budgets
- Overview
- Agile Architecture Governance Frameworks
- Overview
- Traditional vs Agile Governance
- Governance
- Policing vs Empowering
- Procedural vs Responsive
- Reactive vs Proactive
- Agile Governance Frameworks
- Open Agile Architecture – O-AA
- Outcome Based, Product Centric, Team-Led
- Scaled Agile Framework - SAFe
- Based on Agile Architecture Principles
- The SAFe House of Lean
- Disciplined Agile Delivery - DAD
- DAD’s Hybrid Framework
- DAD: Foundation for Scaling Agile
- Agile Governance Characteristics
- What’s common?
- People Focused
- Goal Oriented
- Lean in Nature
- Agile Governance Components
- Governance Components
- Principles and Policies
- Governance Mechanisms
- How to Engage
- Measuring and Monitoring
- Tracking and Reporting
- Architecture Inventory
- Overview
