Catalog
concept#Product#Delivery#Governance#Software Engineering

Agile Ways of Working

A set of principles and practices that enable teams to deliver value adaptively and incrementally.

Agile Ways of Working describes principles, practices and roles that enable teams to deliver value adaptively and incrementally.
Established
Medium

Classification

  • Medium
  • Organizational
  • Organizational
  • Intermediate

Technical context

Issue tracking tools (e.g. Jira)CI/CD pipelines for continuous deliveryCommunication platforms (e.g. Teams, Slack)

Principles & goals

Customer focus and continuous feedbackIncremental delivery and short iterationsTeam empowerment and transparency
Iterate
Enterprise, Domain, Team

Use cases & scenarios

Compromises

  • Superficial implementation without real cultural change
  • Using metrics as pressure instead of learning
  • Loss of technical quality due to excessive pace
  • Short iterations and clear Definition of Done
  • Regular retrospectives as a learning mechanism
  • Proactively address technical debt

I/O & resources

  • Product vision and coarse roadmap
  • Prioritized backlog
  • Cross-functional team and infrastructure
  • Incremental releases with measurable customer value
  • Improved predictability and shorter feedback cycles
  • Ongoing process improvements via retrospectives

Description

Agile Ways of Working describes principles, practices and roles that enable teams to deliver value adaptively and incrementally. It includes frameworks such as Scrum and Kanban and emphasizes customer focus, short feedback cycles and continuous improvement across product and delivery processes. Teams use metrics and retrospectives to adapt.

✔

  • Faster response to market needs
  • Higher customer satisfaction via early feedback
  • Better prioritization and focus on value

✖

  • Requires organizational change and leadership support
  • Can lead to instability without technical excellence
  • Scaling requires explicit coordination and governance

  • Cycle Time

    Measures time from start to completion of a work item; important to identify bottlenecks.

  • Throughput

    Number of completed items per time unit; shows the team's delivery capacity.

  • Customer satisfaction (NPS/CSAT)

    Captures user or customer satisfaction to validate product decisions.

Product team in digital greenfield

A cross-functional team uses Scrum, delivers in two-week sprints and uses retrospectives to adapt.

Support and operations team with Kanban

Support workflow is visualized, WIP limits reduce lead times and increase predictability.

Organization scaling agile practices

Company adopts shared metrics and governance to synchronize multiple teams.

1

Awareness and training for leadership and teams

2

Start a pilot in one team with clear metrics

3

Evaluate results and derive practical adjustments

4

Scale gradually with governance and coordination

⚠️ Technical debt & bottlenecks

  • Insufficient automation of tests and deployments
  • Unrefactored legacy code hinders rapid change
  • Documentation gaps in critical integration points
CommunicationDependenciesScaling
  • Waterfall disguised as sprints without real iteration
  • Using story points as individual performance metric
  • Retrospectives with no follow-up or consequences
  • Lack of leadership support prevents sustainable change
  • Neglecting technical practices leads to instability
  • Too many parallel initiatives overload teams
Facilitation and meeting moderationProduct management and prioritizationTechnical excellence and automated testing
Adaptability to market needsShort feedback cycles for validationFast and reliable delivery capability
  • • Regulatory requirements may slow iterations
  • • Limited team skills for agile practices
  • • Legacy architecture hinders rapid changes