Abstract: Services-Oriented Architecture (SOA) provides principles for designing software applications as suites of independently deployable services with a bare minimum of centralized management of these services. Benefits of SOA include the ability to learn/combine/grow/deliver these services to please customers, anticipating failures and handling change.
If your organization struggles to deliver fast across multiple teams, fails to anticipate failure or handle rapid change, the 14 principles behind Services Oriented Architecture (SOA) applied to organizations offer a solution. We call this Service Oriented Teams (SOT).
In this session we will learn the benefits of modeling your organization in Services Oriented Teams (SOT). This includes improved information flow, ability to expose internal functionality, organizational flexibility, service re-use, lower development and management costs, configuration flexibility. We will do this by applying SOA principles and methods to Agile teams in an all-hands-on-deck workshop, using LEGO®’s as team modeling tools, and SOA methods as teams’ interfaces.
Learning Outcomes: - In this hands-on workshop, you’ll learn:
- - an introduction to Services Oriented Architecture and how applying this to organizational design helps to promote high performing, learning and highly effective teams
- - how SOTs operate as self-orchestrated ecosystems of teams that are, in fact, Complex Adaptive Systems (CAS)
- the benefits of modeling organizational structure to influence the architectural direction of your product (Conway’s law)
- - why SOA principles are as relevant for teams as they are for software architecture
- - how to design organizations to maximize flow of product - with fewer handoffs and better communication
- - why change management is no longer needed with teams’ ability to adapt “baked in” to the organization
- - how to define smart team interfaces to accelerate independent delivery
- - how SOT teams can configure/reconfigure so that other teams are not impacted
- - how to build teams to promote knowledge, knowledge reuse, and growth
- - how to focus on the bare minimum of centralized management of SOT.
- - how investing, nurturing, developing high performing teams is mandatory
- - when standard patterns for org design should be broken to remove bottlenecks
- - the benefit of avoiding Conway law silos by organizing teams in service oriented teams responsible for development and delivery
Attachments: