We are eager to announce a beacon of light to help penetrate the post-holiday fog: Forrester’s DevOps Benchmark Survey for 2017 is officially live! Led by myself and Researcher Elinor Klavens, this benchmark survey serves as the backbone for a large portion of our DevOps research, facilitating the identification and tracking of trends and supporting our research including predictions for the future. Pivotal to many of our reports, this is your opportunity to shape our research, including our upcoming report “Six Trends That Shape DevOps Adoption In 2017 And Beyond.”
The DevOps survey expands on the extensive data contained in Forrester’s Business Technographics survey, drilling into the context, adoption, use, and plans with DevOps. The research team uses the survey’s findings to provide deeper, more informed insights to help guide your DevOps journey. Questions - including how you are dealing with the business mandate of velocity, how DevOps is changing your culture, and where you see DevOps heading - are partnered with practical use of tools and automation.
No matter where you are on your DevOps journey, please take five minutes to complete the survey! All participants can receive an executive summary of the results of the survey after it closes on February 13, 2017.
Additionally, should you want to share your DevOps experiences in more detail or provide more feedback please connect with me at RStroud@Forrester.com or @RobertEStroud
Enterprises today are focusing on delivering applications faster to drive customer experiences and drive business transformation to meet rising expectations. For some, faster delivery is simply faster time to disappointment where the delivery process is shoddy and speed is the only metric. Speed without quality in an oxymoron – and extremely dangerous. The automation of the process known as Application Release Automation (ARA) is one of the critical impediments in the DevOps journey for I&O organizations today. ARA tools are designed to remove errors from manual processes by standardizing and automating the movement of applications with middleware and infrastructure – the critical final step in the delivery pipeline of applications to deliver customer value.
Continuous delivery is the goal; ARA tools are the vehicles to get there
Over the past 25 years, many organizations have modelled their support – and in some cases their delivery organization – after the ITIL frameworks and processes. For many, ITIL has been helpful in establishing the rigor and governance that they needed to bring their infrastructure under control in an era where quality and consistency of service was critical and technology was sometimes fragile.
Today, we are 5 years into “The age of the customer” – an era where customer obsession is driving technology and which demands a culture of speed and collaboration to differentiate and deliver extraordinary customer experience to drive business growth. In this era, the rise of mobility and the race to deliver differentiated business processes is critical to success. Your development teams are driving velocity and elasticity with increased quality and availability, leveraging DevOps practices and often driving change directly to production.
This transition has led some organizations to experience friction between the competing priorities, velocity and control, especially for those who continue to execute on the traditional model of ITIL.
ITIL is starting to show signs of age. That does not mean it is on the verge of demise. ITIL must adapt. To understand the relevance of ITIL and IT Service Management practices in this era of Modern Service Delivery, Eveline Oehrlich and Elinor Klavens and I have embarked on a review of ITIL and the use of IT Service Management practices supporting todays BT agenda.
Looks a bit like sci-fi, right? But it's happening right now. Two vendors, one in the US, one in Europe, take somewhat different approaches to robotic parking:
Boomerang positions its offering as RoboticValet, a service that serves two customers. For property owners (developers, real estate investment trusts), Boomering solves a key problem: The high price of real estate in places like Miami, Chicago, or San Francisco. Robotic valets can save significant space, allowing developers to build more profitable buildings. And for consumers -- that is, buyers of the condominimums -- Boomerang's service is a luxury amenity: A 24/7 valet service that drops their car off to the same spot every time.
Serva TS can retrofit existing garages to 'expand' usable space. Serva TS reports gaining 40% capacity in an existing garage space, making it a less disruptive and expensive solution for garage expansion. For customers, there's a smartphone app: As soon as your flight lands, you can summon your car, which a robot will bring to the designated spot.
I interviewed companies from a variety of verticals – travel, retail, energy, clothing, financial services – and spoke to thought leaders in innovation theory to help I&O leaders solve a series of problems: How can we innovate using customer-facing interaction technologies such as mobile devices, robotics, digital signage, and virtual reality (VR)? How can we establish a device innovation lab (DIL) to help technology and business leaders at our company develop technology-infused, customer-obsessed strategies? And what are the success factors for DILs – from mission statement to staffing to key performance indicators?
In the context of my report, a device innovation lab is an a in-house space for designing, experimenting, piloting, and deploying device-based innovation projects. Done right, a DIL can differentiate your business's digital business efforts in impressive ways. Take, for example, Lowes' robotic retail associate, OSHBot.
By "robots," we mean all forms of automation technologies, including those that conductphysical tasks, intellectual tasks, or customer service tasks (which mix elements of both physical and intellectual activities, but which constitute a distinct category in the age of the customer). Indeed, some impressive new technologies are becoming incredibly useful in a variety of organizational settings. Take, for example, Rethink Robotics' Baxter robot, seen in the video below. Unlike traditional industrial robots, it's safe for workers to be around Baxter -- and it's imperative, too. Because software engineers don't program Baxter; human colleagues simply move the robot's arm to teach it new actions, and it learns in real time.
A few months ago, I blogged about testing quality@speed in the same way that F1 racing teams do to win races and fans. Last week, I published my F(TA)1 Forrester Wave! It examines the capabilities of nine vendors to evaluate how they support Agile development and continuous delivery teams when it comes to continuous testing: Borland, CA Technologies, HP, IBM, Microsoft, Parasoft, SmartBear, TestPlant, and Tricentis. However, only Forrester clients can attend “the race” to see the leaders.
The market overview section of our evaluation complements the analysis in the underlying model by looking at other providers that either augment FTA capabilities, play in a different market segment, or did not meet one of the criteria for inclusion in the Forrester Wave. These include: 1) open source tools like Selenium and Sahi, 2) test case design and automation tools like Grid-Tools Agile Designer, and 3) other tools, such as Original Software, which mostly focuses on graphical user interface (GUI) and packaged apps testing, and Qualitia and Applitools, which focus on GUI and visualization testing.
We deliberately weighted the Forrester Wave criteria more heavily towards “beyond GUI” and API testing approaches. Why? Because:
Software is getting smarter, thanks to predictive analytics, machine learning, and artificial intelligence (AI). Whereas the current generation of software is about enabling smarter decision-making for humans, we’re starting to see “invisible software" capable of performing tasks without human intervention.
One such example is x.ai, a software-based personal assistant that schedules meetings for you. With no user interface, you simply cc “Amy” on an email thread and she goes to work engaging with the recipient to find a date and optimal place to meet.
It’s not a perfectly automated system. AI trainers oversee Amy’s interactions and make adjustments on the fly. But over time, she becomes a great personal assistant who is sensitive to your meeting and communication preferences.
One can imagine Amy extending into new domains — taking on parts of sales/customer service operations or business processes like expense management and DevOps. Indeed, we’ll see a new generation of AI-powered apps, as predicted here.
This weekend, I’ll be heading off to Las Vegas for the 2015 Consumer Electronics Show (CES). Infrastructure & Operations leaders should – and do – keep tabs on the news coming out of CES. In this era of consumerization, bring-your-own (BYO) technology, and Shadow IT, CES announcements affect the I&O role more than ever before. I have three tips for how to think about CES 2015:
Look at consumer technologies through a workforce lens. So many smart, connected products quickly migrate to the workforce. Sometimes these technologies enter via BYO and segue into company-owned, as tablets have done over the past few years. In other cases, vendors that target consumers immediately see the value their products can bring to workforce scenarios. For example, I recently spoke with Jonathan Palley, CEO of Spire, a wearable device that tracks not just activity but also state of mind (tension versus calm, focus versus distraction, and related states). While the product was launched to the consumer market just about a week ago, Jonathan made clear that “workforce is a huge part of our strategy as well.” Imagine helping workers remain in a more productive, less stressed state of mind via wearables.
I’m sitting on my sofa at home (Yes! Home!) on Sunday morning just before Christmas. I’m “shut down” for the holidays now, but of course, I’m watching Twitter and now listening to my brilliant friends Chris Dancy and Troy DuMoulin discussing CMDB (configuration management database) on the Practitioner Radio podcast. It’s a marvelous episode, covering the topic of CMDB in with impressive clarity! I highly recommend you listen to their conversation. It’s full of beautiful gems of wisdom from two people who have a lot of experience here – and it's pretty entertaining too!
I agree with everything these guys discussed. In particular, I love the part where they cover systems thinking and context as the key to linking everything conceptually. I only have one nit about this podcast, and the greater community discussion about CMDB, though. Let’s stop calling this “thing” a CMDB!
I coauthored a book with the great Carlos Casanova (his real name!) called The CMDB Imperative, but we both hate this CMDB term. This isn’t hypocritical. In fact, we make this point clear in the book. Like the vendors, we used CMDB to hit a nerve. We actually struggled with this decision, but we realized we needed to hit those exposed nerves if we were going to sell any books. Our goal is not to fund a new Aston Martin with book proceeds. If so, we failed miserably! We just wanted to get the word out to as many as possible. I hope we've been able to make even a small difference!