Catalog
concept#Product#Delivery#Governance#Software Engineering

Ways of Working

Conceptual description of the processes, roles and practices teams use to organize collaboration and delivery.

Ways of Working defines the coordinated set of processes, roles and practices teams and organizations use to manage collaboration and deliver outcomes.
Established
Medium

Classification

  • Medium
  • Organizational
  • Organizational
  • Intermediate

Technical context

Issue trackers and backlog tools (e.g. Jira)Communication platforms (e.g. Slack, Teams)CI/CD pipelines for delivery automation

Principles & goals

Clear responsibilities and rolesTransparent communication and visible workContinuous improvement through retrospectives
Iterate
Enterprise, Domain, Team

Use cases & scenarios

Compromises

  • Over-bureaucratization due to overly rigid rules
  • Underestimated cultural resistance
  • Lack of metrics leads to wrong adjustments
  • Small experiments with clear success criteria
  • Regular retrospectives and adjustments
  • Use transparent metrics for steering

I/O & resources

  • Product vision and roadmap
  • Existing team and organizational structure
  • Delivery and quality metrics
  • Documented working agreements
  • Improved lead times and reduced friction
  • Governance policies for alignment and escalation

Description

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 adapts to organizational maturity and strategy.

✔

  • Better alignment between product and delivery
  • Increased predictability of releases
  • Clearer responsibilities and faster decisions

✖

  • Requires initial investment in coaching and training
  • Standardized practices can override local needs
  • Not all teams fit a single standard approach equally well

  • Lead time

    Time from request to delivery. Measures speed and flow.

  • Predictability

    Share of planned commitments met within a release or sprint.

  • Team satisfaction

    Qualitative measure of motivation and team morale.

Agile transformation in a product team

A team introduced WIP limits, daily stand-ups and retrospectives, improving throughput and predictability.

Cross-domain coordination for release planning

Multiple teams established a shared release board to synchronize dependencies and schedules.

Adopting Team Topologies for scaling

Organization used Team Topologies to define team types, interaction modes and reduce communication overhead.

1

Conduct as-is analysis of current ways of working

2

Define goals and principles with stakeholders

3

Run pilot projects, measure and scale iteratively

⚠️ Technical debt & bottlenecks

  • Unclear interfaces lead to recurring rework
  • Lack of automation increases manual coordination effort
  • Outdated toolchains block fast delivery
Inter-team dependenciesLack of clearly defined rolesInsufficient measurability of work
  • Introducing rituals without goals or metrics
  • Forcing a single model despite differing domain needs
  • Ignoring cultural barriers in globally distributed teams
  • Scaling too quickly without proven practices
  • Focusing only on processes instead of outcomes
  • Lack of measurement hinders improvements
Facilitation and coaching skillsAbility to measure and analyze delivery metricsChange management experience
Need for fast delivery cyclesTransparent decision and escalation pathsRequirements for scaling and coordination
  • • Regulatory and compliance requirements
  • • Limited coaching and training capacity
  • • Technical dependencies that affect delivery times