How do you prevent rogue engineers from slipping in features that are good but not prioritized?

This usually signals a trust or communication gap rather than a purely logistical issue. Engineering teams sometimes struggle to be heard and may feel that maintenance wo...

This question made me smile. “Rogue engineers” is quite a term :) .First, I believe anyone, regardless of craft, should feel empowered to suggest ideas, challenge assumpt...

The first question I would ask is whether PM and engineering have aligned upfront on a mutually agreed-upon definition of the problem to be solved and the definition of ...

There is no such thing as "rogue engineer" everyone comes to job to best of their abilities however I understand the nuanced question. here is my take Bunch of tools ...

Product managers should partner closely with engineers on building a product roadmap so that everyone is bought into the roadmap and avoids the need for slipping in rogue...

To answer this question, I’m going to put my PM hat on. Why is the engineer “rogue”? What is driving them to want to “slip in this feature”? First, I’d talk to them, u...

This is a classic conundrum. The good news is it’s a lot less costly when it happens in today’s agile world than it was when I started my PM career in the days of 18 mont...

Name and shame them! (kidding)Look, these things may happen and sometimes they can be amazing, sometimes they're a waste. Ask youself why this happens? Do they see a need...

I try to prevent it from becoming a problem in the first place. Most of the time, when engineers build something unplanned, it’s because they see a real opportunity to im...

That is an intriguing scenario. While it's generally rare in well-governed teams—as a connected PM, you should be deeply integrated with both your team and customers the ...