Hewlett Packard Enterprise (HPE) Software – Enterprise Agile Expansion with SAFe

“With a proven framework, we can deliver solutions much faster and with less effort. SAFe® defines the roles, teams, activities and artifacts to apply Lean and Agile principles at enterprise scale, and provides outstanding training and coaching materials to increase our chance of success.”

Peter Vollmer, Distinguished Technologist at Hewlett Packard Enterprise (HPE)

Challenge:

HP teams had experimented with Agile methods for years, but efforts were limited to individual teams with mixed results.

Industry:

Information Technology, Software

Solution:

  • SAFe®
  • HPE Agile Manager
  • HPE ALM

Results:

  • Teams run iterations within a number of weeks rather than months.
  • Typically, teams complete sprints within two weeks.
  • The company noticed a 20 percent drop in defects.
  • Company leaders are backing Agile globally as means of meeting strategic business goals.

Best Practices:

  • Start small – Start with one or two teams to reduce risk and create evangelists that will spread the news.
  • Use a light hand – Don’t force teams to go Agile but rather let evangelists share that Agile is fun and delivers better results.
  • Educate, educate, educate – Establish change agents and continuously educate. Many may assume they know what Agile is all about, but in reality may not.

Introduction

Created as a result of the split of Hewlett Packard into two companies in late 2015, the newly formed Hewlett Packard Enterprise (HPE) helps organizations adapt to modern digital demands—to create secure, cloud-enabled, mobile-friendly infrastructures. HPE Software, one of four divisions within HPE, drives a significant percentage of the company’s overall profit.

Abstract background of wires and glowing particles

At HPE, business units span multiple continents, from the headquarters in Palo Alto, CA to Europe and the Asia Pacific. One product team may include members in up to five different locations.

The company’s journey to Agile began as early as 2001 when some HP teams began iterative development independently. In the years that followed, they went on to experiment with a mix of XP, Kanban and Scrum. However, their efforts, while approaching Agile in business, were limited to individual teams with mixed results.

To scale Agile adoption beyond a few scattered teams would require a more formalized effort and a methodical approach to ensure business continuity.

“We needed to respond more quickly to user requests and environmental changes, and reduce the cost of software development using traditional methodologies such as waterfall,” says Peter Vollmer, Distinguished Technologist at HPE. “Yet we could not risk compromising core business processes and KPIs.”

A Proven Framework for Faster Delivery

When team leaders evaluated the variety of Agile methodologies, they found the measured approach they needed in the Scaled Agile Framework® (SAFe®).

“With a proven framework, we can deliver solutions much faster and with less effort,” Vollmer says. “SAFe defines the roles, teams, activities and artifacts to apply Lean and Agile principles at enterprise scale, and provides outstanding training and coaching materials to increase our chance of success.”

HPE began SAFe Agile expansion with a “coalition of the willing,” Vollmer says. The first to raise their hands, a team based in Fort Collins, Colorado, with members in India, became the first to begin SAFe training and training. With the Colorado team underway, a second-team at HPE’s headquarters in Sunnyvale began as well.

Beyond the Classroom

To help teams apply SAFe beyond the classroom, HPE provided some teams with access to a trainer to educate and coach them through the process. Coaches provide feedback to teams, ask questions and help them find the right answers based on context, culture and environment. To coach the first two teams, and now others, Vollmer ramped up on SAFe through a SAFe Program Consultant (SPC) course.

Success with scaling Agile at HPE has hinged on education and ensuring that team members understood SAFe clearly, including taking the effort to get on the same page regarding terminology. “We found a great deal of misunderstanding when it comes to Agile and its principles, which is why teams often struggle with accepting the change,” Vollmer says. “In order to get the most out of Agile practices, each team should have a trainer who educates and coaches them throughout the learning and adoption process.”

HPE Software - Agile Expansion with SAFe

20% Defect Drop

Early SAFe users evangelized their experience, increasing engagement and adoption. To date, several hundred team members have attended SAFe training and achieved certification. Those actively applying Agile methods numbers in the thousands, based on usage of an HPE-developed onboarding portal (Agile Manager), and continues to grow. Between 2014 and 2015, the number of registered users jumped by 50 percent as the effort gained momentum.

Though still adopting SAFe more broadly, HPE already sees an impact. “Our teams run iterations within a number of weeks rather than months, all while executing robust delivery processes,” Vollmer says. And with the change, teams run sprints in two weeks instead of four.

