3 ms·

>In any case, PM acting as QA is not a healthy state. Hard disagree. The PM shouldn't be finding a lot of bugs, when theyre not doing QA then a lot of specifi

• whstl 3y ago
  Yeah, agree with you. It's also not exactly "QA" in this case, it's more close to just validating things every once in a while... Especially if the specifications aren't clear and "atomic" enough, a lot of implementation mistakes will slip in. If a product manager is the one creating those specifications, they're the main ones who should be going around the product verifying if they're correct or if they actually "work" in practice. Developers and QAs can do it too as part of their job, sure, but it won't be as effective unless specs are ultra-clear, which they often aren't.
  • sf4lifer 3y ago
    If your PM doesn't use your product enough to know every single bug then they don't understand or feel your customer/user pain. Ideally when they experience a bug there is already a ticket created that they can simply prioritize. I have a deal with my QA team: On every new build once they've gone through it, they pay me $10 per bug with no ticket. If I don't find any undocumented bugs then I buy lunch.
    • whstl 3y ago
      Exactly, if there’s one person that has to dogfood, it’s the PMs.