11

PO1: Hey, PO2 just told me that he experiences a lot of crashes in our iOS app!

Me: Whoa! The app hasn’t had any crashes since ages. The testers haven’t reported crashes either. (Me in panic mode). I will ask PO2 about some details about the crashes.

Me to PO2: So, can you please describe me when the crash happens?

PO2: (long story about error messages and UI quirks and how he force quits the app to make them disappear)

Me: OK thanks for that info. Those are definitely valid problems that we have not encountered yet. But none of them are crashes. So are there any other problems that cause crashes?

PO2: Yes and no. (Long story and more problems)

Me: ok we need to investigate that. But are there crashes?

PO2: (Something that doesn’t answer the question)

Me: I need to ask explicitly again: Are there actual crashes where the app closes itself automatically?

PO2: No, that has never happened.

Comments
  • 2
    Are you really assuming IO to be free of errors?

    PO1 probably just misunderstood something PO2 said.
  • 4
    @Oktokolo I guess PO2 just used the word "crashing" for "something wrong happening" in the app. Analogous to a bug.
    Until I specified what I mean by "crashing".
  • 3
    @Lensflare Chances are, PO2 heared the term "crash" for the first time when you mentioned it 😇
  • 1
    @Oktokolo No, I’m not assuming that IO is free of errors. Why would I? I don’t get you mean with that question.
  • 3
    It's the typical tantrum...

    People get emotional and suddenly a bug / glitch / workflow issue is "OMG, it's crashing / dying / destroying data / ..."

    Would be so much faster to get the info rationally then to have to unravel the tale for the grain of sand of truth.
  • 2
    @Lensflare Just wanted to hint at human communication being pretty darn faulty. PO2 could have said anything to PO1. Messages you get after they have been passed through another human's brain are often altered beyond recognizability.
Add Comment