Agile, social media, and requirements

Speaking of social media, one of the two research documents now in the editing queue looks at using social media as a source of product requirements. Using Forrester's POST* methodology as a starting point, how can product managers harness the enormous amount of potentially useful information transmitted in the clear through blogs, forums, Wikis, and similar technologies?

The other document in editing is the "Agile company" piece, covering the results of the survey and interviews we conducted to understand how Agile development changes technology companies. To foreshadow the results, I had to divide Agile adoption into two stages. To date, Agile aficianados have focused on the first, Agile within the development team. Clearly, for the story of Agile adoption, that's only Chapter One.

* In this approach, the steps for analyzing social media involve people, objectives, strategy, and technology (POST).

[Cross-posted at The Forrester product management blog.]

Comments

[Malak]

Hi Jimmy,I distinguish beeewtn defects, field issues, and defects that should be User Stories (new features). I could have been more clear. Known defects that are not fixed in-Sprint and then added to a defect tracking database for later fixing when we have time is what I was referring to. I also had waterfall on the brain when I thought about # 9.

[wow gold]

So trend and great.I would suggest buying them as properly. I bought my 1st wow gold about 7 years ago and i could have def used the care kit then.