Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
From http://agilemanifesto.org/](http://agilemanifesto.org/
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.
I honestly believe this goes beyond a simple MVP analysis. This is more than prioritization of key development, and leaving low-valued features aside for later thought. This is not saying "no" to the PO when he asks for something that isn′t viable or valuable during this current iteration. This IS consciously saying, "K.I.S.S!". (keep it simple stupid!) This IS, questioning at every possible moment, are we doing this the easiest way possible? Are we really using the simplest tech for the feature? Are we positive that the way we have done this implementation 99 times before now, is the right one for the 100th?
As the phrase says, "the art" needs to be refined. It is not a science. It is the ability to weigh reality, such as time, technical restraints, money, emotions.. and being able to constantly question and look for something new and easier to do. And yes, maybe it is insanity, but I think we DO need to ask the same question over and over, and EXPECT a different answer.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more ffective, then tunes and adjusts its behavior accordingly.
From http://agilemanifesto.org/principles.html](http://agilemanifesto.org/principles.html
