Difference between revisions of "Agile Architecture: Process and Design Tips to Support Flexible Systems"

 
(6 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
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 ==
+
 
 +
== Methods of Education ==
 +
Discussion, presentation, Q&A
 +
 
 +
 
 +
== Audience ==
 
* Developers, architects, technical leaders.
 
* Developers, architects, technical leaders.
 +
 +
 +
== Level==
 +
Advanced: While this session is lecture-oriented, it relies heavily on attendees previous experience and knowledge to anchor the concepts.
 +
  
 
== Prerequisites ==
 
== Prerequisites ==
 
* experience in building systems
 
* experience in building systems
  
== Skills Gained ==
+
 
 +
== Objectives ==
 
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
Line 20: Line 31:
 
* facilitate the creation of “agile architectural documentation”  
 
* 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 Test-Driven Development: Requirements as Executable Tests]]
 
  
== Course Content ==
+
== Outline ==
 
* Pull design: principles and examples
 
* Pull design: principles and examples
 
* Agile process tips for an agile architecture
 
* Agile process tips for an agile architecture
Line 39: Line 44:
 
* Understanding the “m-architecture”
 
* Understanding the “m-architecture”
  
==Course Level==
+
 
Advanced: While this session is lecture-oriented, it relies heavily on attendees previous experience and knowledge to anchor the concepts.
+
== Maximum Participants ==
 +
35
 +
 
 +
 
 +
== Environment - Room, Tools, Texts ==
 +
Read this: [[Course Environment - Presentation Oriented]]

Latest revision as of 12:51, 23 March 2008

Overview

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.


Methods of Education

Discussion, presentation, Q&A


Audience

  • Developers, architects, technical leaders.


Level

Advanced: While this session is lecture-oriented, it relies heavily on attendees previous experience and knowledge to anchor the concepts.


Prerequisites

  • experience in building systems


Objectives

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”


Outline

  • 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”


Maximum Participants

35


Environment - Room, Tools, Texts

Read this: Course Environment - Presentation Oriented