Agile Practices on Agile Principles or vice versa

My advice is to focus less on projects and more on products, and less on principles and more on the values which underpin the Scrum framework.

I've probably used the phrase, but I'm not that convinced of the existence of "Agile practices".

Agile is a set of values (things like "individuals and interactions over processes and tools" and "responding to change over following a plan") and principles (things like "our highest priority is to satisfy the customer through early and continuous delivery of valuable software").

On top of these values and principles are some practices that have been used to support them. Coming from a software background, some good examples are the use of continuous integration and automated testing. However, these practices aren't "Agile practices". I've used these practices with great benefit in environments that are the exact opposite of the Agile values and principles - formally defined and documented processes, big requirements and design documents (often front-loaded), contracts, and management per plan.

As far as the success of the Agile values and principles goes, it depends a lot on your context. Are you operating in an uncertain or frequently changing environment? If so, embracing the principles and practices that support them may be beneficial. If your environment is relatively static, then perhaps the things that you do to respond to changes will only add overhead. There's no one-size-fits-all solution.

Thank you Ian and Thomas for your thought. 

As Thomas explained about the existence of "agile practice", how if we just simply change the term of "agile practice" with "agile Methods" such as Scrum, FDD, DSDM, or any other agile methods, as I know each agile methods consist of some different practice. What do you think about the correlation between agile methods and agile principles (agile manifesto) on project success?