Remove Groups 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

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

Everything You Need to Know about Product Portfolio Strategy

Roman Pichler

A product portfolio strategy is a high-level plan that helps you maximise the value a group of products creates. Their visions, target groups, needs, standout features , and business goals must comply with the overall portfolio strategy. [1] A product portfolio is a group of products.

article thumbnail

Five Product Owner Myths Busted

Roman Pichler

” But do not allow people to dominate and tell you what to do, and don’t agree to a weak compromise. The SAFe product owner is tactical in nature and focuses on working on the product backlog and guiding the development teams. Myth #3: The product owner is responsible for the team performance.

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

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. You should therefore review and adapt the roadmap on a regular basis. 7 The Roadmap is Speculative.

Roadmap 337
article thumbnail

Two Development Team Configurations I Lobby Against

Mironov Consulting

But there are some engineering team configurations that I see as problematic.  So 1] Dedicated Bug Fixing Teams Sometimes there’s a push to create development teams specifically to close out bugs and defects, especially after frequent outages or to address long-term system neglect.  This