Timeline for How would company management work as a set of products?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2018 at 12:18 | vote | accept | I.M. | ||
| Jan 29, 2018 at 18:09 | comment | added | Daniel | This is a very broad discussion and different people look at it different ways. Mike Cohn's article definitely has a more open view of what a product is, but also warns against sub-optimizing as you break down products. So, if a website is considered its own product, how does it measure value added to the market? Same with the management tasks. And note that he still looks at these products in the context of the broader product. | |
| Jan 29, 2018 at 11:34 | comment | added | Bart van Ingen Schenau | On a company level, I would say that a product is something that brings revenue for the company and if it doesn't, then that product should be discontinued. | |
| Jan 29, 2018 at 10:22 | comment | added | I.M. | Also, when I tried to argue that the supporting product could not be its own product, we ran into a debate over this article. If spellchecker in a text editor is a product, then why not travel booking? If the website of an airline is a product, then why not our presentation webpage? There must be a core issue that we are missing, I wish I knew how to define it... | |
| Jan 29, 2018 at 10:08 | comment | added | I.M. | Thanks! This is actually quite close to my own understanding (I'm the PO on one of the 'usual,' dev products). One problem with answering the question you suggest may be that M&M have their own priorities (company priorities, if you will). They don't 'support' dev products, they 'bring as much business value as the devs'. So their priorities can't be set by the dev POs, unless we are talking about a significant power battle. | |
| Jan 28, 2018 at 17:50 | history | answered | Daniel | CC BY-SA 3.0 |