Blog

“Be The Change: Transform Your Organization Through Servant Leadership” Presented at Global Scrum Gathering Austin 2019

By: Brian Milner | May 28, 2019 |  Agile Transformation,  Leadership,  Slides

“Revolutionary Ideas do not change institutions. People change them.” – Robert K. Greenleaf.

People over Process is the very first value in the Agile Manifesto. So why do we often begin our transformations focused on processes? Organizations will pay far more attention to what you do than to what you say–if we want to create a culture of Servant Leadership then we need to begin by serving.

In this session at Global Scrum Gathering Austin, Brian Milner dives into the benefits of a Servant Leadership influenced organizational transformation approach.

Key Takeaway from “Be The Change: Transform Your Organization Through Servant Leadership”

  • Understand how Listening, Empathy, Foresight, Commitment to the Groth of People, and Persuasion help unlock new approaches to coaching an organization through a transformation.
Blog

“Make Shift Happen: Leading Change” Presented at Global Scrum Gathering Austin 2019

By: Steve Martin | |  Agile Transformation,  Leadership,  Slides

Change is hard. Despite our best efforts, approximately 70% of change initiatives fail. For the 30% that did not fail, there was most likely tension along the way. The truth is, change is inevitable and organizations do not change… people do.

In this session at Global Scrum Gathering 2019, Steve Martin discussed how organizational change is a mindset shift that begins with leadership.

Key Takeaways from “Make Shift Happen: Leading change”

  • Competitive advantage is temporary – constant change is the “new” status quo
  • Employees at all levels experience fear of change
  • We need to shift focus on the processes of change management and towards leading the creation of change “engines” that harness change
Blog

“Why Transformations Get Stuck” Presented at Global Scrum Gathering Austin 2019

By: David Hawks | |  Agile Transformation,  Article,  Leadership,  Slides

In this world of exponentially increasing market disruption, it is more imperative than ever for organizations to not only achieve operational agility (efficiency, speed, etc.), but also organizational agility (speed to respond to market change).

In this session at Global Scrum Gathering 2019, David Hawks showed attendees how leaders can guide their organization’s past top Agile transformation impediments and accelerate the momentum towards true organizational agility using a proven transformation framework, the Path to Agility®

Key Takeaways From “Why Transformations Get Stuck”:

  • The impacts of four top key impediments slowing or preventing significant gains.
  • An understanding of how an organization develops new abilities by implementing Agile practices and how those abilities result in better agility and impact an organization.
  • The ability to assess their current state of agility and where to focus near term

For more on our approach to building lasting business agility, you can check out our Transformation Services page.

Blog

Webinar: Agile Case Study: Leading Change At Texas Mutual

By: Agile Velocity | Feb 27, 2019 |  Agile Transformation,  Leadership,  Webinar

Download the Full Recording Here

In 2018, Texas Mutual Insurance Company made the choice to go “all in” with Agile. After decades at the forefront of workers’ compensation insurance for the state of Texas, Texas Mutual recognized that they would have to change how they delivered value in order to stay at the top.

In this webinar, Erik Cottrell interviews Texas Mutual COO, Jeanette Ward. Learn how she’s leading and managing change across the enterprise, how Texas Mutual made the decision to go Agile, and how she worked with peers to leave behind old Command and Control leadership habits.

Key takeaways include:

  • An executive’s perspective on managing an Agile transformation
  • Why TXM takes risks in a risk-averse industry
  • Tips for preparing your organization for change
  • Benefits and results gained from implementing Agile in insurance
  • How to win over the Agile skeptics in your organization
Blog

Only The Best: Expecting The Most From Your Agile Partner

By: Agile Velocity | Feb 15, 2019 |  Agile Coaching,  Article,  Leadership

I’ve found most executives genuinely want to know, “How do I help our Agile transformation?” Becoming an agile company is new for leaders and teams. Yet, leaders are often left out while teams get the lion’s share of the attention from Agile coaches.

As a fellow leader, I feel for them. It’s crucial for leaders to be on board with any type of transformation. Equally crucial is a team that supports their leaders and helps them stay engaged in the process. In this article, we’ll outline the ways leaders can show their own investment by leveraging their Agile transformation partners (ie. the partner they choose to provide Agile coaches or Agile consultants).

What Leaders Should Expect To Learn From Their Transformation Partners

1. Answer “Why”

