Scrum@Scale Case Study

No More Hippos! Collaborative Prioritization with Registered Scrum@Scale Trainer Bob Willis

 

This data service government department was bogged down with legacy waterfall practices, inconsistent prioritization and constantly changing top-down directives. Registered Scrum@Scale Trainer Bob Willis guided their Agile transformation starting with transparent prioritization of the backlog, and the implementation of an Executive Action Team and Scrum of Scrums.

CASE STUDY SNAPSHOT

Trainer Name: Bob Willis
Organization: NDA
Organization Size: Large
Industry: Government
Topic: Backlog Decomposition and Refinement, Cross-Team Coordination, Prioritization, Regulatory Compliance, Traditional Project Management Failure
Date: 2019
Website: https://www.linkedin.com/in/willisuk/

Scrum@Scale Case Study Summary 

Learn how Registered Scrum@Scale Trainer Bob Willis guided a data service government department to create a prioritized common backlog and shift focus from projects to products. Time to market, Net Promoter Score (NPS), quality and team health all improved, while still meeting the compliance requirements of the government.

Traditional Project Management Failure 

A UK-based government department providing data and compliance services to the public through Web, Mobile and API channels was bogged down in top-down traditional waterfall management with inconsistent prioritization at all levels. Teams faced arguments, frequent changes of direction, and were constantly on edge. Each of the eight teams had their own backlog causing local optimization. They were project rather than product focused with a 12-month planning structure and little flexibility. There was also a lack of Product Owner empowerment and therefore team engagement. With Bob’s help, the department realized that their agile transformation needed to start with executive participation.

The Solution: Transparent Prioritization 

Registered Scrum@Scale Trainer Bob Willis’ first step was to lead an executive workshop focused on prioritization criteria and estimation. The new criteria were applied to the existing backlog with surprising results about what they were prioritizing and what next steps needed to be taken. The new transparent prioritization led to a drastic reduction in work in progress (WIP) while still considering the regulations, date dependence, and public perception issues unique to a governmental agency.

A MetaScrum and an Executive Action Team (EAT) were formed to guide the work on the new prioritized backlog. Teams became product rather than project focused and products were reduced from 17 down to three.

They went from eight independently functioning teams with separate backlogs to working collaboratively on two products. Teams in the same domain planned together. With a common backlog and cross-functional teams, they were able to align their work and collaborative refinement and planning allowed a much more rapid time to market. Not only did team productivity improve, but engagement and satisfaction increased with the new structure.

Key Results

Six short months into their Agile transformation, the measurable results were already amazing.

  • Team health improved significantly in the areas of team dynamics and leadership
  • Reduced time to market
  • NPS consistently increased
  • Improved quality
  • Escaped defects reduced by 30% 

Who is Bob Willis?

Registered Scrum@Scale Trainer Bob Willis is an enterprise focused Agile coach and trainer with over 30 years global IT experience. He is an expert at guiding organizations through the Agile journey to deliver complex, high value projects, and develop high performing teams.

Bob was selected by Scrum@Scale Founder Jeff Sutherland to be one of the first 30 Scrum Trainers to teach Scrum through Scrum Inc.!

Bob promotes continuous learning and development. He creates an environment focused on transparency, mastery, and innovation. Bob Willis is a passionate evangelist who truly knows the framework produces results.

More Scrum@Scale Case Studies

Achieve 5-10x Faster Market Delivery with Scrum at Scale

Achieve 5-10x Faster Market Delivery with Scrum at Scale

One of the Netherlands' largest DIY retail franchises had a siloed management structure and projects that took 3-12 months or even longer to get to market. They had a waterfall delivery style, with the entirety of the delivery at the end and no early value delivery for customers. Registered Scrum@Scale Trainer Serge Beaumont's approach started with the creation of cross-functional, autonomous teams, each solely responsible for a different part of the process. This allowed for work to proceed very quickly with each team simultaneously able to complete their part of a project without first waiting on another team. The results were immediate and impressive. The team achieved 5-10x faster market delivery to customers, there was now alignment between what was expected and what was delivered, delivery was made in smaller chunks allowing for early value delivery to customers, and e-Commerce sales soared.
Creating Customer-Centric Social Media Teams Using Agile

Creating Customer-Centric Social Media Teams Using Agile

In this case study, Christoph Dibbern tackles a myriad of challenges that were plaguing a social media-based organization – lack of prioritization, no organizational refactoring, and a lack of shared values. These challenges created an unproductive and unhealthy environment, where mistrust and misalignment were common and innovation was stifled. Utilizing Scrum@Scale, the organization was able to align around a customer-centric focus, work as a cohesive unit, and deliver high quality results to customers faster.
Preserve Culture While Scaling: The Road Back to Cohesiveness

Preserve Culture While Scaling: The Road Back to Cohesiveness

Gereon Hermkes explores the complexities of maintaining a cohesive corporate culture amidst the explosive expansion of a technology firm. To address this challenge, Gereon initiated a simple Scrum@Scale strategy focused on rejuvenating the core values of shared language, trust and cooperation. These principles had defined the company's early days but began to deteriorate with rapid scaling.