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
We hear them explain that their current softwaredevelopment is expensive, deliveries are rarely on time, and random bugs appear. The explanation from softwareleadership is often unsatisfying or unclear. Let’s assume that you’ve already expressed your frustrations with technical leadership.
Step 1: Start With a Small-Scale Pilot The journey began in 2022 when Vanguard initiated a pilot within their ChiefTechnologyOffice and IT department, focusing on improving the softwaredeveloper experience. Leadership support was crucial, but grassroots adoption by teams made the real impact.
Consider the battle waged by IBM’s softwaredevelopment teams between competing methods for getting closer to customers. The issue arose as a result of changes to IBM’s business model for software. In the past, IBM mostly provided enterprise software to customers who installed it on their own computers.
It requires strong leadership from all senior IT executives, as well as new business acumen. Requirements and specifications are more flexible and developed within cross functional teams with constantly evolving business needs. New, more agile , softwaredevelopment tools and testing methods are utilized.
In the latest Mik + One podcast, Dr. Mik Kersten, ChiefTechnologyOfficer at Planview, sat down with Dr. Suzette Johnson and Robin Yeman to discuss their groundbreaking work on Industrial DevOps and its potential to revolutionize the development of cyber-physical systems.
We organize all of the trending information in your field so you don't have to. Join 29,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