Agile in a Flash: the principles behind the Agile Manifesto

Today, when I came across the book "Agile in a Flash", I had the impulse to read it at first glance. But a good book needs to be tasted slowly, and occasionally you will have different feelings when you turn it over. After reading some of it, I have the idea of translating it. On the one hand, I can slow down and study it carefully, on the other hand, I can share it with more people.

To meet the changing needs of customers to embrace change through early and continuous delivery, even if software business personnel and developers who can work frequently at the end of the project work together every day to communicate the main indicator of progress through face-to-face communication around inspired individual construction projects: working software always maintains a fixed pace and continues to demonstrate the excellence of technology simplification: maximize unfinished work, self-organization, self-reflection and adjust behavior.

The Agile Manifesto sounds "warm and vague", but you can find that its 12 principles (here reinterpreting the original text on http://agilemanifesto.org) provide a richer description of Agile.

First of all, Agile is the continuous and incremental delivery of high-quality software for customers whose needs are constantly changing due to market competition. Your job: make your customers satisfied.

If your team is highly motivated, you are likely to succeed. They must communicate and collaborate at least every day, which is easiest when everyone is in the same room and has face-to-face communication.

Teams must embrace technical excellence, which is an essential element of always maintaining a fixed delivery pace. Through self-organization, teams can deliver the best architecture, requirements, and design.

In order to maintain a consistent delivery pace, the team must adapt through reflection. An increasing mindset can maintain this rhythm: introduce functionality and complexity when you really need it, rather than prematurely to keep it as simple as possible.

Honey, always remember that this is about delivering high-quality software. Measure progress and success by your ability to deliver continuously.