As SAFe practices expanded, the company also noticed a 20 percent drop in defects, as measured by its own defect-tracking application. Within the system, HPE can easily measure key performance indicators, including customer-encountered defects – insight that contributes to customer satisfaction and delivering higher-quality releases on schedule.

“Like most of our customers, HPE Software must adopt Enterprise Agile practices,” says Jerome Labat, CTO of HP Software. “Working closely with our HPE ALM (application lifecycle management) and AGM (Agile Manager) engineering teams allows us to continuously improve our product, scale out our software operations while keeping our costs under control. We‘ve seen tremendous benefits such as efficiencies, improved quality, and a reduction in time-to-market windows.”

Next Steps

Abstract background of wires and glowing particles

So far, HPE has run four Agile Release Trains (ARTs), all in one business unit. In the coming months, another business unit in Sunnyvale will quickly launch another ART.

Next, HPE Software targets training an additional thousand people on SAFe, which includes all R&D and product management roles. Toward that effort, HPE will establish an Agile transformation team and deploy up to three SPC-certified change agents in each major geographic area.

All these steps underscore the increasing importance of scaling Agile in meeting HPE’s broader strategic business goals.

“We have to get the whole of Hewlett Packard Enterprise, from a development perspective, adopting the Agile methodology, so that we can go faster and deliver more to our customers’ expectations,” said Martin Fink, CTO of Hewlett Packard Enterprise.

Back to: All Case Studies

Suggested Case Study: Amdocs

TomTom – Achieving Enterprise Business Agility with SAFe

Implementing SAFe in Consumer Electronics

“There is no doubt in my mind that without SAFe and Rally we would not have launched this in only 140 days. It is also our best new product ever.”

Industry:

Consumer Electronics

Introduction

Best known for being a global leader in navigation and mapping products, TomTom also creates GPS sports watches, as well as state-of-the-art fleet management solutions and industry-leading location-based products. They are the mapping provider for Apple Maps, and the maps and traffic data provider for Uber drivers in over 300 cities worldwide. Headquartered in Amsterdam, TomTom generates 1 billion euros in annual revenue, with 4,600 employees worldwide.

In 2012, the organization was facing a number of challenges:

  • Organised as waterfall projects
  • Many projects working in all parts of the code with minimal module or component ownership
  • Many releases are months-quarters late
  • Multiple code lines and branches
  • Negligible automated testing & no continuous integration
  • “downstream” teams spend 3,4,5 months accepting the code and often changing it
  • Poor visibility and facts-based decision-making

After reading Dean Leffingwell’s Agile Software Requirements—their SVP read it cover-to-cover on his vacation—they decided to transition to SAFe. Their first step was to provide SAFe training for their CTO, SVPs, and 50 CSMs and CPOs. From there they began reorganizing from the Scrum teams up, arranging product clusters and component Scrum teams around the idea of one Agile Release Train (ART) per product.

Six months into the SAFe transition, they were given a previously unheard-of goal of a 126-day launch cycle for their 4th generation of consumer navigation products. This put SAFe to the test, as it cut their development time down almost two-thirds from what was previously a 1-year cycle. Launching 5 ARTs—1 product each—they assigned 4-14 teams to each train, working across multiple locations.

Highlights of SAFe Benefits

  • Reliable and predictable releases of production code
  • Fail fast (<2 weeks) is better than after 6 months
  • Detect/prevent issues with each new submission
  • No bottleneck at the end
  • Reduces waste as others stay up to date
  • Improved transparency and info sharing
  • Teams establish ways of working & esprit du corps
  • Improves estimating by allowing historical comparisons
  • Team controls their own commitments
  • Sustainable development
Implementing SAFe in Consumer Electronics

Today SAFe is practiced by all of TomTom’s large product teams representing navigation software, online services, map creation and sports software. That represents approximately 750 FTEs, with 200+ trained and certified in SAFe.

Their 32-page case study is well worth the read as it summarizes their experience over a 5-year period, revealing both wins and challenges. Their breakdown of the “Good” the “Bad,” and the “Ugly,” makes it particularly interesting for any large enterprise wanting to understand the ins and outs of a real world SAFe adoption.

A special thanks to TomTom’s  James Janisse, VP Connected Navigation System, and Han Schaminee, SVP Location Technology Products, for sharing your story.

Back to: All Case Studies

Suggested Case Study:

Air France- KLM

