- Specialist – can be the specialist for a specific technology or tool used in the solution
- Domain Expert – provides detailed expertise on critical topics for parts or details of complex solutions
- Technical Expert – may be an expert in key non-functional areas (user interface, security, databases, etc.) required for performance
- Independent tester – may be required for complex solution environments or for regulatory requirements (e.g. from authorities).
- Integrator – can be a separate role for integration and deployment mechanisms in complex solutions, e.g. B. DevOps teams
Disciplined Agile Delivery works in such a way that there are always primary roles (even if sometimes the architect and team leader are the same person). Then the secondary roles are added as needed.
To enable scaling across multiple teams, DAD uses the “Team of Teams” model, which is built on the “Scrum of Scrums” concept invented by Jeff Sutherland.
- DAD Agile teams meet in daily standups
- DAD Team Leads meet separately to coordinate delivery as the Product Delivery Team
- DAD Architecture Leads meet separately to coordinate the architecture and resolve dependencies, it is the architecture team
- DAD Product Owners meet separately to coordinate planning as a Product Management Team.
These teams of teams are then coordinated by a senior program manager as needed.
Starting from this basic scaling model, Disciplined Agile then extends these concepts to the organizational level. How can we mature the organization into a “learning” organization? The idea is that the Agile model is a starting model for Disciplined Agile that can be used to create a lean, agile organization that continually moves through the “stages” of development as needed.
Built-in concepts include the idea of scaling the “supporting cast.” Those in the secondary role can become their own agile teams, producing products that are used by the disciplined agile teams to deliver new products. Support teams encompass everything that could be described as “development operations” or DevOps:
- IT operations
- Customer support
- Security
- Data management
- Version management (release management)
These teams are then expanded to the entire area of product management, called “Disciplined IT”, and governance and product reuse (Commercial-off-the-shelf – COTS, Government-off-the-shelf – GOTS, Free and open -source software – FOSS) as well as enterprise architecture, human resources management and portfolio management.
Disciplined Agile goes one step further and suggests that the entire company can behave in an agile manner. Each part of the organization can be its own agile team or team of teams. This applies to sales, marketing, legal and finance departments as well as other areas of the company.
For the entire organization to be aware of its own structure, it requires “organizational assets” and the “knowledge base”. This means that the organization becomes its own market where it consumes products both internally and externally. By maintaining a central portal for access to the key information and tools needed to run the organization, each team can work without dictating to the others.
This is the realization of the ideas of an adaptive learning organization. The individual phases are listed below (abbreviated from longer forms, which you can find below
https://www.pmi.org/disciplined-agile/process/dae):
- Tribal – impulsive and driven by urgency; management “exploits” its employees
- Traditional – authoritarian, characterized by protocols and formal roles and hierarchies
- Scientific – Profit or growth oriented, driven by innovation and performance thinking
- Postmodern – Consensus-oriented, with values-based decision making
- Alive or self-organizing – Cellular management models with an evolutionary goal
Do these ideas make sense to you? What type of organization do you work in? You can learn more about the concepts and ideas of Disciplined Agile Delivery here: https://www.pmi.org/disciplined-agile