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
Early agile pioneers were working on in-house IT projects (custom software) or enterprise software [ 1 , 2 ]. The economics are different in selling consumer products than when developingsoftware for enterprises—UX matters more for consumer products. Larry makes money even if people can’t use his software.
Here's a case in point: In 2004, my HBS colleague Gary Pisano and I conducted a project at a leading manufacturer of highly sophisticated production equipment for the electronics industry, which I'll call "Exotech." So the company assumed the software team would, too. But the results were much different on the software side.
What I’m referring to is the migration of functionality from hardware to software. They come second to innovations in computer code. But I’ve found that they’re less cognizant of how software has transformed other fields that we traditionally think of as hardware-based. Insight Center. Growing Digital Business.
The methodology is Continuous Development, which, like agile, began as a softwaredevelopment methodology. Rather than improving software in one large batch, updates are made continuously, piece-by-piece, enabling softwarecode to be delivered to customers as soon as it is completed and tested.
Working with an Israeli softwaredevelopment company, AppFront, we invested six months and more capital than we ever thought possible on it. Last month, I visited all of our U.S. restaurants to introduce our new ordering app to employees. The app was a big technology project for us.
He charged developers for toolkits – inhibiting the very software producers he should have wanted on Apple’s platform. The result was that Apple struggled to create a robust platform connecting Apple customers and software producers. Failure to engage developers. Yet platforms can become too open.
By 2004, RIM had acquired 1 million subscribers and only three years later surpassed the 10 million mark. However, the new handset, its software, and the available applications all failed to excite critics and customers. A second accelerant of IT delivery is the iterative softwaredevelopment philosophy known as "agile development."
One of the most significant came in early 2004 when we decided to relocate from San Francisco to Las Vegas. We also lost some good people: Our star softwaredeveloper loved San Francisco and decided not to leave. In the years since Zappos was founded, we’ve had to make some big decisions. Culture That Drives Performance.
Innovative, proudly geeky Norwegian software company, Trolltech , an open-source pioneer, landed a contract with the mobile division of Sharp, the Japan-based consumer electronics global powerhouse. Collins worked primarily on IT related work, such as systems integration and softwaredevelopment.
These were all true of Charlie, a champion I met in 2004 just as the tech world was beginning to show signs of life after the dot com implosion. At the time, Charlie was an internet security specialist at IBM, and I was running business development at a company called Zone Labs.
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