Your response about one of the biggest challenges that an organization faces in adopting an approach is social and cultural concerns, brought that experience back to mind. I know that the Anthropology of Product Management CoP, (#AoPM in Twitter) is focused on discussing ideas of how to address this challenge as a product manager. They are also in LinkedIn.

You often hear that active participation from stakeholders in a project is key to that project’s success. During a Twitter meeting using the hashtag #innochat, we talked about innovation as being the value that you bring to the stakeholders. If your stakeholders are not involved you will not understand their needs, not understand their objectives, not capture their input, not bring them value, and not innovate.

Agile- Meeting stakeholders/customers immediate needs with an evolving product. An agile product development team can have some of the most volatile requirements/releases because of that principle. Agile houses have to understand the importance of version control, traceability, and suspect links. Requirements Management principles that if ignored will kill a shops ability to hit deadlines and cost expectations on iterations and releases.

Lastly during a PMI meeting this week in Austin we talked about feedback and review during/after a project. Don’t wait until it is too late to do anything about the situation to collect comments and feedback. Collect comments on everything, everywhere, that way you have them when your ready to act.