PLEASE NOTE: We'd prefer you send your answers to workwithus@rrsoft.co rather than post them publicly in another Gist, or in comments on this Gist ;-)
The following is a series of questions related to skills that we value in Product Owners
This is not a timed or monitored test, and you may use any print or online resources you would like to assist you when answering.
Please submit your answers in the form of text, markdown, or other lightweight data formats. Please indicate clearly which parts of your response correspond to which question. If your answers span multiple files, please attach them as a zip file.
Do you think Scrum adequately addresses the product discovery process? How do you learn about new ideas and requirements, and include user research in the product discovery process?
A new feature is overdue and has been drastically underestimated because of unexpected technical debt. Nevertheless, your most important stakeholder insists on "finishing it" because so much effort has already been invested. How do you deal with this?
How would you estimate the costs and benefits of epics, tasks, or features in the product backlog to allow for prioritization?
You'd like an important user story to be selected for the next sprint. Unfortunately, the final user interface designs are missing - but the designers promise to deliver no more than two days into the sprint. Despite this, the Scrum Master rejects the story because the Definition of Ready has not been met. What can you do?