Prior to an Agile transformation, every leader should answer the big “why” question: Why are we going through this pain and dealing with the disruptiveness that comes during an Agile transformation?

A transformation partner should recognize the need for a “why” statement and help leaders define the need for change. It’s important to clearly articulate this need to teams as they adopt new models, change processes, and go through transformational pain.

Leaders who remind everyone why the company is going through change offer meaningful support to their teams. The most common why statements we’ve heard at Agile Velocity include the following:

  • Growing market share
  • Increasing revenue
  • Getting faster customer feedback
  • Improving time-to-market
  • Beating the competition.

When leaders can effectively convey their compelling reasons for change to their colleagues and teams, they can lay the foundation for lasting, positive change.

2. Thought Partnership With Powerful Change Leaders

A transformation partner should help leaders build a powerful coalition of fellow leaders.

Company-wide change does not happen in a silo, and fractured relationships will doom an Agile transformation. We know firsthand that Agile transformations only works when companies build teams of leaders at high enough levels to make the transformation stick. It’s incumbent upon leaders to build and nurture a guiding coalition of fellow leaders that can help ensure change practices become standard daily procedures.

It’s absolutely pivotal that the right transformation partner is on board to help achieve this goal. As leaders drive changes through their organizations, they’ll wrestle with an array of new issues and problems. They’re going to need someone they trust with an objective point of view to talk through their options. Ideally, this is your transformation partner.

3. There’s A Plan, Right?

Transformations are more than smart people doing smart things. We believe leaders should have a concrete transformation framework to help lead their companies through change. (Ours is called The Path to Agility®.)

A  framework helps leaders identify exactly where they are in the change process. They also help organizations recognize what’s coming next, what’s working, and which areas still need attention.

Companies who don’t undertake change with such a framework in place are leaving things to chance and hope–which isn’t a great strategy. A leader should expect their Agile coaches or Agile consultants to provide them with an approach that reduces that risk.

4. Respond, Don’t React

In 1995 a leader told me, “Erik, I don’t mind problems but I hate surprises. I mean, I really hate them. Never call me with a surprise. But, you can always call with problems.” A good transformation partner identifies their teams’ change stages and communicates what’s coming next.

Agile Velocity’s Path to Agility® makes it easy for leaders to look around the corner to see what’s coming. Together with leaders, we can anticipate the next set of problems and challenges so they are prepared and ready in advance. Leaders who hear of issues from their teams with no forewarning (surprise!) often fall into “action mode” to solve problems. This typically reinforces the problem. Leaders who are prepared can support their teams’ efforts to solve their own problems.

5. Delegate (Smart) Decision-Making With Confidence

A core tenant of Agile is to empower teams. Why? These are typically the people with the best understanding of the problems they’re facing. Agility equips team members with the skills to make confident decisions. As a result, Agile leaders should be able to trust the decisions being made—but that’s a very foreign concept for most leaders.

There’s often a misconception that leaders are giving up power in this process. However, they should still inspect decisions to ensure the right ones are being made at the point of challenge or failure. The question is: How do leaders lead empowered teams versus managing, directing, and controlling them? As the leader, it’s a hard transition to make on your own.

It’s crucial that leaders have their transformation partner on hand to observe interactions with their teams in order to provide reflection about helpful habits (as well as to root out unhelpful or negative habits). The partner also should be in the room during key moments to watch the leader in action so that he or she can provide insight and guidance.

6. Still A Leader, New Approach

Leaders still lead. But how do they lead an Agile organization?

We often refer to that as servant leadership. Servant leaders help their teams grow, thrive, and find immense pride in the valuable work they are doing. The basic notion is harnessing collective brainpower over that of just one person.

Servant leaders still ask hard questions, and they let teams fail in safe ways. This way leaders foster an increased understanding that helps team members make sound judgment calls.

More on servant leadership here, 3 Ways To Use Servant Leadership In Your Organization.

 

Being a leader is hard work. However, all leaders are entitled to a little help. Knowing what to expect from those who are meant to support you can make a world of difference. We hope these 6 points help you to maximize the value of your Agile transformation partner.

For more on our approach to building lasting business agility, you can check out our Transformation Services page.

Blog

5 Agile Trends We’re Seeing in 2019

By: David Hawks | Feb 11, 2019 |  Agile Coaching,  Agile Marketing,  Agile Transformation,  Article,  Leadership

