Strategic advice to leverage new technologies

Technology is at the heart of nearly every enterprise, enabling new business models and strategies, and serving as the catalyst to industry convergence. Leveraging the right technology can improve business outcomes, providing intelligence and insights that help you make more informed and accurate decisions. From finding patterns in data through data science, to curating relevant insights with data analytics, to the predictive abilities and innumerable applications of AI, to solving challenging business problems with ML, NLP, and knowledge graphs, technology has brought decision-making to a more intelligent level. Keep pace with the technology trends, opportunities, applications, and real-world use cases that will move your organization closer to its transformation and business goals.

Subscribe to Arthur D. Little's Technology Newsletters

Insight

This Executive Update describes two security challenges in the design of Web applications and how they can be addressed: the client-side equipment and the network

This Advisor is a continuation of the "Scrum Ain't Enough" series (see "Agile Analytics: Community, Customers, and and Collaboration," 18 October 2011, and "

Enterprise architecture has moved away from a purely IT role and is increasingly involved in business architecture and strategy planning. This is particularly evident in the rapid adoption of capability-based analysis.

This is a positive change. Enterprise architecture -- as the organizing logic for business processes and IT infrastructure -- has become more widely recognized as the embodiment of strategy.

With the term "devops" picking up steam, vendors are now (re)branding their tools as devops tools. Similar to unit-test tools that supported an agile workflow, the current discussion on deployment automation supports the devops ideas. Even though tools have their merits, after reading the August 2011 issue of Cutter IT Journal -- "Devops: A Software Revolution in the Making" -- it should be clear that tools are merely one aspect of devops and must be complemented with other aspects. The nice thing about tools is that they give you something concrete to discuss, as compared to the more intangible notion of "culture." Within large enterprises, tools are probably the easy part. Therefore, this issue focuses on the harder aspects, like "people and processes," or as the Agile Manifesto puts it, "Individuals and interactions."

The ultimate victory will depend on the hearts and minds of the people who actually live out there.

-- US President Lyndon Baines Johnson

On the dev2ops blog (one of the primary locations for seminal devops thought), Alex Honor states his chosen methodology as "People over Process over Tools."1

It would seem that the devops discussion is mostly driven by development's incentives, and appropriately so, given developers' focus on building functionality for the business user.

Agile software development strategies took the world by storm in the early 2000s.

Devops as a cure for the dysfunctional gap between development and operations is here to stay. Complex applications built as an orchestration of highly distributed services, some internal, some outsourced, demand that development and operations find a common language in which to collaborate.