12 Principles Behind The Agile Manifesto
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
This agile principle has three focus areas
- Releasing software early
- Delivering value continuously
- Satisfying the customer.
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
While this agile principle actually focus on process adaptability to change. But unfortunately it is often interpreted as people should adapt to change or complain the team is not agile.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
This agile principle gives a guideline related to how frequently the team should deliver working software, shorter development & release cycles delivers the best value to the customer
Business people and developers must work together daily throughout the project.
This agile principle guides how the business and development people work together. This way the collaboration increases and risk reduces.
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
This agile principle focus on how the collaboration should be in management culture & style. Focus on collaborative ecosystem
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
This agile principle highlights, face to face communication as the best way of communication.
Working software is the primary measure of progress.
First measure to measure progress is working software that is build, that’s the key message of this agile principle
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
This agile principle
Continuous attention to technical excellence and good design enhances agility.
This agile principle
Simplicity--the art of maximizing the amount of work not done--is essential.
This agile principle
The best architectures, requirements, and designs emerge from self-organizing teams.
This agile principle
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
This agile principle
*Reference : Agile Manifesto
Remaining Principles coming up soon…
Learn more from our certification & training programs
Naveen Nanjundappa, Certified Scrum Trainer
Well known for his unique teaching style, Mr. Naveen Nanjundappa has over 19 years of service in IT industry, with experience in most of the standard roles of software development life cycle such as developer, tester, leader, manager of projects and products. He was introduced to XP & Scrum in 2005. Following his passion for coaching, he has spent last 8 years coaching agile transformation, Scrum teams, trained over 4000+ people from various organizations. Expertise in Scrum, Leadership Agility, Organizational Agility, Process Agility, Team Agility, Product Management & Project Management.
CSM / CSPO certification by Naveen Nanjundappa is Transformational, with lot of examples from real life and Indian working culture. Participants will feel empowered, focused and knowledgeable to handle situations at work & most importantly you transformed not just certified!
- .
- 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.