We’ve been watching companies thrive—and struggle—for a long time. 2019 is our ninth year as a company and marks over 15 years of my personal work with clients as they transition to Agile. Throughout our time as a team, we’ve identified many key issues and problems that affect companies on their Path to Agility®.

Here are five Agile trends to look out for this year:

1. Companies still struggle with Agile implementation

It’s been 17 years since the Agile Manifesto was created. Unfortunately, there’s still more bad Agile than good, and it’s a bit sad that 17 years later so many companies still struggle to adopt Agile.

Over the last year or two, I’ve been conducting a survey in some of my talks, including when I spoke at AgileCamp 2018 in Dallas. We found that 75 percent of companies undergoing organizational transformation were using Superficial Agility—mimicking Agile practices without truly understanding them.

As stated above, Superficial Agility is a practice where companies adopt Agile methodology without fully comprehending or communicating why. These adoptions often fail because they’re practice-driven versus outcome-driven. These companies tend to implement Agile and Scrum without a clear, tangible goal in mind. If you have an ambiguous goal, you are guaranteed to have a bad outcome.

Remember: Agile is a solution, not an outcome. What we mean is, companies have to understand the business outcomes they want to see, such as delivering to market faster or responding more quickly to market demands. These are business outcomes people can align around and by which companies can measure success. Agile is how they can obtain those results.

2. More companies realize the importance of leadership involvement during an Agile transformation

The good news: Companies are recognizing that getting stuck is more than just a team problem. It’s a leadership problem that requires…

  • Organizational structure change
  • Behavior shifts that impact culture
  • Leaders to adjust their decision-making processes

We are seeing more clients asking for help as they realize leaders have to be a larger part of an Agile transformation to ensure success.

3. More companies are implementing the Scaled Agile Framework® (SAFe®)

Whereas Scrum traditionally takes places at the team level, Scaled Agile Framework (SAFe®) and other scaling frameworks, like Scrum at Scale, etc. take place in large organizations with thousands of team members, managers, and leaders. SAFe® is one of the hottest things among large companies today, and it continues to gain traction.

Unfortunately, we’re seeing companies repeat earlier mistakes made 10 years ago.  Back then, there was a similar sense of peer pressure to implement Scrum. Today, companies are following Agile trends, like SAFe® or Scrum at Scale, without understanding the reasoning or goals behind their practices and processes. As we saw with Scrum, this leads to a lack of business results for the organization.

SAFe® only works when companies become outcome-driven rather than practice-driven. Companies should know why they want to implement SAFe®, have a clear set of objectives they want to achieve, and apply the right amount of process to reach the goals they want to accomplish.

4. There are too many pretenders in the Agile coaching space

I know, I know—this is a bold statement. But let’s be honest. It takes a lot to help companies successfully undergo an Agile transformation. This business pays very well for consultants, and as a result, there are a lot of unqualified people who’ve hung their shingles in the Agile space.

The person hiring an Agile consultant is typically an uninformed buyer, and it’s easy to get snowed. These coaches may not have a deep understanding of how to implement an Agile transformation, how to motivate others, or the nuances of implementing Agile across different corporate cultures.

We’ve seen more and more individuals call themselves Agile coaches, yet they lack the experience and expertise to deliver value and coach organizations through major change. Few Agile coaches truly understand the patterns and challenges of agility because they simply haven’t done enough engagements to recognize them.

5. Agile is expanding outside of IT

This Agile trend has been gathering steam for a few years now. When we break down the core principles of Agile, we’ve found they apply anywhere you deal with complex systems and processes within an organization. Other parts of an organization, such as HR, marketing, and operations, are adopting many of the same practices we’ve been using in technology organizations for years. The need for greater visibility and predictability empowered teams, and a continuous improvement mindset has been identified across all departments.

However, Agile will need some translation when applied outside of IT. It’s not enough to mimic the practices of technology organizations. As always, we recommend being very clear about why the organization is implementing Agile.

Agile Trends From Here On Out

Agile continues to grow through whole-organization Agile transformations, Agile scaling frameworks, and Agile implementations outside of technology. Companies are drastically transforming and are highly responsive to market demands as a result.

Our industry’s challenge now is to avoid repeating mistakes of the past so that a decade from now we don’t end up with a lot of bad SAFe® and bad business-unit agility. Companies that don’t figure out how to get unstuck and achieve their outcomes are in danger of having their business models disrupted by organizations that get it—and 2019 will be no exception.

