Author: Tim Curless

  • Achieving Organizational Change Through Scaled DevOps

    Achieving Organizational Change Through Scaled DevOps

    The rapid pace of technological change has had a major impact on customer expectation, forcing IT decision-makers to adopt agile processes to ensure the continual delivery of innovation. This has led to the mass adoption of DevOps practices, with 77% of organizations indicating they rely on DevOps to deploy software, or plan to, in the near future.

    DevOps is a key ingredient for building and deploying better software faster. It enables developers to spend less time on onerous tasks and more time creating new features that drive competitive advantage and elevate customer experience.

    But, for DevOps to streamline organizational change, it can’t be a one-off initiative. Scaled DevOps requires aligning team members on common goals and best practices and establishing a DevOps maturity model tailored to a company’s individual needs. This is no easy lift and has led teams to abandon DevOps initiatives before they even get started. While the road to scaled DevOps can be daunting, the benefits can have a positive ripple effect across the organization.

    Business

    The business benefits that accompany DevOps are endless. Think: expanding your customer base, spearheading organizational readiness and achieving unmatched speed. As the consumer landscape continues to change, you will be able to adapt accordingly to generate new features and pathways to customers. Plus, DevOps provides a prime opportunity to get more information from your client base and relay it back to developers, equipping your organization with opportunities to learn from its failures and develop a company-wide, reflective model that better accommodates customer demands.

    Once your organization establishes a successful DevOps practice, it will be better prepared to take on other emerging trends and undergo a full-scale digital transformation. With DevOps as the catalyst for change, you can surpass competitors and disrupt the industry with innovative ideas, enabling you to stay ahead of the curve. Once an organization is fully committed to DevOps practices, the company will also enjoy a competitive advantage due to increased speed by empowering your business to provide customers with capabilities faster than rival industry players.

    Culture

    DevOps may require a daunting corporate culture makeover, but it also allows businesses to enjoy unbeatable cultural benefits by improving communication, establishing a foundation for continuous learning and boosting corporate morale with more meaningful work. When effective processes for communication are in place, employees can avoid the misunderstandings and missteps that often lead to failed initiatives and low morale. Once DevOps improves communication between teams, it sets the stage for more collaboration and cross-departmental education, allowing an organization to develop new operational efficiencies and empowering staff with highly specialized knowledge. With reduced inefficiencies, team members are empowered with more free time to create and meet new goals, plus budding talent from competitors will be drawn to your organization’s innovative environment.

    Operations

    Empowered by scaled DevOps, businesses will enjoy huge operational and technical rewards with automation, controlling costs and revamping security practices. Since establishing a DevOps practice requires the successful adoption of automation processes, a DevOps initiative includes the same key benefits that automation boasts by delivering the coveted digital experiences that consumers, employees and stakeholders demand. Automation not only meets these demands, but also sets the groundwork for a DevOps journey with CI/CD pipelines that automate software releases to rid your organization of manual release challenges.

    On the financial front, as your company moves toward a consumption-based economics model for things like public cloud, your DevOps practice will help control costs and environments by alleviating unused tools. In the long run, improved security will also prove profitable because there is no fiscal nightmare worse than a breach. Upon defining your DevOps model, compliance and control are not only maintained, but rapidly transformed through automated policies and configuration management.

    With knowledge of the transformational qualities that come with an effective DevOps approach, IT leaders are eager to adopt DevOps to improve efficiency, boost profitability, deliver superior customer experience and establish a culture of empowerment. However, they must understand that successful DevOps initiatives do not happen overnight. DevOps is reliant on continuous testing and education to ensure that companies can keep pace with their new collaborative culture, rapid delivery process and new technologies. Nevertheless, motivated by the promise of positive business, operational and cultural transformations, organizations will be more willing to prioritize the key credentials necessary to start, and maintain, an efficient DevOps practice.

    — Tim Curless

  • The ‘Mad Men’ Approach to Pitching DevOps

    The ‘Mad Men’ Approach to Pitching DevOps

    It’s been said that the mark of a good salesman is having the ability to sell ice to an Eskimo. And, if you’re familiar with the 1960s-era T.V. hit “Mad Men,” you know that ad exec Don Draper could do just that. His character was debonair, brash and unapologetic—but one hell of a businessman.

    So, what does a smoke-filled, Madison Avenue ad agency have to do with DevOps? Well, if you’re in the market of adopting (and selling) the methodology to the powers that be, the parallels are abundant.

    Before we dive into those similarities, let’s tackle some fundamentals of the DevOps movement, as well as the benefits and value of the agile-inspired approach. DevOps focuses on rapid IT service delivery through the adoption of agile, lean practices with an emphasis on people and company culture. The collaborative practice utilizes automation tools to bridge Dev and Ops teams together throughout the entire service life cycle, from design to the development process to production support.


    Related Content:

    DevOps: The Innovation Power Couple

    Executive Buy-in May Be Preventing DevOps Success


    While that’s a broad definition of DevOps, the specific benefits are vast: Faster software releases with fewer defects; increased operational efficiency; and improved scalability, security and compliance (not to mention a substantial savings in time, money and resources). By practicing DevOps, you also attract a top-notch, hungry talent pool, as well as a different generation and brand of customer.

    For instance, let’s compare TransUnion, a 50-year-old company, versus Credit Karma, a 10-year-old company. In this day and age, folks in their 20s and 30s manage their finances differently than baby boomers—and need an agile, modern and DevOps-forward company that can operate like a startup on an enterprise level (granted, Credit Karma consumes data from TransUnion and other reporting bureaus). For years, we only saw our credit report when we applied for a loan or mortgage. Enter a smartphone app that enables consumers to view their credit report on-demand and the game changes. The TransUnions of the world see this and realize they, too, need to pivot and adjust to their market. Catch my drift?

    With that said, let’s get back to our “Mad Men” DevOps scenario. One of Don Draper’s more notable quotes was, “Change is neither bad or good; it simply is.” You often hear a similar phrase of “adapt or die” in the tech world, and this is particularly true for DevOps adoption.

    So, how do you sell this critical undertaking to the suits in the boardroom? To start, let’s look at three key components of any effective ad campaign pitch: the support of your team, a ton of preparation and a killer presentation.

    Don’t Go It Alone

    There are mixed opinions on whether DevOps adoption is a top-down or a bottom-up initiative, but I’m from the school of thought that it’s both. The key to an effective DevOps approach is not only getting buy-in from leadership, but also getting your Dev and Ops teams to collaborate on a common goal (such as agility or security) and to be willing to adapt to change.

    Think of your colleagues as your creative department in an agency setting: Without their feedback and support, your pitch is likely to fail (and you’ll become the heavily ostracized, needle-nosed “Pete Campbell” of the office).

    Some advice? Become a DevOps evangelist and seek out department innovators to help spread your message. Start small and organize a lunch-and-learn. But, most of all, get people excited and ask for constructive criticism.

    Start with the ‘Why’

    When formulating a business case for DevOps, the most important question to ask is, “Why?” Put yourself in the c-suite’s shoes, understand their management and company goals and find ways to align your strategy with those.

    For example, maybe your CIO is concerned by the cost of application delivery. Work to calculate the cost of an application by estimating staffing costs, labor hours, number of deployments/releases and the potential cost of a production failure—and how practicing DevOps would reduce that costly downtime.

    You’re the ad executive making the pitch—the Don Draper of DevOps, if you will. If you can’t prove its value and make the room as excited about DevOps as you are, you’ll be leaving the boardroom with your tail between your legs.

    Speak Their Language

    Most management doesn’t care about speeds and feeds, so tailor your message according to your audience. While tech folks care about features, non-technical people are excited about benefits, particularly how they outweigh the costs. Consider advantages like faster release times, attracting new customers and creating fewer unplanned outages.

    It’s important to think of these business executives as the ad agency’s client. And, while the concept of DevOps won’t fit into an “elevator pitch” format, try to keep the meeting as brief as possible (providing lunch doesn’t hurt either!). Don’t gloss over
    fundamentals, but ask questions to gauge your audience’s knowledge and adapt your content to further their understanding.

    And, most importantly, keep the jargon to a minimum.

    Finally, I’d be remiss if I didn’t mention one final piece of pitch advice from our resident ad man: “Make it simple, but significant.”

    — Tim Curless