Loading content
Ways of Working defines the coordinated set of processes, roles and practices teams and organizations use to manage collaboration and deliver outcomes. It includes principles, team structures, communication patterns and decision-making processes. The aim is improved efficiency, adaptability and clear accountability across product development and delivery; it…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Ways of Working describes the deliberately designed practices, roles, processes, and tools through which a team achieves results together.
The expression was shaped by agile software development and team research. The 2001 Agile Manifesto stated central principles for collaboration; approaches such as Team Topologies later applied them to team boundaries and team interactions.
Treat a team as a social and technical system: agree how work starts, decisions are made, information flows, and interfaces are maintained.
Working practices are made explicit and adapted regularly.
Roles, routines, and interfaces guide the flow of work and decisions.
Good ways of working combine autonomy with clear responsibility and communication paths.
Ways of Working helps teams adapt collaboration to goals, dependencies, and the pace of change.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.