Scrum in 2023: What to Expect and How to Prepare
Scrum is now more than thirty years old and more widely adopted than ever. The 2022 State of Agile report found Scrum in use at over 90 percent of agile-practising organisations. But adoption figures can be misleading. Scrum is used everywhere; it is used well in far fewer places. And the context in which Scrum operates is shifting in ways that require practitioners and organisations to adapt their approach if they want to keep getting value from the framework.
Looking ahead to 2023, five themes stand out as particularly important: the integration of product thinking with Scrum delivery, the growing crisis of technical debt, the expansion of agile beyond individual teams to organisation-wide adoption, the increasing recognition that psychological safety is not a soft issue, and the permanent embedding of remote-first team design as a structural reality rather than a temporary accommodation.
Product Thinking: Outcomes, Not Just Outputs
The most significant shift in how high-performing Scrum teams operate is the move from output-focused delivery to outcome-focused product management. Output-focused teams ask: did we ship the features we committed to in the Sprint? Outcome-focused teams ask: did we move the metrics that matter to users and the business?
This shift requires Scrum Masters and Product Owners to develop fluency in product thinking -- the ability to articulate what value a product should deliver, to measure whether it is being delivered, and to make prioritisation decisions based on evidence of outcomes rather than assumptions about outputs. Outcome-based roadmaps -- which describe what the product needs to achieve rather than what it needs to build -- are increasingly the expectation in organisations that take product management seriously.
Practitioners who want to remain effective in 2023 should invest in understanding metrics frameworks (HEART, SPACE, DORA), hypothesis-driven development, and the fundamentals of product strategy. These are no longer specialist topics for product managers only -- they are increasingly expected competencies for anyone working in a Scrum team.
Technical Practices: The Debt Crisis
Across the industry, technical debt has reached crisis levels in many organisations. Years of pressure to deliver features at speed have produced codebases that are difficult to maintain, expensive to change, and fragile under load. The result is a vicious cycle: high technical debt slows delivery, which creates pressure to cut corners further, which generates more debt.
The original Scrum framework was always intended to work alongside strong technical practices -- test-driven development, continuous integration, refactoring, and the disciplines now associated with the DevOps movement. In many adoptions, the ceremonies were adopted without the engineering disciplines, producing a shell of the intended framework.
In 2023, the organisations that will get the most from Scrum are those that treat engineering excellence as a first-class concern, not a secondary consideration after feature delivery. This means dedicating explicit capacity to debt reduction in every Sprint, making the cost of technical debt visible to business stakeholders, and holding the line on Definition of Done standards when the pressure to ship is high.
Agile at Scale: Beyond the Team
Scrum is a team-level framework. The challenges of coordinating dozens or hundreds of teams working on the same product or portfolio have driven the development of scaling frameworks -- SAFe, LeSS, Scrum of Scrums, Nexus, and others. Adoption of these frameworks is increasing, and the organisations investing in enterprise agility are beginning to see meaningful results in areas like cross-team dependency management, portfolio prioritisation, and alignment between development and business strategy.
Practitioners in 2023 who work in larger organisations should develop at least a working understanding of how Scrum connects to organisational-level agility. The Scrum team does not operate in isolation -- it operates within a broader system, and understanding how that system is structured affects what the team can and cannot do effectively.
Psychological Safety: No Longer Optional
Research on team performance consistently finds that psychological safety -- the belief that one can speak up, surface problems, or propose unconventional ideas without fear of punishment or humiliation -- is a stronger predictor of team effectiveness than talent, resources, or process. Google's Project Aristotle, which studied hundreds of internal teams, found psychological safety to be the single most important factor distinguishing high-performing teams from average ones.
Scrum depends on psychological safety at every turn. Retrospectives only generate genuine insight when team members feel safe to surface real problems, not just comfortable ones. Sprint Reviews only create useful feedback when stakeholders feel safe to raise concerns. Impediment escalation only works when Scrum Masters feel safe to challenge organisational obstacles.
Organisations that invest in building psychologically safe environments for their Scrum teams in 2023 will see commensurate improvements in Retrospective quality, backlog transparency, and the willingness of teams to surface risks early rather than absorbing them quietly.
Remote-First Teams: A Permanent Feature
The pandemic-driven shift to remote work accelerated an experiment that many organisations had been reluctant to run. The results were mixed but instructive. High-performing Scrum teams proved capable of maintaining effectiveness in remote settings when they had the right tools, clear communication norms, and deliberate investment in team cohesion. Struggling teams found that remote work amplified existing dysfunctions rather than creating new ones.
In 2023 and beyond, distributed and hybrid team configurations are a permanent feature of the landscape, not a temporary accommodation to be reversed when circumstances allow. Organisations that have not yet redesigned their Scrum practices for distributed teams -- asynchronous ceremonies, digital collaboration tools, explicit documentation norms, and intentional investment in relationship-building across locations -- should treat this as a priority.
What Practitioners Should Focus On
Develop product thinking skills: outcome measurement, hypothesis-driven development, and outcome-based roadmapping.
Champion technical practices: TDD, CI/CD, and explicit debt-reduction capacity in every Sprint.
Build at least a conceptual understanding of agile-at-scale frameworks and how they connect team-level work to organisational priorities.
Invest in creating the conditions for psychological safety, especially in Retrospectives and Sprint Reviews.
Redesign ceremonies and collaboration norms for distributed teams -- asynchronous-first where possible, with intentional synchronous touchpoints.
XNM Consulting helps organisations strengthen their Scrum and agile delivery practices, from team-level coaching to enterprise agility strategy.