Skip to content

From Intuition to Data: How Saxoprint Scaled a Proven Agile Framework Across Two More IT Teams

An engineer in a hard hat and safety vest monitors industrial systems using multiple screens inside a production facility.
Kategoria:
Project Management / Agile, DACH
Branża:
Branża produkcyjna
Miasto:
Dresden, Germany 🇩🇪

Client

Saxoprint GmbH is a German printing company headquartered in Dresden, specializing in online printing services for business customers across Europe. The company uses advanced technologies both in production and in IT systems supporting sales, order processing, and business operations.

As part of an earlier collaboration, VM.PL carried out an AI Agile Transformation project that helped standardize Agile processes and significantly improve the performance of one of Saxoprint’s IT teams.

Following the positive results of the pilot project, Saxoprint decided to extend the approach to two additional teams. The goal of the Agile Scale Up project was to introduce proven standards across different working environments and establish a common foundation for data-driven planning and process management.

Challenge

Saxoprint already had a proven Agile framework in place, but its other IT teams followed their own processes. Their approaches differed in how they handled requirements, managed tasks, planned sprints, and measured performance.

The project involved two teams with different responsibilities: one focused on integrations and ERP business systems, while the other developed solutions supporting sales operations. Each team faced its own organizational challenges.

  • Lack of common standards and measurable data: Sprint planning relied primarily on developers’ experience. Without regularly tracking Lead Time, Cycle Time, and Velocity, it was difficult to assess the teams’ actual throughput, evaluate the effectiveness of improvements, and predict delivery timelines.
  • Fragmented task management: The teams used multiple tools and boards, which sometimes led to inconsistent task information. For the sales systems team, coordinating work with an external development partner added another layer of complexity.
  • Unstructured requirements management: Tasks reached developers through different channels, often without sufficient preparation. The absence of consistent quality criteria for requirements resulted in additional clarification and changes during implementation.
  • Limited visibility into disruptions: Unplanned tasks, support requests, and bugs affected sprint scope but were not consistently categorized. This made it difficult to distinguish actual disruptions from predictable day-to-day responsibilities.

Saxoprint needed a way to standardize work management across teams while addressing their individual needs. Another priority was establishing a measurement system that would help identify the causes of delays and support decisions based on actual performance data.

Infographic comparing two IT teams with different workflows, tools, and task boards, highlighting unclear requirements, inconsistent KPIs, and unplanned work.

Solution

VM.PL built on the framework developed during the previous pilot project and adapted it to the specific needs of two additional IT teams. The Agile Scale Up project was divided into four phases covering assessment, standardization, implementation, and evaluation.

Phase A – Assessment and Gap Analysis

VM.PL consultants analyzed how both teams organized their work, conducted employee interviews, and reviewed their existing task and requirements management practices.

By comparing current workflows with the standards established during the pilot project, they identified key process gaps and determined which elements of the framework could be adopted without modification and which required adjustments.

Phase B – Standardization and Team Preparation

Based on the assessment, VM.PL developed common working standards tailored to the needs of both teams.

  • Azure DevOps as the central management tool: Task structures and progress tracking practices were standardized, reducing the fragmentation of information across different boards.
  • Definition of Ready and Definition of Done: Common criteria for task readiness and completion were introduced to improve requirements quality and minimize uncertainty during implementation.
  • Clear responsibilities: The Product Owner’s role was defined as the central point of contact for receiving and prioritizing requirements.
  • Way of Working: A dedicated handbook was created for each team, documenting agreed-upon practices for collaboration, sprint planning, and performance monitoring.

VM.PL also provided training on using Azure DevOps and interpreting performance metrics.

Phase C – Implementation in Daily Operations

The next phase focused on applying the new standards during regular sprints.

VM.PL consultants participated in team meetings, supported Product Owners and developers, and helped address challenges that emerged as the teams adopted the new practices.

Regular KPI tracking enabled the teams to analyze Cycle Time, Lead Time, and Velocity and gain a clearer understanding of their actual throughput.

A new classification system for disruptions helped distinguish bugs, additional tasks, and support requests. This allowed the teams to identify sources of unplanned work more accurately.

Capacity planning that accounted for support activities helped the integrations and business systems team better incorporate service requests into its daily workload.

Phase D – Performance Evaluation and Handover

At the end of the project, VM.PL conducted a KPI audit, comparing both teams’ results against their initial baselines. During the final workshop, the consultants presented the results, identified remaining limitations, and provided recommendations for further process improvements. Responsibility for maintaining the established standards and monitoring performance was formally transferred to the teams and their Product Owners.

VM.PL’s four-step approach to extending Agile practices: assess team workflows, set shared standards, apply them in daily work, and measure the results.

Results

The Agile Scale Up project confirmed that the framework developed during the pilot could be successfully adapted to additional IT teams, despite differences in their responsibilities and working practices.

The most important change was the shift from planning based primarily on experience to managing workflows using measurable data. The implementation period also brought significant reductions in task completion times.

Reduced Cycle Time Across Both Teams

Both teams achieved substantial reductions in average Cycle Time, measured from the start of work on a User Story to its completion.

Integrations and business systems team: Cycle Time dropped from 9.4 to 3 days, a reduction of approximately 68%.

Sales systems development team: Cycle Time decreased from 5.6 to 2 days, a reduction of approximately 64%.

These results demonstrate that the framework developed during the earlier pilot can be successfully applied to teams with different responsibilities and organizational structures.

Consistent Work Management Standards

Both teams adopted agreed-upon standards for preparing requirements, planning work, and tracking task progress.

Regular measurement of Cycle Time, Lead Time, and Velocity established a foundation for evaluating performance across successive sprints. Separating different categories of unplanned work also made it easier to distinguish operational support requests from bugs and additional requirements.

Greater Team Autonomy

Another important outcome was the gradual shift toward teams taking ownership of their own processes.

One example was a team-led initiative to introduce labels for support requests. This demonstrated that the new standards were being used to independently identify and resolve organizational challenges.

A Proven Framework Ready to Scale

The first project for Saxoprint demonstrated how standardizing Agile processes could improve the performance of a single IT team. Agile Scale Up showed that the same approach could be extended to additional teams while adapting it to their specific needs.

With consistent standards, regular KPI monitoring, and better visibility into the causes of delays, Saxoprint established a foundation for more predictable IT work management.

The project’s greatest value was creating a repeatable model that enables teams to identify problems, evaluate the effectiveness of improvements, and continuously optimize their processes based on measurable data.

Infographic showing cycle time falling from 9.4 to 3 days in one team and from 5.6 to 2 days in another after adopting shared Agile standards.

Design, Development, DevOps czy Cloud – jakiego zespołu potrzebujesz, aby przyspieszyć pracę nad swoimi projektami? Porozmawiaj o swoich potrzebach z naszymi specjalistami.

Jakub Orczyk

Członek zarządu / Dyrektor sprzedaży

Zamów bezpłatną konsultację
Jakub Orczyk