4 ms·
On the contrary in the Kanban process, PM is the pivotal role. They control the que, the cadence of feature releases, etc ... Without an effective PM, the whole
by bhattisatish 13y ago
On the contrary in the Kanban process, PM is the pivotal role. They control the que, the cadence of feature releases, etc ...
Without an effective PM, the whole thing will fall as a pack of cards.
- bdehaaff 13y agoTrue. But PM needs to pick its head up and think more broadly. A "one in one out" queue is contrary to delivering winning product.
- bhattisatish 13y agoAs I have said below (https://news.ycombinator.com/item?id=6119175 https://news.ycombinator.com/item?id=6119175) You need to delink engineering releases from marketing releases. Where is it written that when the engineering releases a feature you need to make a marketing push? When you have a collection of features ready which as a whole makes sense for marketing, then you make a marketing release with all the related PR, hype cycle, etc ...
- bdehaaff 13y agoI think that we would actually agree. I don't really care how Eng gets to a major milestone and delivers a good portion of the required features. The issue is that when the teams lose focus of the bigger picture and stop thinking about key dates and what collection of features are needed to win. When any dev methodology becomes the goal and not the means to an end -- companies and their customers suffer.
- deleted 13y ago[deleted]