Product Management Process

Defining what MVP means and how to differentiate it from other terms typical for the product pipeline.

What is MVP (minimum viable product), proof of concept and prototype definition? In this video, Railsware Academy describes the whole product pipeline and its key terms - outlining the differences between minimum viable product (MVP) and minimum lovable (MLP), marketable (MMP), and awesome (MAP) products as more advanced MVP examples.

Managing the unpredictable overhead that contributes to the total cost of ownership.

In a product's life cycle, there are often those technical imminent changes needed to improve the quality of the product dubbed as Technical Debt. They result in a scattered and distorted view of the product, poor decision-making, and draining of the product's value. Sjoerd Nijland slams these complexities as the evil monster in product development that comes to haunt developers and the entire Scrum team if not well managed. Read on what is Technical Debt and some of the ways that can be leveraged to manage it through the article.

The product management process is 7 stages: idea management, specs, roadmapping, prioritization, delivery, analytics, and feedback.

The product management process is similar across workplaces but the names and details may vary. It’s a lengthy path, with stakeholder participation throughout and contributions from multiple departments. This piece defines the seven main stages of the product management process such as idea management, road mapping, prioritization, delivery, and more. We also learn that great ideas in product development do not necessarily mean they will develop into exceptional products.

How to structure product teams and feature developments inside one team: basic needs, long-term initiatives, and short-term bets.

Product management concepts and frameworks writer Andras Juhasz discusses the answer to the conundrum, of "how to structure product teams to operate efficiently" in this article. He explores a framework for designing product teams, how that’s similar to making investments, and how it can be translated to deciding on feature priorities by simply treating product teams as investments.

All high functioning teams must prioritize. Not once a month, not once a week — but rigorously, and ruthlessly.

Sharing the process used at Def Method to help clients avoid product failure and ensure that they build to succeed.