This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
The term product owner is commonly used to refer to six different product roles in my experience. A feature owner who manages a major capability with which end users interact like search and navigation on an online retailer’s website. But the ability to save the document is a feature, a part of the overall product.
If you do things that are purposeful, you’ll eventually be successful.” — Howard Schultz Several years ago, I found myself in a heated discussion about product roadmaps with a client. So as he leaned across the table and looked me in the eyes, he demanded, “Explain why I need a product roadmap.” Why not, indeed?
A streamlined releasemanagement process is imperative for mitigating deployment risks and accelerating software delivery. All too often, releases turn into stressful events, fraught with last-minute surprises that disrupt business processes. What is the ReleaseManagement Process Flow?
AI product management is a specialization in developing and managing products that use AI technology to build, shape and improve them. Apart from artificial intelligence itself, AI is often referred to as Deep Learning and Machine Learning (ML) technologies and Natural Language Processing (NLP). What do we mean by AI?
TL;DR In SaaS companies, a product owner is responsible for developing the product’s vision and navigating the product roadmap to maximize value. The product owner is also often referred to as the voice of the customer (VOC) on the Scrum team. Brighttalk offers webinars on various topics, including product management.
TL;DR In SaaS companies, a product owner is responsible for developing the product’s vision and navigating the product roadmap to maximize value. The product owner is also often referred to as the voice of the customer (VOC) on the Scrum team. A CSPO or equivalent certification is a strong plus.
TL;DR In SaaS companies, a product owner is responsible for developing the product’s vision and navigating the product roadmap to maximize value. The product owner is also often referred to as the voice of the customer (VOC) on the Scrum team. Product owner FAQs What is a product owner vs. product manager ? Agile, Scrum).
TL;DR In SaaS companies, a product owner is responsible for developing the product’s vision and navigating the product roadmap to maximize value. The product owner is also often referred to as the voice of the customer (VOC) on the Scrum team. The role also calls for tactical expertise.
TL;DR In SaaS companies, a product owner is responsible for developing the product’s vision and navigating the product roadmap to maximize value. The product owner is also often referred to as the voice of the customer (VOC) on the Scrum team. Brighttalk offers webinars on various topics, including product management.
While the terms “deploy” and “release” may seem similar, they represent different processes that play crucial roles in the software development lifecycle. Release, on the other hand, focuses on the strategic decision of when and to whom the software will be made available, aligning with business objectives and market readiness.
For software companies, a greenfield project refers to kicking off a new app from scratch. product launch / releasemanagement / product disruptor / idea management / incremental innovation. Note: When a team builds on existing infrastructure or upgrades an existing product, the industry calls this a brownfield project.
We organize all of the trending information in your field so you don't have to. Join 96,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content