If you’d like to learn more about how to avoid getting stuck in your Agile transformation, check out our white paper, 8 Common Pitfalls of an Agile Transformation.

Blog

Webinar Recap: What’s Next? Agile Trends in 2019

By: Agile Velocity | Jan 04, 2019 |  Agile Transformation,  Leadership,  Video,  Webinar

2018 was a remarkable year for the Agile community. Agile is now expanding into new departments and industries. Companies are continuing to tackle the challenge of scaling Agile throughout their organization. More and more leaders are getting involved in their organizational transformations every day.

What does this all mean for companies and their use of Agile in 2019?

In our latest webinar, Founder & CEO, David Hawks, and SVP of Client Success, Erik Cottrell, presented the Agile trends they’ve observed in 2018 and during Agile Velocity’s 8 years of business.

You’ll leave with…
– An overview of Agile trends occurring in companies across industries
– Agile transformation mistakes to look out for in 2019
– Quick tips for scaling Agile & implementing frameworks, like SAFe or Scrum at Scale
– Our predictions for the future of Agile


Watch Agile Trends in 2019 Webinar

Blog

3 Ways To Use Servant Leadership In Your Organization

By: Brian Milner | Dec 19, 2018 |  Article,  Leadership

Servant leadership is a term that’s been around for decades. While it can sometimes feel overused or outdated, I believe the principles of servant leadership remain as relevant today as they’ve ever been.

For example, a 2017 Gallup workplace poll found that roughly two-thirds of American employees are either not engaged or are actively disengaged from their work. Employees want their work to have meaning and clear purpose–and they’ll seek out positions where their contributions have a tangible impact. Implementing servant leadership principles helps employees feel more invested in their work, meaning the organization is able to attract and keep top talent.

Applying Servant Leadership To Every Level Of An Organization

At its core, servant leadership is a philosophy that places the needs of employees and teams ahead of the leader with the goal of fostering success. The term was first coined by Robert Greenleaf in the 1970s when he defined the 10 main characteristics of a servant leader.

Today, I’ll look at three of these characteristics–listening, empathy, and awareness– and discuss how they play out in different levels of an organization.

The Executive Level & Listening

Listening is crucial at the executive level. After all, leaders who listen gain much more insight into pertinent issues taking place within the organization.

After listening and really hearing, executives can affect positive change by modeling the behaviors and traits they want to see in their organizations. Showing team members what you expect demonstrates that you are willing to roll up your sleeves and dig in as well. History’s great leaders–Martin Luther King, Jr. and Gandhi, for example–showed the world the change they wanted, proving the best way to create lasting impact is to walk the walk.

Middle Managers & Empathy

Middle managers are there to make sure their teams have the right equipment or facilities to properly do their work. This requires them to be servant leaders to their teams.

The best managers understand how to put themselves in another’s shoes. They should constantly be aware of the tools their teams need to be successful and cast an eye to potential roadblocks that would prevent their teams from agility and high performance. Doing so creates psychological safety among the team. Employees feel free to speak their minds, knowing their opinions and voices will be heard. When a middle manager flexes their empathy skills, it becomes much easier for them to stay in tune with their teams’ needs and protect their sense of safety.

The Team Level & Awareness

Employees can become unmoored from their organization’s purpose if they’re unaware of their own impact. This can lead to hopelessness and dysfunctionality among teams. Team members who can articulate how their roles further their company’s mission are better connected to the strategy of the organization. Furthermore, those who are aware of the purpose behind what they are doing gain the freedom to become more creative, allowing them to find better ways to accomplish the organization’s goals.

Remember, every job within an organization is created to advance the company’s mission. While it’s largely the duty of leadership to communicate an individual’s purpose, the individual should have awareness of how that purpose plays out in their day-to-day.

The Role of Servant Leadership in Agile

Servant leaders lead through influence rather than authority, and they earn the right to lead through their actions. Employing key aspects of servant leadership allows you and your employees to become more engaged at work and perform at higher, longer-lasting levels.

At the end of the day, these are important factors in any organization. But I particularly like to emphasize the benefits of servant leadership in an agile organization. As it turns out, the culture built through servant leadership is ideal for an organization trying to implement Agile or sustain their agility. Benefits like a tuned-in leadership team, psychological safety in the workplace, and engaged employees are vital assets in creating durable business agility.

 

Have you tested out any of the 10 characteristics of servant leadership in your organization? If so, we’d love to hear your stories. Share in the comments below!

