article thumbnail

Two Development Team Configurations I Lobby Against

Mironov Consulting

Product management doesn’t run Engineering; Engineering runs Engineering. And at least in public, Engineering and Product leadership need to be shoulder-to-shoulder , actively supporting each other at every turn.   Not everything that’s reported as a bug is a bug – or should be fixed.  Customers

article thumbnail

I’ve abandoned “MVP”

Mironov Consulting

Filed under “whiny excuses from product management for missing delivery dates.” So IMHO, calling something an MVP invites chaos. Stakeholders keep expanding the definition of ‘done’, since we can’t ship a real revenue product without features A, B, C, X, Y and Z. Subtle distinctions are lost.

Insiders

Sign Up for our Newsletter

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

article thumbnail

How to Decrease Beta Testing Costs by 40%

Centercode

When you’re managing beta and delta testing, you’re tasked with providing accurate, useful insights to several different stakeholders — reporting and prioritizing issues for Engineering and QA, feature acceptance for Product Management, contextualizing insights for UX, even testimonials for Marketing.

article thumbnail

GDPR: Who Should be Your Data Protection Officer?

Mind the Product

A DPO must be allowed to operate independently and report to the board. For example, if the DPO finds that the VP of marketing needs to remove data from their machine they should be able ask them to do this – and if they don’t, be able to report them to the board without fear of reprisal.

article thumbnail

Designing an Organization for a Product Approach, Part 2

Johanna Rothman

Again, I am not saying this is the only way a product organization would look, but this is a possibility. The senior manager has P&L (Profit and Loss) responsibility for the entire product line, including Product Management (for this product line), Customer Support, Training, etc.

article thumbnail

Why Your Entire Company Should Talk with Customers Weekly

Amplitude

Product team engaged with customers based on quantitative data around feature usage patterns to uncover why some users retained better . Led to the new reporting features and multiple product fixes inspired by insights. Engineers, product managers and designers got to see their product used.