SK Hynix Memory Solutions – Adopting SAFe to Improve Enterprise-grade SSDs Production

SK Hynix Memory Solutions - SAFe to Improve Enterprise-grade SSDs Production

Industry:

Technology, Semiconductors

Overview

SK hynix memory solutions (SKHMS) is a subsidiary of  the SK Hynix, Inc, which ranks #82 in the Fortune Global 500, and is the 5th largest semiconductor company in the world. Hynix memory is used by Apple, Asus, Google, IBM, Dell, and Hewlett Packard, as well as in products such as DVD players, cellular phones, set-top boxes, personal digital assistants, networking equipment, and hard disk drives.

Being a leading provider of custom system-on-chip (SOC) solutions for the solid state disk (SSD) storage market, SKHMS wanted to maintain their competitive edge via relentless improvement for producing enterprise grade SSDs. They teamed up with Scaled Agile Gold Partner, CPrime, to assess areas of improvement, and to understand the major impediments in their product delivery life-cycle. They gave careful attention to:

SAFe to Improve Enterprise-grade SSDs Production
  • How hardware was coordinated with firmware development.
  • How testing was conducted throughout the current PDLC process.
  • Departments involved in building and delivering the product.
  • How often these products were released to the customer and/or to the market.
  • Source code management and build deployment.
  • Tooling in place to support the Agile pilot.
  • The U-Curve optimization (analysis of transaction costs) for delivering work.

They ultimately chose SAFe as the Framework best equipped for agility transformation and to address the complex issues often associated with the firmware development. Kicking off a 1-year pilot program, they started with 5 Scrum teams with 50 people to support their first Agile Release Train (ART), and set their Program Increments (PIs) at 3 months, with a two-week iteration cycle.

Software and Hardware Align Through Program Level, Value Stream

They decoupled the Hardware group from the Firmware ART because their work was not conducive to two week iterations with the Scrum Teams. Instead, the Hardware group worked in a Kanban like fashion with SLAs on their work based on the Backlog prioritization. For example, knowing what features were coming down the pipe, they were able to prioritize their own work and in some cases, put out proto-hardware for testing purposes during the Program Increment. This coordination was possible because representatives from the Hardware group attended critical Program level meetings as stakeholders and because they were part of the Value stream for delivering the product.

Early Results Reveal Tangible Value

The Pilot was off to a solid start and teams were embracing the change, and seeing the tangible value of using SAFe. The overall metrics and feedback indicated:

  • 60% improved transparency
  • 55% defect reduction rate
  • 50% improved service delivery predictability

The 8-page study, provided below, is well worth the read, as it includes helpful detail and insights that include:

  • Their Preparation Checklist
  • Program Backlog Prioritization
  • Business Value
  • Timing Criticality
  • Opportunity Enablement/Risk Reduction
  • Feature Analysis & Architurecture Design
  • PI Planning
  • Continuous Integration

A big Thank you! to Johnny Lam, Director at SKHMS, and Dr. Sanjeev Raman Enterprise Agile-Lean Coach from cPrime, for sharing your SAFe experience.

Back to: All Case Studies

Suggested Case Study:

Seamless Payments

Seamless Payments – A Story of Successful SAFe Transformation

“To sum up, the case study of Seamless is evidence that small or medium-sized companies can benefit from a scaled agile framework with custom modifications.”

Challenge:

  • Multiple environments
  • Feature requests coming from different markets
  • Synchronizing work between teams (Software Engineering department spans 4 countries)
  • A way to deal with inevitable change of culture due to fast growth

Industry:

Technology, Financial

Introduction

Founded in 2011, and active in more than 30 countries, Seamless handles more than 3.0 billion transactions annually, making it one of the world largest suppliers of payment systems for mobile phones. Perhaps best known for its flagship mobile wallet product, SEQR (se•cure), the fast-moving Stockholm-based company has grown from 50 to 200 employees in 2 years, and is pursuing an expansive growth strategy that has presented challenges both technical and organizational.

Challenges

Seamless Payments - A Story of Successful SAFe Transformation
  • Multiple environments
  • Feature requests coming from different markets
  • Synchronizing work between teams (Software Engineering department spans 4 countries)
  • A way to deal with inevitable change of culture due to fast growth

Wanting to avoid the unnecessary bureaucracy that often comes with expansion, they turned to a scaled-down version of SAFe—along with major technical investments in the deployment pipeline—to provide a structure that would provide a solution for current challenges, and accommodate growing complexity.

