Difference between revisions of "Agile Architecture: Process and Design Tips to Support Flexible Systems"
(New page: Course Name Craig Larman’s Agile Architecture: Process and Design Tips for Flexible Systems Brief Course Description 1 day. This one-day seminar introduces you to the techniques and tips...) |
|||
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
1 day. | 1 day. | ||
+ | |||
This one-day seminar introduces you to the techniques and tips to build agile architectures. This spans not only design tips, but also related agile method practices. You will learn a set of lightweight analysis tools to better understand the domain, the constraints, and variation points. You will learn simple collaborative techniques to help align the business goals of product management with the architectural goals. We will explore the concept of “pull design” in software development, and design principles that enhance agility at an architectural level. | This one-day seminar introduces you to the techniques and tips to build agile architectures. This spans not only design tips, but also related agile method practices. You will learn a set of lightweight analysis tools to better understand the domain, the constraints, and variation points. You will learn simple collaborative techniques to help align the business goals of product management with the architectural goals. We will explore the concept of “pull design” in software development, and design principles that enhance agility at an architectural level. | ||
You will leave with an understanding of the major techniques and guidelines for agile architectures, and pointers to useful learning aids to quicken your journey. | You will leave with an understanding of the major techniques and guidelines for agile architectures, and pointers to useful learning aids to quicken your journey. | ||
− | + | ||
− | + | == Who can benefit == | |
− | Who can benefit | + | * Developers, architects, technical leaders. |
− | Developers, architects, technical leaders. | + | |
− | Prerequisites | + | == Prerequisites == |
− | experience in building systems | + | * experience in building systems |
− | Skills Gained | + | |
+ | == Skills Gained == | ||
Upon completion of this course, students should be able to: | Upon completion of this course, students should be able to: | ||
− | apply lightweight domain and architectural analysis | + | * apply lightweight domain and architectural analysis |
− | describe dozens of design and agile methods tips for developing an agile architecture | + | * describe dozens of design and agile methods tips for developing an agile architecture |
− | facilitate design workshops | + | * facilitate design workshops |
− | work with product management to align business and architectural goals | + | * work with product management to align business and architectural goals |
− | facilitate the creation of “agile architectural documentation” | + | * facilitate the creation of “agile architectural documentation” |
− | Related Courses | + | |
+ | == Related Courses == | ||
Before | Before | ||
− | + | * Agile Software Development: Hands-on Practices, Principles, Agile Modeling, and TDD | |
− | + | * Agile TDD and Refactoring | |
− | + | * Agile Design and Modeling for Advanced Object Design with Patterns | |
− | + | * Agile Acceptance TDD: Requirements as Executable Tests | |
After | After | ||
− | Course Content | + | == Course Content == |
− | Pull design: principles and examples | + | * Pull design: principles and examples |
− | Agile process tips for an agile architecture | + | * Agile process tips for an agile architecture |
− | Agile SAD workshops: technical memos and N+1 sketch-views | + | * Agile SAD workshops: technical memos and N+1 sketch-views |
− | Lightweight domain modeling and architectural analysis | + | * Lightweight domain modeling and architectural analysis |
− | Release and iteration planning with product management | + | * Release and iteration planning with product management |
− | Tiger teams and master programmers | + | * Tiger teams and master programmers |
− | Architects as teachers | + | * Architects as teachers |
− | Architectural CoPs | + | * Architectural CoPs |
− | HAL and simulation layers | + | * HAL and simulation layers |
− | Understanding the “m-architecture” | + | * Understanding the “m-architecture” |
Revision as of 05:48, 6 November 2007
1 day.
This one-day seminar introduces you to the techniques and tips to build agile architectures. This spans not only design tips, but also related agile method practices. You will learn a set of lightweight analysis tools to better understand the domain, the constraints, and variation points. You will learn simple collaborative techniques to help align the business goals of product management with the architectural goals. We will explore the concept of “pull design” in software development, and design principles that enhance agility at an architectural level. You will leave with an understanding of the major techniques and guidelines for agile architectures, and pointers to useful learning aids to quicken your journey.
Who can benefit
- Developers, architects, technical leaders.
Prerequisites
- experience in building systems
Skills Gained
Upon completion of this course, students should be able to:
- apply lightweight domain and architectural analysis
- describe dozens of design and agile methods tips for developing an agile architecture
- facilitate design workshops
- work with product management to align business and architectural goals
- facilitate the creation of “agile architectural documentation”
Related Courses
Before
- Agile Software Development: Hands-on Practices, Principles, Agile Modeling, and TDD
- Agile TDD and Refactoring
- Agile Design and Modeling for Advanced Object Design with Patterns
- Agile Acceptance TDD: Requirements as Executable Tests
After
Course Content
- Pull design: principles and examples
- Agile process tips for an agile architecture
- Agile SAD workshops: technical memos and N+1 sketch-views
- Lightweight domain modeling and architectural analysis
- Release and iteration planning with product management
- Tiger teams and master programmers
- Architects as teachers
- Architectural CoPs
- HAL and simulation layers
- Understanding the “m-architecture”