Agile Project Management with Scrum

I have been wondering lately, what does agile really mean here?
This article says, Agile means responding to change - both technological change and changes in requirements perhaps due to customer demand and market opportunities.

It makes sense to me that this would be needed. The world is spinning much faster now and people expect content on the web, for example, to be relevant.

How does this differ from typical PM approaches? It has an answer there too...
-----
More traditional project management "command and control" approaches assume the relationship between the inputs and outputs of a software development process are stable and predictable and that the schedule of outputs will still be relevant by the time they appear. Scrum accepts the fact that things are going to change and takes an empirical approach.

In Scrum work is delivered in monthly "sprints". Each sprint delivers a single, usable piece of work called the "product increment". This product increment is immediately available for evaluation and use by the customer at the end of a sprint. Projects managed in a "command and control" style often have an infrequent release schedule. This can result in a gulf between customer expectations and reality. Scrum requires these predictable, frequent releases to ground customer expectations on demonstrated, working code rather than the false comfort of forecasts and reports. Short of an emergency, stakeholders aren't allowed to approach developers formally or informally with requests to do additional work during a sprint. This gives the development team enough stability to be able to complete a product increment without being distracted by the noise of external disruptions.
-----
Now that last part about not having stakeholders formally talk to developers is something that I try to enforce on my projects also. So, maybe it's not so different after all...to learn more visit:
ITWALES.COM - Agile Project Management with Scrum: