Русские видео

Сейчас в тренде

Иностранные видео


Скачать с ютуб Kent McDonald of Inside Product: Diving into the Best Product Management Techniques в хорошем качестве

Kent McDonald of Inside Product: Diving into the Best Product Management Techniques 2 недели назад


Если кнопки скачивания не загрузились НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием, пожалуйста напишите в поддержку по адресу внизу страницы.
Спасибо за использование сервиса savevideohd.ru



Kent McDonald of Inside Product: Diving into the Best Product Management Techniques

Every software team is different and requires a tailored approach to thrive. It’s essential to discover what works for your specific team to achieve product perfection. This week, we have a rare go-to subject matter expert on our podcast to help you get there! Meet Kent McDonald. Kent is a seasoned freelance product manager and writer with a background as an agile coach. He has served as the past chair of the Agile Alliance Conference and is a Co-founder of the Agile Project Leadership Network. Kent is also a prolific author, having written numerous books and articles on agile methodologies, business analysis, strategy roadmaps, and product management. His extensive experience and insights make him a respected figure in the Agile community. In this episode of Scaling Tech, Kent and Arin dive into the best agile principles in software development, differences between product roles, and tips for improving productivity within a software team. And that’s just the tip of the iceberg! Join us today and get ready to make notes as we explore product management and best agile practices. Read Kent’s blog post about Moving from Business Analyst to Product Owner to Product Manager About Guest: Name: Kent McDonald What he does: He’s a Freelance Product Manager, Writer, and Former Agile Coach. Company: KBPMedia Where to find Kent: LinkedIn | Website | Newsletter Key Insights ⚡Agile methods should help reveal and address inefficiencies in workflows, not create them. It’s essential to allow teams enough time to focus on what truly matters in their organization and make a meaningful impact rather than just keeping them busy. Kent explains, “What happens is then, especially in organizations that are just getting started out, is that the folks that maybe look like they know what they're doing because they're actually moving along and progressing things, then other parts of the organization start asking, ‘So what are you doing and how are you doing it?’ And then they pass along this advice like, ‘Well, we've got this very long backlog that it works great because we always have something to do.’ Thethe point they're missing there is that chances are 50-60% of what they're doing is probably the wrong thing and isn't necessary. And they're emphasizing producing output and keeping busy over doing things that actually make a difference.” ⚡What’s the difference between a product owner, product manager, or business analyst? Although these roles seem similar—and are often confused—they each serve distinct purposes within an organization. Kent explains, “Product management is probably closely related to a job title that does the full set of figuring out what problem we’re trying to solve, how are we going to do that, working with both the market and the development team to make it happen. Product owner, as it was initially defined, was a role, specifically the product aspect of working with the development team. And then, in some cases, as I mentioned, product manager fills the product owner role. [...] And so that's kind of how I look at it. To roll the business analyst into it, as I mentioned before, they're the folks, the good ones are the ones that understand the business rules, processes, and data that an organization needs to operate.” ⚡ How to manage external stakeholders effectively? It’s vital to analyze stakeholders’ requests carefully and not take them at face value. Kent explains, “Oftentimes when you're getting stuff from stakeholders or users, they're phrasing the request in the form of a solution. ‘The system should do this. The system should have a red button that spins when you press it and whatever.’ But by having those feedback separate and actively doing some sort of analysis, as you're saying, does something actually apply, you're able to go through it and throw it against some filters to say, does this actually make sense or not. So, as part of that, you can handle your things from those stakeholders along those same lines. And you may weigh the feedback from certain stakeholders higher than others, depending on the subject matter of that request.”

Comments