Sellers - Added the questions... with no real attempt to edit the questions. I will collect more questions and maybe some answers :) as the panelists contribute. Perhaps we should have a blog where someone answers a question each day. Also, I suggest that we try and keep the answers relatively short (1-2 para) with links to more detailed information in the knowledge base. This lets someone quickly scan the FAQ, and can use the knowledge base for more detailed information.

Some of these questions seem to have implicit context (or term definitions) that I believe it would be better to be explicit about, e.g., "better, different, worse" than what; defining "hacking." Others seem to assume agile performs a task/behavior that it normally does not, e.g., build a WBS. And others ask incredibly broad questions with specifics that may require different answers for each, e.g., documentation based on SOX, ITIL, or, not mentioned, CMMI, ISO 9001, etc.

Interesting, no questions here about customer satisfaction, feedback, ensuring value delivery, etc. which are important ideas in an agile approach.

From my experience most professionals asking candid questions about Agile are not interested in the value for the organization/customer, but want to know what it will change in their practices, daily work... how it is different. Anyway, the first question is about "what is better/different with Agile". The answer should cover the benefits.

1) To respond to a couple of the comments above. First, as PMs, please add your FAQ about what you consider relevant to a PM. E.g., Why is Agile better for the organization. You can add them as comments or let them sub team lead. Second, please volunteer to answer/clarify the questions. Rodney Bodamer is the sub-team lead and can get you editing privileges for the page.

2) I have taken a first cut and answering the first question above
I have been a PMP for x years and not had special problems delivering IT projects. Why should I care about Agile? What's in it for me?
The discipline of project management and good project managers are evolving over the years as new practices and techniques are developed. Recently, there has been a lot of success - reported and actual - for projects and companies using Agile based techniques for software development and general project management. There are several reasons why a project manager should have at least a firm understanding of Agile. First, it is likely that a project manager is going to be in a situation where he or she will have either a project sponsor and or development teams arguing for or already using Agile techniques and will need to have a general understanding of the agile approach in terms of benefits and limitations. Second, Agile represents an area of potential growth for a project manager, there are a lot of new and interesting values, practices and techniques that can spur a project manager to improve. Third, Agile represents a significantly different perspective on project management. Understanding this perspective can deepen your understanding of a lot of the principles and practices of project management.

I really like this growing body of questions! It seems like this may be a very relevant model to build out our content. I personally like the idea of trying to answer a question or two a week. I'm curious though, how are people going about collecting these questions right now?

Brian, the first round of questions actually came from submission to an Agile Panel that I organized for the Atlanta PMI Chapter. As you can some of the questions are rather 'raw'. I hoping that over time, other folks will contribute - questions, answers and comments.

Muchof the lexicon used in Agile has an equivalent meaning in the PMBOK. Will we need to change the PMBOK to reflect the NEW Agile Lexicon?