More Stories in Less Time—Despite Setbacks

The story of this SAFe transformation is published in InfoQ and comes from Agile and Lean Product Development Expert, Mikael Lundgren, and Seamless Payments’ Software Engineering Manager, Tomek Pająk. They provide an account of the experience that is rich with detail and goes beyond tactical execution to include the strategic thinking behind this scaled-down SAFe transformation. They recount:

  • How they down-scaled SAFe while maintaining its core ideas
  • Tools utilized for managing backlogs of features, epics, and stories
  • Recruiting Scrum Masters to act as Agile coaches for entire organization
  • Establishing new roles to better support working environment
  • Introducing WIP-limited program execution where work is planned in Agile Release Trains

Many thanks to the study authors, Mikael Lundgren and Tomek Pająk, for sharing your story and providing inspiration for small to medium-sized companies seeking scalable solutions as they face similar growth challenges.

Read the full story in the InfoQ article, Downscaling SAFe.

Seamless Payments - A Story of Successful SAFe Transformation

Back to: All Case Studies

Suggested Case Study:

Standard Bank

Elekta – Adopting SAFe for a Successful Lean-Agile Transformation

Elekta is a human care company pioneering clinical solutions for treating cancer and brain disorders. They develop sophisticated, state-of-the-art tools and treatment planning systems for radiation therapy, radiosurgery and brachytherapy, as well as workflow enhancing software systems across the spectrum of cancer care. Headquartered in Stockholm, Elekta employs around 3,800 employees globally in 30 countries.

Industry:

Software

Overview

Every day 100,000 patients receive diagnosis, treatment or follow-up by an Elekta solution

Elekta’s development goal is to enhance patient and customer value by providing solutions that improve, prolong and save lives better and faster. With teams working in several time zones, and individual members having different backgrounds and history working on separate products, their challenge was to create an environment where teams could better align with global priorities and with each other.

Implementing SAFe for Lean-Agile Practices

In 2007, Elekta adopted Scrum, but in their attempt to scale up, they saw that the Scrum teams were operating in silos which created issues with dependency, integration, and visibility of the big picture, all causing lack of clarity on overall objectives and plan. Wanting to address all areas of the enterprise, Elekta took a holistic view and introduced SAFe to their Scrum teams, launching their first Agile Release Train (ART) in 2013. Soon thereafter, they expanded to the Program level and trained all of their teams.

Today, Elekta is running 4 ARTs with 20 teams across three continents. Their SAFe journey has delivered significant gains and improvements in several areas, provided valuable lessons learned, as well as a roadmap to refine their value streams, and tackle ongoing challenges, including a deeper integration of Lean-Agile practices at the Portfolio level. Here are the highlights:

Introduction of SAFe Led to Key Changes in the Organization

  • Introduced Rally for Agile project management
  • Adopted organization and roles for SAFe (RTE, PM/PO, UX, EA, Agile coaches)
  • Streamlined development tooling and processes
  • Updated the Quality System for Agile development
  • Simplified project time reporting

Gains Made Through Introduction of SAFe

  • Improved quality
  • Cross site and cross functional collaboration
  • PI Planning provides both vertical and horizontal alignment
  • Transparency through Rally, reports, and  SAFe ceremonies
  • Agile Portfolio estimation & planning drives realistic Portfolio plan

Elekta’s Top 3 Tips for Starting up SAFe

  • Get buy-in from management—this is not isolated to development
  • Plan for a lot of training and exchange of practices to ensure an understanding of the principles behind (the mechanics are easy to learn). Bring in consultants/experts!
  • Use Agile to introduce it (don’t wait until everything is planned and in control, just start!)

Take a moment to read the Speaker notes in the PowerPoint; you’ll see that Elekta has been generous with sharing some of the context and nuance that can be especially helpful for anyone going through a SAFe transformation.

Many thanks to Elekta’s Director of Engineering, Petrine Herbai, Manager of Engineering, Lars Gusch, and our Gold Partner, Rally Software; we appreciate all the great information you have shared, and look forward to hearing more about your continuing journey of SAFe transformation.

Many thanks to Elekta’s Director of Engineering, Petrine Herbai, Manager of Engineering, Lars Gusch, and our Gold Partner, Rally Software; we appreciate all the great information you have shared, and look forward to hearing more about your continuing journey of transformation.

Share:

Back to: All Case Studies

Suggested Case Study: Royal Philips

