The Journey to Scrum@Scale at a Fortune 500 Oil & Gas Company

In this client story, we’ll discuss how Scrum Inc. leveraged these four differentiators and played a pivotal role in a Fortune 500 oil and gas company’s journey to Scrum@Scale.

Contexte
In recent years, acquisitions have been a major growth strategy in the oil and gas industry. As a Fortune 500 oil and gas company merged with various newly-acquired companies, its IT portfolio grew. The firm soon found itself with approximately 150 legacy IT systems and little or no integration among them. Teams had no clear visibility into customer information, since a single customer’s data often resided in many different systems and Excel spreadsheets.

The leadership team recognized that a change was needed. They decided to implement an SAP ERP system to streamline the IT infrastructure. Two activities in particular were challenging: migrating data to the ERP system and rolling out enterprise IT solutions. Although the organization consistently spent $50 million per month on the ERP implementation and data migration, teams struggled to demonstrate progress.

A newly appointed IT leader thought Scrum could be the answer to these hurdles. To explore the idea further, he initiated discussions with Scrum Inc.’s Consulting & Coaching Practice. Scrum Inc. trained the executive team to cultivate understanding and support for Scrum at the leadership level. In addition, Scrum Inc. helped form executive coordination teams and Scrum Key Performance Objectives (KPOs) related to Scrum goals and the Scrum Golden Rules.

After initiating the Scrum work at the executive level, the company asked Scrum Inc. to engage with the SAP implementation, enterprise solutions, and data wrangling teams to train and coach them on Scrum practices. The Wells and Fields Data Wrangling Team’s experience illustrates how Scrum Inc.’s unique approach helps organizations deliver results quickly and efficiently.

A Closer Look: The Wells and Fields Data Team’s Experience with Scrum
When Scrum Inc. coaches first engaged with the Wells and Fields data team, both the team and the company were new to Scrum. The team was starting with the 3-5-3 fundamentals (3 roles, 5 events, 3 artifacts) and members were striving to obtain a Shu state – that is, they were adopting Scrum practices, but they weren’t yet going deep to understand the rationale behind the principles.

During the autumn of 2017, the dedicated Product Owner (Benjamin) and the open-minded Scrum Master (Peter) experienced two back-to-back failed go-lives as their team attempted to prepare data for the struggling SAP ERP implementation initiative. Benjamin and Peter had been unable to advance the readiness of the team’s data to the 70% acceptance level which was mandated by corporate key performance indicators (KPIs).

In addition, the team faced three additional challenges:

• Geographically distributed teams. Team members were distributed between offices in Texas, France, and India.
• Limited subject matter expert resources. Subject matter experts (SMEs) were spread thin – one SME, for example, had been assigned to four operating Scrum teams.
• Insufficient development staff. Additional developers were needed.

Embracing Scrum
As the team engaged with Scrum Inc., Benjamin noted, “We really wanted to put into practice everything we learned in our training. We knew that how we were currently operating was not working.” The team agreed to adopt key principles from the Scrum training, including respecting roles, participating actively in Scrum events, and making work and progress visible. Scrum Inc. also encouraged the group to focus on four actions:

• Experimenting with One Week Sprints. At the kickoff, the team agreed somewhat reluctantly to test one-week Sprints. They found that the tight feedback loop motivated the team to write more concise and focused Product Backlog items. The team discovered they could swarm on these items and complete them in a single day within a Sprint. As a result, the team doubled its velocity from an average of 15 to 30 in seven short Sprints. Velocity is key metric which quantifies the amount of work a team can tackle in a single Sprint.
• Measuring Team Happiness. During Sprint 4, the team started measuring overall happiness. This metric proved to be a key indicator for team productivity, as well as the quality of work delivered. When a team member was abruptly fired in Sprint 10 by management without team input, there was a steep decline in team happiness and productivity also slowed.
• Addressing the Habit of Over-committing to Work. In Sprint 11, new developers were added to the team. Although this was good news, it did not immediately address the team’s habit of over-promising, but under-delivering work. Once the new developers were onboard, the team leapt from a committed velocity of 62 points (completing a total of 39) to 114 points (completing just 540).

Scrum Inc. coached Benjamin and Peter to work with the team to produce well-defined, achievable Sprint Goals and a committed Sprint Backlog moving forward. By Sprint 13, the team committed to 68 and delivered 76 points. Moving forward, the team maintained a more consistent pattern of committing to and in many cases, over delivering on their promises to stakeholders.

• Experimenting with Co-Location. Benjamin encouraged the Texas-based team to work side-by-side in a large room. The close proximity of the team members helped them become hyper-productive.

Results
By Sprint 19, Benjamin and Peter’s team delivered the North American Wells and Fields data into the new ERP system. Their results were impressive:

• The delivery was one full week ahead of schedule.
• The data was at a state of 93% readiness – well above the corporate mandated 70% level. Prior to adopting Scrum, the team never delivered data above a 17% readiness level.
• Two other mission-critical countries that had stagnated at a 35% readiness level were pushed to 74% and 82% readiness.

Enterprise Scrum Engagement and Success Stories