Blog

7 Steps to Building Durable Work Relationships and Effective Communication Skills

By: rachel.abrams@agilevelocity.com Cottrell | Dec 13, 2018 |  Article,  Leadership

At work, “stuff” inevitably hits the fan–it’s just a matter of when. However, there are things you can do to ensure important workplace relationships weather any storm, regardless of its fury.

The Problem

We don’t often invest enough time in developing durable workplace relationships. Many of us just hope that when things get difficult, everyone will just play nice. Unfortunately, that approach leaves the door open to discord, friction, and dissent. The good news? I’ve seen many examples of how to build good work relationships, and I’m happy to share them with you.

Effective Communication in the Workplace Takes…You Guessed ItWork

Rather than leaving workplace relationships to chance, modern leaders are working harder than ever to engage with their colleagues. I’ve distilled the work into seven practices to build those durable, storm-worthy relationships. Taken together, these practices can forge lasting workplace partnerships, alleviate tension when things go sour, and mitigate a crisis before it gets out of hand.

1. Build Personal Capital

Invest a little time getting to know the people you work with and what they care about outside of work.

Why: Getting below the surface creates common ground. Discussing hobbies, interests, history, family, or time spent on vacation are a few of the ways you can get to know your colleagues better. It only needs to be for a couple of minutes, and when it’s genuine, you’re making connections that will matter later.

It’s like putting money in the bank for a rainy day–you are building relationship capital. Eventually, things will get difficult and you will have to make a withdrawal. Business is messy, and things go askew. However, when people know their colleagues care, they have a much easier time forgiving or helping out if someone messes up.

2. Be Vulnerable

Appropriately share details about how you feel at work or what matters in your personal life to allow peers to get some insight into how you operate.

Why: Letting others get to know you helps people relate to you and builds trust. You don’t have to overshare (please don’t), but showing a little vulnerability makes you much more approachable. Vulnerability also shows you are willing to both seek and give trust–and frankly, you have to give it to get it.

3. Ask for permission

Secure your coworkers’ agreement to always talk openly and with candor about tough things whenever they come up.

Why: This is powerful. Workplace relationships can withstand storms much better when people engage each other in ways that demonstrate they are committed and agree to do good work together. That means being honest and not shying away from difficult conversations. That little effort enlists their support and helps navigate the difficult discussions about workplace expectations because you have created a safe space to do good work and have real, safe communication in the workplace.

You don’t need a special occasion to do this. Try setting up a quick 15-minute meeting. Mention your need for more candor and insight from colleagues to help you make better decisions. Ask if they’ll agree to offer candid feedback, and offer to do the same in return. End the meeting by saying something like, “We’ve agreed to be candid with each other. Thanks.” Follow up by seeking them out and listening to what they say.

4. Ask for help

Try something many leaders feel is risky. Try inviting coworkers into your challenges to gain their wisdom and insight.

Why: Asking for help allows you to be vulnerable and have honest conversations about issues that are not so electrically charged. Reaching out to others shows you don’t have all the answers. It also makes others feel good about being invited in–people love to help. It’s a simple way to get their expertise, enlist their help, and show your respect. Plus, no one can do it all on their own, and you might find they have really great advice.

5. Listen intently

Be present in the moment, and listen fully to what your colleagues have to say before you contribute.

Why: You are showing your colleagues that you are willing to carve out the time to understand and hear them. You don’t have to agree or even like what you hear, but listening shows you value them enough to make them a priority at that time. It also helps overcome challenges–you can’t solve problems without gaining full context of an issue, and you can’t gain full context without listening intently.

Pro Tip: The basics really matter here. Eliminate distractions by ignoring your phone, text alerts, and emails.

6. Be brave

When it’s time for those difficult conversations, be courageous.

Why: American psychologist Abraham Maslow sums it up: “In any given moment, we have two options: to step forward into growth or to step back into safety.” Don’t shy away from difficult conversations, even though it can be one of the hardest things for people to do. It’s much easier to summon the courage for difficult meetings or conversations when you have invested time in steps 1-4 since laying a foundation of trust in relationships makes summoning courage to work through difficult situations a whole lot easier.

7. Take action

When something important surfaces, act as soon as possible.

Why: Don’t wait days or weeks to have meaningful conversations. Prompt action diffuses emotional energy. If someone is really hurt, time frequently does not heal those wounds. You can nail steps 1-6, but it won’t do any good if you don’t act. Too often, the longer you wait, the bigger the problem grows.

 

