Remove Examples Remove Software Review Remove Weak Development Team
article thumbnail

Dealing with an Underperforming Development Team

Roman Pichler

What is Bad Performance? Before I discuss how you can help an underachieving team, let’s briefly explore what good performance looks like, assuming that an agile, Scrum-based process is used. Second, the team participates in continuous discovery and strategizing , and its members regularly help refine the product backlog.

article thumbnail

Leveraging Software Platforms

Roman Pichler

Be Clear on What a Software Platform Is. Different people have suggested different definitions for the term software platform. Let me briefly share mine: I view such a platform as a collection of software assets that are used by several products, as the following picture illustrates. Treat the Platform as a Product.

Insiders

Sign Up for our Newsletter

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

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.

article thumbnail

Everything You Need to Know about Product Portfolio Strategy

Roman Pichler

Figure 1: The Product Portfolio and Product Strategy Using Microsoft Office as an Example In Figure 1, the strategies of the individual products—Word, PowerPoint, and Excel—implement the Office strategy. Another example is YouTube, which is available in three variants—standard, premium, and kids.

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

5 code review best practices

Atlassian

Subscribe to Work Life Get stories about tech and teams in your inbox Subscribe. In 1988, Hewlett Packard (HP) conducted an internal review of their software development processes and set a target to improve their code quality tenfold. Create a code review checklist. Introduce code review metrics.

article thumbnail

10 Product Roadmapping Mistakes to Avoid

Roman Pichler

For example, I could ask myself why it would be helpful to measure calorie intake. If you say yes to every request, you are in danger of creating a Frankenstein product—a product that is a collection of unrelated features, offers a weak value proposition, and gives rise to a poor user experience.

Roadmap 337