Un product owner es un actor clave en los proyectos de desarrollo según la metodología Agile. Suele ser la persona más comprometida con el resultado de un proyecto y la persona que dirige los equipos de desarrollo hacia la consecución de los objetivos clave. Los equipos que necesitan un product owner buscan a una persona que sepa crear una visión clara para el futuro de un producto, priorizar los objetivos y dirigir de forma satisfactoria al equipo con el fin de conseguirlos.
Estas son las tres preguntas de entrevista más comunes para el puesto de product owner y cómo responderlas:
Respuesta recomendada: Esta pregunta abierta está diseñada para averiguar si el product owner sabe quién es el público objetivo. Como product owner, tienes que saber reconocer quiénes son las partes externas interesadas y desarrollar el producto en función de esta información. Si bien cada una de las partes interesadas desempeña un papel fundamental en el proceso, también hay que interactuar con ellas y explicarles cómo contribuye cada una al éxito del producto.
Respuesta recomendada: Como parte de la entrevista, esta pregunta abierta permite evaluar tus habilidades interpersonales y de comunicación a la hora de trabajar con un equipo en el desarrollo de un producto. Como product owner, tu función es asegurar que el equipo esté informado acerca de cualquier cambio en el mercado y de la demanda. Tendrás que asegurarte de que todos los miembros del equipo entiendan la visión que hay detrás del producto. Explica de qué forma mantienes informado al equipo. Describe la información que consideras más importante compartir con tu equipo y por qué.
Respuesta recomendada: Esta pregunta abierta te brinda la oportunidad de mostrar tus conocimientos y experiencia con una variedad de marcos de descubrimiento de productos. Aquí puedes mostrar cómo determinas la aplicabilidad y eficacia de cada uno de los marcos y por qué los usas.
↳
Did you study for any of the Assessment Tests? Thank you.
↳
How long after the last interview did you wait for until they contacted you?
↳
I got an email within a week
↳
Any example? Was case study given in advance?
↳
Yes it was given in advance and was discussed during meeting with founder
↳
Yes it was given in advance and was discussed during meeting with founder
↳
Interesting question for a Product Owner, I would generally consider managing the team dynamics (including conflict) as a key part of the Scrum Master role. Menos
↳
In response to the inquiry above, the Product Owner and Scrum Master role at Renovate America are considered one role. It's obviously not ideal since these two roles are supposed to balance each other, but that is the current setup at the company. Quite a bit of responsibility for one role. The PO manages the backlog (feature prioritization) and runs all retrospectives as well. Menos
↳
Yes, she emailed me about the assessment
↳
How long did it take them to tell you you were not getting an offer?
↳
How much do you want to earn and by when ?
↳
Spread knowledge
↳
MVP has to be defined first. Assuming you have a list of stories that are all groomed and sized, you can combine that with your estimated velocity of your dev team. This velocity should be based on a historical average. If you have roughly 100 points worth of stories in your MVP and you do 10 points of velocity a sprint, you should be done in 10 sprints. You then multiply the cost of the development per sprint (# of engineers @ rate) by 10. That's the cost, but you should charge your margin on top of that. Also, there's always "found" work so you should add 50% schedule slack so it really should take 15 sprints. Underpromise and overdeliver. Menos
↳
MVP has to be defined first. Assuming you have a list of stories that are all groomed and sized, you can combine that with your estimated velocity of your dev team. This velocity should be based on a historical average. If you have roughly 100 points worth of stories in your MVP and you do 10 points of velocity a sprint, you should be done in 10 sprints. You then multiply the cost of the development per sprint (# of engineers @ rate) by 10. That's the cost, but you should charge your margin on top of that. Also, there's always "found" work so you should add 50% schedule slack so it really should take 15 sprints. Underpromise and overdeliver if you can. Menos
↳
With proof of my liquid capital.
↳
Found excellent read: bit.ly/faang100
↳
Thank you for your honest feedback. We feel it's important to thoroughly explain our business model with openness and transparency. Our websites have changed how people relate to and think of online entertainment market and we are the leader in premium adult content worldwide. Our award-winning brands have become a point of reference for the industry and we are very proud of the recognition we have gained. This would not be possible without the amazing talent we hire - anyone across our teams from marketing to technology - we ensure we hire the people who are passionate and comfortable with what we do. We feel by asking the right questions you get the right answers! Thank you! Menos
↳
It was unexpected as we are in 2018!!!! Why would somebody care for a tech job in adult industry? Menos
↳
I would ask them what exactly do they envision being able to do when this work is delivered. This is my way crafting acceptance criteria and success factors. I would ask why the current way is not working, why the change now? If the ask seemed like a ton of effort, I would ask if the team could produce part of this request, what would be the most critical piece in order for the digital format to be useful. I would just listen for the messages not said directly suchas, if they really know what they want and why. Menos
↳
Since the VPs want a digital version of their compliance documents, it is implied they have physical versions. I'd ask for a hard copy of the compliance document. Once I have a version in hand, I'd ask them what parts of the document tend to be the same doc-to-doc, and which parts change or require user input. Menos