In Agile software development projects the team has all the means needed to control their work and to easily deliver metrics that give management above the project level a clear sense of progress and status.  They follow a disciplined approach that embeds quality control into their work.

There is a feature set that has been described and a very concrete set of accomplishments as the team completes the features.  Clearly someone has planned and decided on the feature set and the sequence among the features.

As the team assesses the work they apply a "burn rate" derived from work on past, similar projects - analogous or parametric estimating. As they burn through the feature set they can compare actual rates to expected to measure productivity and report accomplishments.

A Scrum Master or equivalent plays part of the PM role acting as communicator, making sure issues are addressed and buffering the team from interruptions and other drains on their productivity.

Additionally, most if not all Agile projects are embedded in projects and programs, for example, new product development, and business process improvement involving application software development.

These higher order projects are generally more complex than the typical Agile software development project and must be managed in a more traditional way, with a designated PM, while encouraging the Agile approach on those sub-projects where it is appropriate.

In the end whether Agile projects need a PM is not worth arguing.  All projects need project management. How it is applied can vary from situation to situation.

To be successful in Agile environments (and in fact to do well in most environments) PMs must first favor people over process and avoid a command and control approach, relying on and promoting a shared vision and collaboration, including healthy conflict and its resolution.  The objective is to cultivate and reinforce self-managing teams in which the team members, considered peers of the PM, make decisions and perform many project management roles.

The project management role includes a leadership component, which when done well leads to the team thinking that they did the work and the leadership themselves.

Don't forget to leave your comments below.