Acuvate

NOVEMBER 23, 2018

It is a set of practices that automates the process between software development and IT teams. The process involves building, testing and releasing the software faster and more reliably. This means that any commit that happens to the solution by dev team will trigger the build immediately.

Software Review 40

Software Review Development Team Review Technical Review Software 40

CorporateIntel

APRIL 1, 2012

A software bug caused it to be withdrawn. There is no argument that we live in a world of staggering speed, where competitors race to meet customer needs and time to market matters. I have often heard the mantra from development teams: “Better, Faster, Cheaper—we can give you any two and a half.”

Software Review 40

Software Review Underperforming Technical Team Technical Review Software 40

Harvard Business Review

JULY 4, 2016

When it comes to designing and leading meetings that produce results , when you meet matters just as much as how you meet. ” Makers, also known as individual contributors, are the software developers, engineers, architects, writers, and researchers who produce knowledge. Please do not disturb.”

Meeting 14

Meeting Management Software Development Software Developers 14

Harvard Business Review

MARCH 28, 2012

As part of this effort, the company decided to use tools to drive high levels of performance on a new project that required both hardware and software components. The project ran successfully for hardware development, and the project management tools worked exactly as expected. But the results were much different on the software side.

Software Review 16

Software Review Software Development Software Developers Development Team Review 16

Harvard Business Review

MARCH 11, 2013

Big, successful companies that manage huge projects like highways and dams and office parks have to deal with many more variables than a software development team. Granted, they have fancy project management software to help them stay on top of the schedule. Keep your team informed. It's funny, though.

Project 21

Project Management Underperforming Technical Team Software 21

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. For a software project, useful metrics might be lines of code that have been written and bugs per line. Communicate less — but in the right ways.

Underperforming Technical Team 19

Underperforming Technical Team Guidelines Software Development Software Developers 19

Harvard Business Review

JULY 2, 2015

Your team has identified an important goal to hit, challenge to be addressed, or opportunity to be pursued. You call a meeting or two, set objectives, put a plan together, and start to execute. Certain objectives are harder to meet than you had hoped. I’ve found 30-60 minutes is optimal for most debriefing meetings.

Underperforming Technical Team 15

Underperforming Technical Team Tools eBook Development Team Review 15

Harvard Business Review

JUNE 17, 2015

Consider the battle waged by IBM’s software development 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.

Software Review 15

Software Review Design Thinking Software Design 15

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

MARCH 11, 2013

Big, successful companies that manage huge projects like highways and dams and office parks have to deal with many more variables than a software development team. Granted, they have fancy project management software to help them stay on top of the schedule. Keep your team informed. It's funny, though.

Project 13

Project Management Underperforming Technical Team Software 13

Harvard Business Review

JUNE 27, 2016

In China, however, talking with customers was seen as in imposition on both the developers and the customers, who were considered uninterested and unreliable in articulating product requirements. Open office layouts were rather unusual in China and developers there were confounded by the expectation of being more collaborative.

Culture 14

Culture Collaboration Software Development Software Developers 14

Harvard Business Review

AUGUST 25, 2014

Peter Cappelli reviews the evidence to conclude that there are not major shortages of workers with basic reading and math skills or of workers with engineering and technical training; if anything, too many workers may be overeducated. We see it in the high pay that software developers in Silicon Valley receive for their specialized skills.

Technical Review 11

Technical Review Software Review Design Policies 11

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

Harvard Business Review

AUGUST 23, 2018

Nearly every business leader I meet fears being overcome by tech-savvy upstarts. In addition, this model improves the future work of innovation teams by helping them build an awareness of what downstream teams need most. In this model, multidisciplinary teams tackle challenges across the initiative’s life cycle.

Project 8

Project How To Innovation Design 8