Challenge
A global event ticketing technology company was operating with nearly 40 development teams using inconsistent Agile practices, tooling, and delivery standards. Some teams followed Scrum, others used Kanban, and many teams interpreted core delivery practices differently, creating fragmented workflows, inconsistent ceremonies, weak backlog management, and limited visibility into delivery health across the organization.
The company had recently introduced quarterly capacity planning, but without standardized sprint planning, Definition of Ready (DoR), Definition of Done (DoD), velocity tracking, or consistent backlog refinement, teams struggled to execute reliably against those plans. Ticket spillover between sprints was high, reporting was inconsistent, and delivery risks often surfaced too late for leadership teams to intervene effectively.
Approximately 400 employees across engineering, product, delivery, and PMO functions also had widely different levels of Agile knowledge and Scrum experience, making organization-wide alignment difficult. Leadership had already identified the need for a large-scale Agile training and standardization initiative and was preparing to engage an external training vendor at significant cost to help align delivery practices across the organization.
Insight
The organization did not necessarily need a large external training vendor to standardize Agile practices successfully. The PMO already had strong operational context, existing relationships with delivery teams, and internal leadership capable of supporting adoption if the rollout structure could be designed to scale across different teams and working environments.
Solution
Designed and facilitated a two-phase Agile transformation and Scrum training program focused on standardizing delivery practices across the organization. Phase one introduced company-wide foundational training covering Agile principles, Scrum terminology, delivery expectations, and the rationale behind the operational changes. Sessions were delivered virtually, recorded for scale, and reinforced through PM-led follow-up discussions, PMO office hours, and feedback loops.
Phase two introduced adaptive instructor-led team training designed around each team’s workflows, Agile maturity, and delivery environment rather than forcing every group through identical material. The rollout established shared delivery standards while allowing implementation guidance, exercises, and operational discussions to adjust based on each team’s structure and execution patterns. A train-the-trainer program also enabled project managers without formal training backgrounds to facilitate sessions consistently across the organization while still tailoring discussions and implementation support to individual teams and working styles. The overall rollout aligned Scrum adoption with quarterly planning, Jira workflows, and future DevOps delivery standards, creating a more scalable operational foundation for execution and reporting.
Results
Within six months, approximately 95% of teams had transitioned to functioning Scrum teams operating under shared delivery standards and practices. Standardized workflows enabled more reliable Jira reporting and improved visibility across planning, execution, and delivery performance.
The initiative also supported a broader DevOps workflow transition by establishing more consistent operational behaviors and execution expectations across teams. Standardized practices improved team mobility, allowing approximately 25% of team structures to shift with less disruption because delivery processes and expectations were now more consistent organization-wide.
Additional outcomes included reduced sprint spillover, improved on-time delivery, stronger backlog readiness through Definition of Ready practices, and more scalable cross-team coordination. The organization also avoided the need for a large external training engagement by building and scaling the rollout internally through existing PMO leadership and facilitator enablement efforts.