Remove Technical Review Remove Testing Remove Weak Development Team
article thumbnail

A Practical Prioritization Approach for Technical Debt

The Product Coalition

Assume you have new feature requests from business, but your technical team wants to fix the technical debts first, what do you do?”. Before we get to the approach, lets look at the two different types of Technical debts that may come your way. The ‘Deliberate Tech Debts’ Imagine a scenario?—?‘You Copyright?—?Dilbert.com

article thumbnail

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

Product Talk

When an organization shifts from delivery or feature teams to product teams , the first step is often a change to team structure. Delivery and feature teams are often structured by function—front-end teams, back-end teams, mobile teams, etc. These teams can rarely deliver value on their own.

Insiders

Sign Up for our Newsletter

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

article thumbnail

The ultimate marketing technology stack for 2019

Intercom, Inc.

Known as the Martech 5000 — nicknamed after the 5,000 companies that were competing in the global marketing technology space in 2017, it’s said to be the most frequently shared slide of all time. Marketing technology is now the largest portion of total marketing budget (29% on average according to Gartner ).

article thumbnail

The Top 20 Symptoms of a Weak Development Team

TechEmpower - Product Management

When speaking with founders and CEOs, we often hear concerns like this: My project manager is losing confidence in the development team. I think that poor communication and differing team cultures might be part of the problem, but how can I know for sure? This is where a technical review can be useful!)

article thumbnail

10 Product Roadmapping Mistakes to Avoid

Roman Pichler

As its name suggests, this roadmap focuses on product goals and outcomes, such as acquiring customers, increasing engagement, and future-proofing the product by removing technical debt. A good test to understand if a product goal describes an outcome is to ask the why question. Therefore, be careful not to mix up goals and features.

Roadmap 337
article thumbnail

Words matter: Removing exclusionary terminology from our codebase

Intercom, Inc.

As she tells it, “When I was fresh out of college, I was working at my first job in the tech industry. My team’s lead engineer stopped what he was doing and announced to the all-male room, ‘Looks like the token female engineer has arrived.’ Think about the impact that racism has already had in tech.

article thumbnail

Three Qualities of Great Product Roadmaps

Roman Pichler

As their name suggests, these roadmaps focus on product goals or outcomes such as acquiring customers , increasing engagement , and future-proofing the product by removing technical debt. This helps align the stakeholders and development teams, as I discuss below, and acquire a budget if required. Actionable.

Roadmap 290