Remove Software Review Remove Systems Review Remove Tips
article thumbnail

5 code review best practices

Atlassian

In 1988, Hewlett Packard (HP) conducted an internal review of their software development processes and set a target to improve their code quality tenfold. Eventually, they concluded that incorporating code reviews into the development cycle saved more money than resolving defects after they were found by customers.

article thumbnail

10 Scaling Tips for Product People

Roman Pichler

One company I worked with, for example, assigned developers who had worked on enterprise systems using an ancient programming language to develop a brand-new, embedded product with the latest technologies. This led to a bloated, over-complicated code base and a product that was difficult to adapt and expensive to maintain.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Five Ways to Track Customer Sentiment

Alchemer Mobile

Whether a customer completes a purchase, leaves a review, or mentions your company socially, there is always an emotional state connected to their action. For more tips on NPS+, check out our guide which dives into this much deeper. Most support systems come with the ability to tag and categorize customer conversations.

article thumbnail

Mechanism of change: Getting more from your incident reviews

Intercom, Inc.

You can’t build software without encountering incidents – from critical bugs to full-blown outages, dealing with incidents are an inevitable part of the process. As a result, you’ll find no shortage of articles telling you how to write a review – or as they’re commonly known, a post mortem – of your incident. Ask five key questions.

article thumbnail

Ask the Community: How Do You Shift From Functional Teams to Value-Driven Teams?

Product Talk

Instead, they hand off work from team to team—the back-end engineers design the data model and system architecture, the front-end engineers build the interface elements, the mobile engineers work toward feature parity, etc. Sam created a diagram to help demonstrate the benefits of organizing teams by value stream as opposed to code base.

article thumbnail

Sprint Review – Make it Much More Than a Demo…

Agile Velocity

In a previous post in our Scrum Assessment Series , we shared some ideas to help catalyze engaging sprint reviews. Here, we take a deeper dive into the topic of awesome Sprint Reviews. The Sprint Review, just like the Retrospective , is an important feedback loop in a Scrum team’s toolbox. Why is the Review so important?

article thumbnail

Tool tips: How our design team switched to Figma

Intercom, Inc.

The company had to pay for redundant software. Things can get really messy in a traditional file system. In my previous company, we even had to create and maintain a formalized system for our working directory. Figma, on the other hand, gives you a transparent and almost flat document system. Something had to change.