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
Since then, around 115 professionals from 12 countries, spanning various industries like softwaredevelopment, consulting, manufacturing, and marketing, have taken the online course. The course boasts of an 89 percent completion rate, thus proving its value.
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." The project ran successfully for hardware development, and the project management tools worked exactly as expected.
Many softwaredevelopers will tell you that the whole history of the software industry can be described by increasing levels of abstraction. For product designers, the first implication of the software-replaces-hardware trend is that a much higher proportion of the value of a product will be in the electronics.
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 software code to be delivered to customers as soon as it is completed and tested.
By 2004, RIM had acquired 1 million subscribers and only three years later surpassed the 10 million mark. A second accelerant of IT delivery is the iterative softwaredevelopment philosophy known as "agile development." In 1998, RIM launched the BlackBerry. A year later, the second version got a full keyboard.
Failure to engage developers. The platform owner must also show softwaredevelopers what’s in it for them if they contribute. In 2013, Johnson Controls invited developers to help them build Panoptix, an energy efficiency platform for buildings and office space.
Collins worked primarily on IT related work, such as systems integration and softwaredevelopment. In 2004, when ZeroChaos , a provider of contingent workforce solutions, began courting IBM as a customer, IBM was concerned with losing the war for engineering talent to new startups such as Yahoo and Google.
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.
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.
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.
This involved replacing people with machines to do the same work, but such systems are inflexible and not able to adapt to new challenges unless a person steps in to make changes (Ake et al, 2004; pg 27). Ake et al, 2004; pg 266). Technology has its role in every workplace, but the lights are back on for the people in the room.
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