🤣 I laughed loud on "if you want to fail, you prioritize based on this animal" 😂😂
@DaerJohannes4 ай бұрын
The link in the description does not work anymore.
@DavidPereira884 ай бұрын
Hey, I updated my courses and you can find them here: www.d-pereira.com/courses
@cyberpunk.3864 ай бұрын
The issue with primarily going for the low hanging fruit in the matrix is that you're not chasing the bets enough. They equally deliver value, but are harder and also need to be prioritised. Some developments are hard and do deliver good value and therefore are equally worth chasing.
@DavidPereira884 ай бұрын
If the goal is to deliver value, benefiting from what drives that fast is often a wise choice. Yet, I do not recommend neglecting bets; instead, I recommend balancing, knowing that bets may fail to drive value and that the costs are high. Balance is the key.
@cyberpunk.3864 ай бұрын
@@DavidPereira88 Agree. There's also an element of short term vs. long term goals. Low hanging fruit usually deliver ROI in the short term, while the bets have longer ROIs.
@jscianna096 ай бұрын
Congratulations David! I can't wait to read your book!
@DavidPereira886 ай бұрын
I hope you enjoy it.
@jeevd00077 ай бұрын
Hearty congratulations David. Looking forward to reading your book.
@DavidPereira887 ай бұрын
Thanks a lot!
@sahils007in7 ай бұрын
Congratulations 🙌 . I have already or-ordered it earlier. Would receive online version by 27 May I guess.
@DavidPereira887 ай бұрын
Woop! Enjoy it!
@biplab437 ай бұрын
Congratulations 🎉 I will read it soon!
@DavidPereira887 ай бұрын
I hope you enjoy it! Let me know once you've read it.
@realjkahler8 ай бұрын
David, as CEO/PO, we struggle with when to bring the engineers into the conversation. I was told by a few PM's that you secure the high-level requirements/design(s) and business goals prior to inviting any developers to a meeting. Thoughts?
@realjkahler8 ай бұрын
Great video. As CEO, our company struggles with alignment of deliverables. I don't mind small wins, but we end up focusing on so many projects, like you said, we never (or at least feel like) we never get anything done.
@adegunloyerebecca26719 ай бұрын
@DavidPereira88 Are you available for a business chat regarding your Udemy course? On getting you more sales, Real and active student with 5 stars positive reviews I'll be looking forward to your response Thanks
@sahils007in9 ай бұрын
Thanks for such a great session. Very insightful !!
@DavidPereira889 ай бұрын
I'm glad you enjoyed it! Any particular takeaway?
@sahils007in9 ай бұрын
Take your bets incrementally and based on evidence invest more.
@DavidPereira889 ай бұрын
@@sahils007in That's a great one!
@baozarzakariyyah83519 ай бұрын
Thank you 😊
@DavidPereira889 ай бұрын
Welcome :)
@IgorBarros1710 ай бұрын
I really liked the way you explained your experience! thanks for the insights
@rodrigodepaula0010 ай бұрын
Você é brasileiro hahahaha
@DavidPereira8810 ай бұрын
Sim, qual o motivo da risada?
@nicorago8811 ай бұрын
Thank you David for your video! Please, I would like to understand the part where you say we must show the problem and not the solution in the refinement meeting. In our product team, we usually use the Refinement Meeting to explain to the team what needs to be built (previously we had a meeting between the Product Manager, Product Designer, and the Tech Lead to find out the best solution to the problem). But, what would it look like to have a refinement meeting with user problems and needs (opportunities) and how would be possible to put product backlog items in the sprint if we are just talking about problems in the refinement? There won't be time to better define the solution if we do so. Please, help me understand that.
@irajt566711 ай бұрын
This is a great channel. I wish i had found it before. Thank you David...so very insightful and helpful.
@dollaya8893 Жыл бұрын
This is helpful. Thank you so much
@trunggiang2573 Жыл бұрын
I have question: A user story doesn’t focus on the solution, so when will BA define detailed descriptions for the dev to implement?
@DavidPereira88 Жыл бұрын
Why would you need detailed solution descriptions? The way you asked the question implies the DEV implements the solution instead of uncovering how to solve a worth problem.
@trunggiang2573 Жыл бұрын
@@DavidPereira88 We are following the following abbreviated process: BA and UI/UX designers receive user issues, analyze competitors, conduct market research to provide requirements. Then, they brainstorm with the development team to gather additional input, ideas for solutions, and finalize the best approach. Afterward, the BA needs to complete detailed documentation, including business process descriptions and system design descriptions for the development team. Currently, our refinement sessions are struggling to clarify the solution, and new documentation is needed to facilitate them. Can you provide advice on where we might be going wrong
@DavidPereira88 Жыл бұрын
@@trunggiang2573 That's a classic way of working, which differs much from how I work. I don't see a short answer for that. I'd recommend reading my newsletter or attending to one of my upcoming cohorts. maven.com/david-pereira/product-discovery-done-right
@trunggiang2573 Жыл бұрын
@@DavidPereira88 I have enrolled in your courses on Udemy, and they have been very helpful. Thank you so much
@skipscheerer3671 Жыл бұрын
"Promosm" 🙌
@shansm-ew6ef Жыл бұрын
David, really loved how you explained refinement. Thank you!
@CliffAdams Жыл бұрын
Love this concept, but I can tell you from many recent experiences, this is NOT what hiring managers think Product Owners are. They DO think POs are backlog shepherds or BAs. The real question is how do we lead those horses to water, especially under economic duress?
@DavidPereira88 Жыл бұрын
Many hiring managers are ill-equipped to differentiate the real Product Owner from the wrong versions of it. It's hard to transform. But I always ask the question, do you want a team of achievers or doers? If your answer is the second, I'm not your guy because when someone tells me what they want, I won't do it because I will strive to understand what they need and lead teams to create value beyond features. It's a different game, and that's the one I play.
@ermanmanyasli Жыл бұрын
I guess your quadrant in min 6 is a bit incorrect. If stg is not easy to build & also doesn't promise that much impact, it is waste of time. hence, you need to replace reds and grey circles' positions in your quadrant imho.
@DavidPereira88 Жыл бұрын
Not really. Easiness of implementation means how quickly you can implement. The more to the right, the quicker. Meaning that the beginning is hard.
@mitchelroe78296 ай бұрын
@@DavidPereira88 I just watched this and came to comment the same thing as @erman… but then noticed you’re using “Easiness” instead of the more common “Difficulty” that we normally see on these graphs. If the X axis were difficulty, then you would need to swap red and grey… but should also have a swap between green and orange. With difficulty on the bottom you would get a reverse result of: High return, low effort=green High return, high effort=orange Low return, low effort=grey Low return, high effort=red
@TheTeamdom Жыл бұрын
That quote "using what we know to discover what we don't know" is by whom again please? I can't make out the name? Martin Dowman?
@DavidPereira88 Жыл бұрын
He's Dutch. Maarten Dalmjin, you can find him here: www.linkedin.com/in/maarten-dalmijn/
@pablosrn442 Жыл бұрын
good content! simple and efective.
@zzohib9063 Жыл бұрын
Just made it to sr developer, I want to apply to product owner positions. Can I make the switch cold turkey or is there a step first
@jscianna09 Жыл бұрын
Bjorn for president! XD It is so true! I see the same problem over and over again. Truth be told, Scrum or no Scrum, most companies choose a type of hybrid framework that simply doesn't work. And they have a management system that has disaster written all over it: Sales makes impossible promisses (about things they know nothing about - they are not developers-) then they tell the developers what to do (and of course this must be done yesteryear), the developers are like "what the f+++k are you talking about?!". Or worse still, companies allow stakeholders access to Jira! >_< every time time I see this I just want to slap someone in the face, with a chair!, are they insane?! you give a child a hammer, everything is a nail! they claim they want to be transparent, but this is just stupid! (talk about paving the road to hell with good intentions) ; stakeholders end up treating Jira as a feauture wishing well, hoping their ticket will work as a coin that will hit a developer on the head! I mean, for crying out loud! And then they wonder why developers keep leaving them...
@jscianna09 Жыл бұрын
Thank you David, you are great! I truly value your imput :)
@Pyrognats Жыл бұрын
Like the learning about reversible and irreversible decisions. Indeed it is hard to let go of trying to make the perfect decision.
@solovyev11 Жыл бұрын
Thank you, David. Could you please advise? If my product deals with some complex logic: puzzling algorithm or formula to calculate some chart or widget value. Should the team (Devs + QAs + PO) investigate the proper rules? Who should document the description, diagram, spreadsheet in acceptance criteria? I can hardly imagine developers spending time on science papers research. Thanks again
@aussietramp Жыл бұрын
underrated video.Thanks for sharing irmao.
@MSMdof Жыл бұрын
makes sense
@Kawoski2 жыл бұрын
Excelente vídeo cara, parabéns
@mirceamanolache82702 жыл бұрын
this video helped me a lot . thanks! 😃
@LeandroR992 жыл бұрын
4 months into a PM role. I am still 'taking the horse by the reins', and this video seems useful. Thanks!
@DavidPereira882 жыл бұрын
Happy to know that. You may enjoy the content from my website too, d-pereira.com
@therahul53042 жыл бұрын
Og
@ryswiesenbrg842 жыл бұрын
Issues I am running into is how to manage personss who are from Water Fall and are trying to move to Safe with a BA trained in DSDM
@youngloenoe2 жыл бұрын
Meetings are a result of management that does not have a way to prove their value. We have too many meetings nowadays.
@clintonjones4222 жыл бұрын
also love the fraggle reference though some listeners/viewers may have no idea what that is... it is like wombles!
@clintonjones4222 жыл бұрын
just smash that mosquito! Overengineering is like perfection, it is the enemy of good [enough]...
@DavidPereira882 жыл бұрын
Simplicity is generally the best weapon!
@2NormalHuman2 жыл бұрын
Interesting experience. Do you plan to retry the interview at booking?
@DavidPereira882 жыл бұрын
Not really. I moved on and I found another path for my career.
@areochou80442 жыл бұрын
Role play is a fantastic idea. Learned much, and I am looking forward to more :)
@areochou80442 жыл бұрын
Most of the time, the trap comes from the management above the team from my experience. And how to convince them is what confused me.
@DavidPereira882 жыл бұрын
@@areochou8044 results talk more than words, sometimes you got to do what's opposing top management requests but great outcome you help you earn their trust and start changing.
@areochou80442 жыл бұрын
,@@DavidPereira88 You got it. Trust is everything, I changed my jobs thrice in the last 3 years. Maybe it is a little bit affected by covid-19, as you know, many small businesses shut down during that hard time. Each employer has yet to give me enough time to prove myself. Maybe, other people like me want to hear your experience and stories about how you conquered the bosses. 😀Appreciate your replies, I will continue to do what I do. Thanks so much.
@vipinkuniyil60512 жыл бұрын
Thanks for sharing 👍
@DavidPereira882 жыл бұрын
Welcome
@janaffolter47582 жыл бұрын
Thx David, this is always good and valuable to hear from you. We feel less alone! And I like your PO mindset. Thx for sharing with us.
@DavidPereira882 жыл бұрын
I'm glad to know it resonates with you as well Jan.
@Savvynomad2252 жыл бұрын
Do you have any advice for being a product owner, doing agile, with internal architecture products? I'm finding that the end users for this dynamic are other agile scrum development teams themselves, so there's less involvement for the product owner, outside of maybe being an order taking backlog manager for the CIO. Any thoughts for this dynamic?
@DavidPereira882 жыл бұрын
That's a complex topic. I've been a PO for backend services already. We found our way by setting clear goals, one, we kill dependencies. Then we organized the backlog based on it. I strived to evaluate which dependencies would be worth removing first and then prioritized. The CTO tried to push for different things, but we could focus on the goal. In summary, start with the goal and gain support for it.
@Savvynomad2252 жыл бұрын
@@DavidPereira88 thanks David. This is great guidance.