New answers tagged

0

May I gently suggest that the question you are asking is what to do about a symptom, and that there is a more important question to be asked about the cause? To answer the question you are asking, I suggest creating a new workflow state, REJECTED, which is a resolved state. Put these tickets in that state. Exactly what to do about the associated branch will ...


0

Your PM seems to be acting a bit like a user who doesn't really know what he wants until he sees it in action. Then you can do all the sign-offs you want, but you may still end up with the response "this is not really what I had in mind". Such responses are probably a fact of life and you will have to find a way in which the PM can say "This ...


1

I doubt that there is a technical solution to this problem. The underlying issue is in the product management space. The fact that the product manager is specifying what to build, having the team go out and build it, and then deciding that the wrong thing was built is extremely wasteful and costly. Rather than trying to figure out what to do with these ...


3

I also believe that the most concerning part is: the PM has decided that whilst the AC has been met, the code should not reach production as it does not deliver a suitable enough value to our user. I see three possibilities here. The PM does not believe that the AC need to include providing value. The PM is not putting in enough effort to the AC to ...


1

I'm not a big fan of Feature Toggles (because they can become a maintenance and configuration nightmare if not properly managed), but this could be a solution for deploying the code, without making it available to users. When the Product Manager (PM) eventually decides a feature can be shown to users, you just toggle the feature and later remove the feature ...


Top 50 recent answers are included