2004 Management Software Developers 
Boxes and Arrows
FEBRUARY 3, 2012
Agile and Iterative Development: A Manager’s Guide. Pearson Education, 2004. [2] “Agile Development: Lessons learned from the first scrum” Cutter Agile Project Management Advisory Service, Executive Update, Vol. 20, 2004: [link]. [3] User Stories Applied: For Agile Software Development.
hackerearth
DECEMBER 8, 2017
Leaders and managers can design the way they lead, manage, innovate, and create. A popular misconception is that design thinking is riskier than the traditional business approach that managers take to solve a problem. Design thinking is not just for products; the concept can be applied to the workplace itself.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Harvard Business Review
MARCH 28, 2012
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." Like many companies, Exotech struggled with serious time delays in its product-development projects. The results?
Harvard Business Review
JUNE 9, 2015
What I’m referring to is the migration of functionality from hardware to software. Many software developers will tell you that the whole history of the software industry can be described by increasing levels of abstraction. Software development will be more complex.
Harvard Business Review
NOVEMBER 19, 2015
Working with an Israeli software development company, AppFront, we invested six months and more capital than we ever thought possible on it. Some teams decided to hoist their general manager in the air for the picture; others formed human pyramids. It takes a careful mix of mission, management, and culture.
Harvard Business Review
MARCH 31, 2016
Studying these successes and failures, we’ve identified half a dozen key reasons platforms fail, all of which boil down to managers’ misunderstanding of how platforms operate and compete. Steve Jobs failed miserably at managing openness at Apple in the 1980s. Failure to engage developers. Insight Center.
Harvard Business Review
MAY 4, 2018
The methodology is Continuous Development, which, like agile, began as a software development 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.
Expert insights. Personalized for you.
107 
Let's personalize your content