Twelve Principles of the Agile Manifesto

We take a look at overall ideas from the twelve principles of the Agile Manifesto before moving on.  There are some challenging concepts mixed in among recommendations that are very common.  All of these can be applied in areas other than software development. Likewise, their efficacy is seen there as well. We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. The Twelve Principles When we look at these observations and recommendations, there are themes that appear.  We also can see how software projects relate to projects in other areas or lines of business.  There are foundational concepts of a good team, working together, buy-in, and communication.  Some of the concerns addressed are rarely encountered.  However, many of the challenges to overcome still exist in many teams today. Row In The Same Direction Rowing a boat and tug-of-war are often used as allegories for teamwork.  While I would prefer to avoid them, they are just too easy to understand.  That being said, most of the twelve principles address the idea of everyone rowing in the same direction.  We want a team that is cohesive, communicates and is driven.  Motivation or a good work ethic is essential in the success of a project.  Therefore, a group of motivated individuals is more likely to succeed. Define The Team There are times that an "us vs. them" attitude can arise in a project.  This attitude is not helpful.  It will often be a drag on a project and may doom the whole thing to fail.  That is why these twelve principles return several times to defining the team and helping it work better together.  Communication is a concept we often see in project success.  Thus, the Agile Manifesto does not ignore it.  Instead of eschewing documentation, this approach embraces the most effective methods of communication. The Twelve Principles and Overall Manifesto

There are no comments yet.

Please log in to write the first comment.