Remove Document Remove Software Review Remove Weak Development Team
article thumbnail

How to Develop, Articulate, and Sell Product Strategy

The Product Guy

First, I did not know how to frame, develop and present product strategy in a systematic way, and second, as a startup, my company has not historically had a good track record of strategy being developed outside of senior management (read: founder). Two major obstacles stood in my way.

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.

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

8 Tips for Collaborating with Development Teams

Roman Pichler

Manage the Product, not the Team. Focus on your job as the product manager or product owner, and manage the product, not the team. Treat the Team as an Equal Partner. The team members are not your resources but the people who create your product. Assume that the team members want to do their best.

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 354
article thumbnail

Establishing a Good Product Relationship with a Remote Engineering Team

The Product Guy

We had just hired a new VP of Product who was radically (and rapidly) changing our product development process, and our engineers – based remotely, in Argentina – were struggling to keep up. “To Second, and more important, it shows the demotivation and binary thinking that can result from bad or nonexistent communication.