4 ms·
Former PM/PO and my best experiences were when the engineers had final authority on how it works, but I had final say on what it does
by passwordoops 2y ago
Former PM/PO and my best experiences were when the engineers had final authority on how it works, but I had final say on what it does
- figassis 2y agoI don't think it would make sense any other way. When doing rituals like refinement and sprint planning, POs want features but have no idea how they interact with what's already there, or how integrations are implemented, or how things are optimized. Simple features might be very complex to change for example, often because product itself asked to make something that does not scale for the sake of velocity, and now wants to build on top of that. There should be a conversation, engineers should inform POs about risks, alternatives, workarounds, etc. Sometimes POs are just not aware that there is a much better way to do X.
- piva00 2y agoSWE here with experience on product development through a few startups earlier in my life, working on larger orgs later. I wouldn't choose any other way. As a SWE I can have my opinions about the product, I can build a business case for what I see might be gaps in the offering and try to sell it but I'd still very much need the PO/PM to take the job of fleshing that out to users'/product's needs and defining the "what" better than I can. A well-oiled product team is invaluable, there's very few things I hate more in this career than working with an incompetent product manager, everyone else's lives become extremely difficult if a PM is not doing a good job.
- deleted 2y ago[deleted]