Following these steps builds durable relationships, stimulates effective communication in the workplace, and forges lasting workplace relationships that are able to withstand whatever challenges a turbulent business day throws your way.

Do you have any tips on how to have tough conversations at work? Share with me in the comments below!

For information on our approach to building lasting business agility, you can check out our Transformation Services page.

By Holt Hackney, Originally Printed in Architecture and Governance Magazine

In the first couple sentences of “Agile Integration: The Blueprint for Enterprise Architecture,” a recently released report by Red Hat, the authors write: “Business success is increasingly based on your ability to react to change. As new disruptive players enter markets and technology upends what consumers expect, organizations increasingly need to change plans in much shorter cycles than ever before. Modern software architectures and processes can make organizations more effective at dealing with this change and emerging as winners in their markets.”

With the business case spelled out, the report goes on to describe “a new architectural framework called agile integration” that can help “your organization to create a competitive advantage.” This is not to be confused with the traditional “agile software development,” according to the authors.

Rather, the agile methodology, when applied to agile integration, “takes the complexity of existing systems, different data types, data streams, and customer expectations, and finds a way to unify them.

“A distributed integration architecture treats each integration point as a separate and unique deployment,” according to Red Hat, which is a provider of open source software solutions. “The integration can then be containerized and deployed locally for a specific project or team without affecting any other integrations deployed throughout the organization.

“Each instance uses an immutable definition . . . [making] the environment highly repeatable and consistent for each instance, which is ideal for continuous integration and continuous delivery pipelines.”

Erik Cottrell, Senior Vice President of Client Success and Strategy of Agile Velocity, suggested the developing trend was promising.

“Enterprise IT constraints are not new for companies adopting Agility,” he said. “What’s new, and exciting, is how courageous Lean/Agile Enterprises are now responding to IT infrastructure constraints with the same urgency and ingenuity as their application development counterparts. These companies recognize how profoundly IT challenges inhibit their ability to deliver value to their customer base and waste valuable team cycles. These IT innovations are foundational to an enterprise value stream.”

He continued: “Agility offers relief to teams who can’t know more than they do at the outset. By actually working with, and learning quickly from, small batch size teams are able to deliver value and get smarter along the way. Better still, new constraints and challenges are surfaced faster and can be addressed as work is being done, not just during planning or documenting. There’s a myth that no planning is done in Agile, but we find there’s the right kind of planning that actually allows teams to accelerate doing work.”

Near the end of the 19-page report, Red Hat concludes that “agility is a process, not a project” that is essential.

“It has never been more important for organizations to be able to react to change in the market, and it is largely IT systems that must deliver this ability to launch new services or update existing ones quickly. Rethinking IT infrastructure has never been more important, as it is the foundation of digital services.

“Infrastructure teams have historically been tied to very long, modulated processes because of the need to mitigate risk and maintain stability. However, it is possible to shift the mindset of infrastructure from hardware or platform-based to integration-based. Integration is not a subset of infrastructure.” Elaborating on this, the authors note that “it is a conceptual approach to infrastructure that includes data and applications with hardware and platforms.”

To achieve the aforementioned “agile integration,” the authors suggested three technology pillars:

Distributed integration, which uses messaging and enterprise integration patterns to integrate data and systems. These are broken down into small, team-driven integrations that are distributed, as needed, across projects and touchpoints.

Internal API management, which creates a reusable set of interfaces to allow development teams to engage with applications and systems. APIs provide guidance and structure to how applications should interact.

Containers, which allow integration projects to be closely aligned with development and operational projects and enable integrations to be developed, tested, and released similarly to software projects using DevOps methods.”

These resonate with leaders like Cottrell, whose company is at the heart of the “Agile” movement in Austin, Texas.

“These three pillars allow teams to get to ‘done’ by providing the necessary access to and integration with key technologies without waiting in an IT queue, where the request has to be prioritized against other, unrelated requests,” he said. “By giving teams access to these building blocks, they’ve reduced friction and allow for remarkable acceleration at scale, all without losing necessary discipline or appropriate controls.”

Red Hat put the proverbial exclamation point on the concept in its report when it wrote that “technology has to be used to support culture change, and that means working to make infrastructure teams—and not just their software—more agile.” A&G

View the Article PDF Here