CorporateIntel

APRIL 1, 2012

A software bug caused it to be withdrawn. Information compounds on our desktops, the team with analysis paralysis most often loses to the nimble risk takers—but all this means is that in product development , the role of Quality Assurance (QA) has never been more critical. You don’t hear that one too often.

Software Review 40

Software Review Underperforming Technical Team Technical Review Software 40

Harvard Business Review

FEBRUARY 2, 2012

The fundamental asymmetry, of course, is the presence of bonuses and an absence of clawbacks. That is, individuals and teams may receive impressively large and ostensibly "performance-based" bonuses if they hit their numbers. Developing better software would have paid less. Yes, the sales team was (ultimately) fired.

Underperforming Technical Team 15

Underperforming Technical Team Software Review Development Team Review Technical Review 15

Harvard Business Review

MARCH 20, 2012

Teams can be highly effective even when members have never met in person. In fact, virtual teams can actually outperform traditional co-located groups. Dispersed teams can outperform co-located ones only if — and this is a big "if" — they are managed properly. Here are a few guidelines: 1. Put processes in place.

Underperforming Technical Team 20

Underperforming Technical Team Guidelines Project Software Development 20

Harvard Business Review

MAY 13, 2011

And by integrating Skype with its free cloud offerings — such as its free version of Office software — Microsoft multiplies the linkages and the revenue potential. Of course they can, but getting the right internal structures to facilitate this is tricky. Leave the Skype unit to promote product development and user growth.

How To 16

How To Development Team Review Software Review Software 16

Harvard Business Review

JUNE 19, 2017

If software has eaten the world, then agile has eaten the software world. For example, a Google search for “agile software development” returns over 14 million results. The bulk of this agile canon will teach your individual teams to deliver higher-quality code, faster.

Agile 8

Agile Software Review Technical Review Development Team Review 8

Harvard Business Review

JULY 6, 2012

First, the teams behind winning apps tend to be composed of the organizations' best techno-marketing talent, people with deep understanding of social media. Second, they take a few basic ingredients — brand, marketing, technology, and service — and combine them in just the right ways over the course of five stages.

Underperforming Technical Team 15

Underperforming Technical Team Course Data Policies 15

Harvard Business Review

JANUARY 26, 2015

The innovation roadmap was hauled out and reviewed less in the spotlight of global opportunities than the cold reflection of domestic politics. These questions, of course, aren’t hypothetical. Strategic success required pleasing Vladimir Putin’s Kremlin. The room went quiet. No one disagreed. Insight Center.

Development Team Review 13

Development Team Review Software Review Disruption Roadmap 13

Harvard Business Review

JULY 22, 2015

In addition to receiving traditional training, each participant designs and carries out a 100-day project that targets an important business challenge, such as increasing the firm’s footprint in the health care segment or developing new software to enhance mobile phones (these are real examples). Do it fast.

Project 15

Project Design Learning Underperforming Technical Team 15

Harvard Business Review

MAY 24, 2012

Software development is a frenzied decathlon of activity, constantly pressed on all sides by resource constraints, budgets and deadlines. Few members of the team are harder hit by this reality than the user experience and design staff. Waterfall development lays the wrong foundation. Course correction was possible.

Agile 16

Agile Software Development Software Developers Design 16

Harvard Business Review

JULY 4, 2016

” Makers, also known as individual contributors, are the software developers, engineers, architects, writers, and researchers who produce knowledge. This is particularly true in organizations where employees are both, what Paul Graham calls, “makers” and “managers.”

Meeting 14

Meeting Management Software Development Software Developers 14

Harvard Business Review

SEPTEMBER 9, 2014

Of course, the pricing is always what signals the problem, but behind that it is how the innovation process is set up. However, our experience has been that [when a product fails] it’s not a technology problem or a pure R&D problem — it is really around marketing, customer segments, and of course pricing.

Survey 14

Survey Innovation Processes Marketing Course 14

Harvard Business Review

MAY 22, 2018

I wasn’t a software engineer, and I was tempted to leave agile methods to the geeks. I watched videos and took certification courses. The best learning experiences, however, came from sitting with strong agile teams. Nearly every company I visited in my work as a consultant turned out to have agile teams running somewhere.

Agile 15

Agile Software Engineering Course Learning 15

Harvard Business Review

JUNE 27, 2016

In India, workers had yet another interpretation: they saw the shorter cycles as a way to align their processes and skills with developers around the globe, who they believed were also moving to more rapid cycles, and they applauded the move as a way of forcing more engagement with customers earlier in the process.

Culture 15

Culture Collaboration Software Development Software Developers 15

Harvard Business Review

JANUARY 8, 2013

For one marketing services firm, it meant being exposed to their biggest client's development teams and sitting through technical tests and focus groups to better appreciate and understand how its products were actually designed and built. What does it mean for your company and industry? What should it mean? And the rest won't talk.).

LEAN 10

LEAN Innovation eBook Video 10

Harvard Business Review

JUNE 8, 2018

Digital companies, however, consider scientists’ and software workers’ and product development teams’ time to be the company’s most valuable resource. This notion, that risk is a desirable feature, can seem like sacrilege to anyone who’s taken an introductory finance course.

Report 8

Report Development Team Review Project Resources 8

Harvard Business Review

JULY 19, 2017

Based on our experience working with these teams, we recommend senior teams do the following if they want to become more agile: Treat your enterprise priorities as a managed backlog. See your leadership team as an agile Scrum that prioritizes the backlog based on importance, then tackles them in sequence until completed.

Agile 8

Agile Underperforming Technical Team How To Leadership 8

Boxes and Arrows

DECEMBER 23, 2014

In a flash of insight, he realized that software could replace pencil-and-paper accounting for everyone. They had users try their new software, Quicken, while they ran a stopwatch. Then they’d tweak the software and retest until processes that took an hour were reduced to a quarter of that.

Design 104

Design Software Review Underperforming Technical Team Software 104