This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Further, automation has become a core strategy as organizations migrate to and operate in the cloud. More than 70% of respondents to a recent McKinsey survey now consider IT automation to be a strategic component of their digital transformation strategies. However, turning those logs into meaningful insights requires a data lakehouse.
The huge popularity of value stream management (VSM) in software delivery — Forrester, GigaOm and Research In Action have published reports on the market in recent months— stems from its ability to help IT leaders to better align their software delivery with business outcomes and strategy. What is Value Stream Management (VSM)?
They are all likely to exist in some kind of silo that’s difficult to access from the outside the group that created the silo–and the reason for that difficulty may be political as well as technological. What will cause those trends to end, and what strategies will the business need to adopt?
The DevOps Handbook was published last year, and I think that will put the question to eternal rest. Even though there are numerous other books (and opinions, for that matter) on the subject, I believe The DevOps Handbook will become the de facto arbiter of what officially is and is not “DevOps.”
As the podcast takes a break for the summer, now is the perfect time to take a look back on some of the best thought leadership on technology and business modernization. Episode 15: Adrian Cockcroft, VP of Cloud Architecture Strategy, Amazon Web Services. Episode 28: Pieter Jordaan, Group Chief Technology Officer, TUI.
But the other thing is to be able to take operational concerns into account during your design development and implementation of any technology. So if you’re using their database container or technology, guess what? Jeff: And then from there, diving into any of the DevOps handbook. You didn’t do anything.
The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations. In Project to Product, Value Stream Network pioneer and technology business leader Dr. Mik Kersten introduces the Flow Framework –a new way of seeing, measuring, and managing software delivery.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content