
I’ve finally finished adding two submissions to the 2009 Agile Alliance conference. My first submission is my very popular “Prioritizing for Profit” talk on how a product manager should approach the prioritization of a backlog based on backlog items that drive profit and avoid ROI prioritization schemes. My second submission, Leveraging Collaborative Ideation and Decision Making Technologies, is a new talk about an emerging class of tools that help distributed Agile teams in collaborative ideation and prioritization activities.
Since the selected papers are based on what people submit, and since I care enough about Agile Product Management that I created the leading company on the subject, I thought I’d take a look at the submissions to the Agile Product Management stage that Enthiosys’ own Rich Mironov is producing.
What an incredible disappointment.
Instead of seeing submissions that address the full range of product management issues, I’m seeing submissions that clump into a few small categories, all of which can be summed up as “product management through the eyes of a product owner”. These are:
C’mon people—one more time—a real product manager does more than manage a backlog. A real product manager does a whole plethora of things (if you’re confused, visit our partner Pragmatic Marketing).
So, how about some submissions on:
My main point is that I’m very concerned that the Agile conference is still thinking about Product Management through from the vantage point of a product owner. That’s just wrong. I’ll try to make a few more submissions to compensate for this. In the meantime, if you read my blog, and you’re an AGILE PRODUCT MANAGER, please, submit, on something other than managing a backlog. (And, if you really do think that being an Agile Product Manager is primarily about managing your backlog… submit to another stage).
More at: www.enthiosys.com
Comments
Luke, you're right, and it seems like an illustration the centripetal force at work in product teams. It's always easier to talk about the issues closest to yourself, like the backlog. It always takes effort to learn about the outside world, like personas, segmentation, etc. You don't need another person with an opinion on the team. You need a PM to inform the team.
Just FYI, I'm working on a tool to help organizations define exactly what product managers should do, and identify if they need particular specializations. Product owner is conspicuously separate from product manager, even though they might both share the same interests. And I keep finding organizations, during my research, in which the product owner is a product manager...But that's someone wearing two hats.
Reply to this Comment