I have been thinking about a blog post for awhile now... here it is................... Nothing. Fortunately Peter has been keeping the trough flowing. I have not been inspired by a single thing out there lately.

There were a couple posts recently that I think are worth some reaction.

John at ZIGZAG suggested that the problem with requirements is the problem. Read it here. For some bizarre reason you need to register for an article he posted for free on the Atlanta TechProduct Management Assn Yahoo Group. Read it for free here. This article seems like someone going left because everyone else is going right. Tyner Blain addressed it perfectly here. Writing GOOD problem statements is the single most difficult thing you, as a Product Manager, can do.

The other was, when Saeed somewhat presented a narrow view of Product Management and Agile. Read it here. If your development team is now producing product in a more rapid interative fashion this will most definitely impact the way you work. The development team needs access to a customer / market representative and this person, in SCRUM, is titled the Product Owner. He is correct in saying that it does not need to be the Product Manager, in fact I could see it being an Analyst of some sort. This Analyst/Owner will need to be available to (and a part of) the Agile team for clarification and validation. Imagine how sour the Product Manager will be when the Development team drops a feature because they were unable to get clarification in a timely manner. I believe the Product Manager will still need to funnel in problems and own the prioritization/ranking for the requirements/stories and does not need to be there every day. But someone has to.

Anyway, enough for now.