We announced today that we have outstanding customers who continue to support us...

What are the RIGHT requirements? It used to be you planned a release and listed the must-haves and got them... Eventually

But with agile we get the product backlog faster... Yeah? i.e are those the Right requirements?

Who owns the definition of the right requirements?

The Product Management blogosphere has been atwitter, and a-Twitter, with the question of the best metaphor for the role of product management. Is a PM the captain of a product as Christopher Cummings suggests? Or, going back to the old tropes, should we think of them as mini-CEOs of their products (one is always tempted to believe the Cranky Product Manager, isn’t one)? Or are they cat herders – and does that explain anything? In any case, Saeed wants to make sure we don’t undermine ourselves with unsavory metaphors like “glue” and “grease.”

Q1: What are the top three Requirements/Features in your next product release?

Q2: How do the top three help address your long-term product strategy?

Q3: If you had been planning this release six months ago or six months from now, would the top three still be the same?

Each requirement has a web of relationships with customers, stakeholders, market elements, risks, and competitors

In my last post I talked about the fact that agile methodologies are all about "doing the most important thing first." This post is about figuring which is the "most important thing."

For those of you who attended the Tom Grant webinar recently, thank you, your participation made it a success. As is usually the case, we received more questions than Tom was able to respond to during the duration of the webinar.

However, Tom has very graciously responded to your unanswered questions.

Last week we hosted a webinar with Tom Grant of Forrester who spoke about how the merging of the right ingredients can produce winning results. One of my favorite Tom quotes from the webinar was:

Innovation is both an art and a science. Social media help with both.

Forget about agile methodologies and the agile manifesto. The key idea of agile is "do the most important thing first."