Remove How To Remove Software Review Remove Weak Development Team
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

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? But how do you know which? It’s a good question.

Insiders

Sign Up for our Newsletter

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

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

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

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

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

Succeeding with Product Delivery and Scrum: 10 Tips for Product People

Roman Pichler

Listen to the audio version of this article: [link] 1 Complement Scrum with a Product Discovery and Strategy Process Scrum is a simple framework that helps teams develop successful products. Continue the discovery and strategy work while the product is being developed. But don’t stop there.