The Agile Manifesto is a statement of the principles that underpin agile software development. The Manifesto was derived by representatives of various new methodologies such as Scrum and extreme programming where they saw the need for lightweight methodologies to replace the traditionally used heavy weight ones.
The 12 principles of the Agile Manifesto are:
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer’s competitive advantage.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business people and developers must work
together daily throughout the project.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Continuous attention to technical excellence
and good design enhances agility.
Simplicity–the art of maximizing the amount
of work not done–is essential.
The best architectures, requirements, and designs
emerge from self-organizing teams.
At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.
I can relate to most of these manifesto rules by relating them to the way that we work today. We strive to keep the customer happy and we work together as a team to achieve this. We also look to release working software within a 2 week cycle which is also a marker for our progress. If you compare these to the way that you work using Scrum, you will see that you are following the agile manifesto.