First day back from holiday: after 30 minutes of work (excludes start-up, catch-up etc.) The P.O. (product owner) comes to me

Telling me I needed to switch project, ok I thought at least they switched the project from what ever it was to a propper OTAP street while I was away

Few tickets later the P.O. asked me if tickets x could be deployed to our test servers as well as production.. (note the ticket was already merged with our develop branch and he wanted only that single ticket x to be deployed)

WTF is the point of a OTAP street if you're going to deploy it to every server type at once?

So day one after my holiday I already needed to fight the P.O. again

At least I wasn't disturbed during my vacation... Witch is a first.

  • 4
    Isnt there a scrum master with a bat to kerp the PO at bay?

    Or are you the scrum master?
  • 2
    @alexbrooklyn nope, we don't have scrum masters
  • 0
    @incognito what is OTAP?
  • 1
  • 1
    @JoshBent @mt3o lol, my bad didn't stop to think OTAP is Dutch..

    But the second link of @JoshBent explains it exactly:


    1. The program or component is developed on a Development system.
    2. Once the developer thinks it is ready, the product is copied to a Test environment
    3. If the test is successful, the product is copied to an Acceptance test environment
    4. If the customer accepts the product, it is deployed to a Production environment
  • 1
    @incognito gotta just love that there's a short letter description for the most mundane of things always.
  • 1
  • 0
    Ok, usually, when using scrum, and the role of PO comes from scrum framework, you should have scrum master in your team and he should be doing this talk with the PO, not you, the dev.
    Also, this kind of status report should be easy to read from your scrum board (I'm assuming you use scrum not kanban not waterfall) and you should have daily meetings to discuss progress and blockers during those meetings.
Add Comment