NAPA Group – Achieving Business Agility Using SAFe and Scrum

NAPA Group is a leading software house providing solutions for ship design and operation with the mission to improve safety and eco-efficiency of the global maritime industry. Headquartered in Finland, NAPA and NAPA for Operations (Onboard-NAPA) have established themselves as the de facto standard for ship design. They are used by shipyards, owners, designers, classification societies, research institutes, authorities, consultancies and universities around the world.

Industry:

Software, Maritime


The partner that made it happen:


Overview

In 2012, with nearly 400 user organizations for design application and 2,000 installations onboard, they found themselves suffering from growth pains stemming from major annual releases, a large volume of projects, variable scope and schedules, and lack of a framework of best practices needed to support their fast-paced expansion and development. In other words, release schedules were slipping, and it was becoming difficult to get software out.

“95% of ships built annually are designed by our customers using NAPA.”

With the guidance provided by Scaled Agile Gold Partner, Nitor Delta, NAPA embarked upon a 2-year journey of dramatic organizational change that included a combination of Scrum integrated with a full-scale SAFe implementation that ultimately led to their first Release Planning event in 2014.

The results from their 2-year journey are impressive:

• Transparency increased on all levels
• Delivery cycle time down from >12 months to 3 months
• Increased predictability (2014 92% successful releases)
• Need for patches decreased
• Less defects in main branch
• Good basis for further growth

The NAPA experience is a classic example of how the principles of SAFe and Scrum can work in harmony for successful business agility to produce measurable business results. They have demonstrated that the strategic planning enabled by the Portfolio level in SAFe in no way diminishes the value of Scrum, but in fact, illustrates the complementary aspects of both practices.

Many thanks to Toivo Vaje, SA, of NAPA Group for sharing your Lean-Agile experience, and to Maarit Laanti of Nitor Delta for your role in this successful SAFe implementation.

Back to: All Case Studies

Suggested Case Study: HPE Software

CSG International – Achieving Lean-Agile Transformation Using SAFe

Lean-Agile Transformation Using SAFe

Sometime after the publication of Scaling Software Agility in 2007, Dean Leffingwell started working with Mauricio Zamora, Scott Prugh (and later Mark Fuller) in a Lean-Agile transformation using SAFe at CSG International. More than 90,000 customer service agents rely on CSG (NASDAQ: CSGS ) customer care and billing solutions each day to support more than 48 million North American video, voice, and data subscribers. The company has been around for over 30 years, and the solutions have evolved during that period such that there are now more than 10 separate technology platforms at work and a significant amount of legacy code. It’s a demanding, extremely complex environment, hosting millions of transactions per day.

Industry:

Information Technology, Customer Service

We began before SAFe was codified into the framework it is today, so at CSG we truly learned together, with Mauricio, Scott, and Mark, all adding value to the conceptualization of SAFe 1.0-2.0 and on.

As SAFe evolved, CSG trained a number of internal SPCs who eventually trained over 2,000 employees using Leading SAFe.

As development practices improved, the system started putting more and more pressure on faster delivery, not just faster development, and Scott Prugh, and others, turned their minds to the DevOps challenge. Along the way, Scott became a contributor to SAFe, as the author of the Continuous Delivery Guidance article.

Fast forward to 2014. At DevOps Enterprise Summit 2014, Scott describes how they have applied SAFe, and more importantly, the Lean and Flow principles that underlie it, to substantially improve productivity and throughput from development through deployment.

If you have ever wondered how, specifically, Lean-Agile principles—like cadence and synchronization, cross-functional teams, visualizing work, backlog management, reducing batch size, synchronized release planning, and more—can increase the quality, throughput, and delivery of large scale software in a seriously complex legacy environment, you have to watch this 20-minute video!

After all, until it’s deployed, all that cool new software doesn’t provide any real value to anyone.

Mauricio helped start Scaled Agile, Inc., and was a principal developer of SAFe

Mauricio “Mo” Zamora
July 23, 1969—November 24, 2011

Mauricio helped start Scaled Agile, Inc., and was a principal developer of SAFe, but tragically, he passed away on Thanksgiving, 2011. His work lives on inside SAFe, where it improves the lives of practitioners every day; that was Mo’s personal mission. We think about Mauricio most every day, and his professionalism, knowledge, passion and integrity still set the standard we all try to adhere to.

Back to: All Case Studies

Suggested Case Study: Royal Philips