3 ms·

Changing the design on a daily basis doesn't seem like a winning strategy - the engineer will never be able to complete anything since they're chasing a moving

Changing the design on a daily basis doesn't seem like a winning strategy - the engineer will never be able to complete anything since they're chasing a moving target, and so you'll never get an MVP that you can actually give to customers and get feedback on. I don't think you necessarily need to fire your PM, but sit down with him and ask him to slow down. New ideas are great, but if he thinks about them for a while before suggesting them to the engineer, it will weed out some of the bad ideas before they get implemented. (Maybe the PM should switch to decaf coffee or get more sleep?) If this continues, your engineer will burn out and/or quit.

cimmanom 8y ago
This. I’m not usually a fan of scrum, but this is one of the problems it can help solve. You can decide to zig or zag every couple weeks at the end of a sprint, but for those couple weeks you’ll hold steady in one direction so that you can make reliable progress (and force the people making changes to sleep on them and bundle them up.) Frankly, though, your PM sounds ineffective - especially in a kanban system. Part of their job is making sure there’s a shippable MVP SOON that you can THEN iterate on IF improving it at that point will have more business impact than building the next feature will. And they’re clearly undermining that effort.