О целях Agile. Решение какой проблемы на него возлагали и что легло в основу его манифеста:
💬 "During the Snowbird meeting, Kent Beck said that the goal of Agile was to heal the divide between business and development. To that end, the following "bill of rights" was developed by Kent, Ward Cunningham, and Ron Jeffries, among others."
—"Clean Agile: Back to Basics" by Robert C. Martin
Kent Beck выяснил, что напряжение являлось ни чем иным, как упреждающими защитным механизмом, спровоцированным страхами обоих сторон процесса разработки.
Идея Bill of Rights возникла на основе идеи Declaration of Independence (перевод):
💬 "Software development is risky. People involved have many fears of what may go wrong.
To develop effectively we must acknowledge these fears. Why do we need a software process? For the same reason that we need laws, governments, and taxes: fear.
The Declaration of Independence says:
That among these [rights] are life, liberty, and the pursuit of happiness. That to secure these rights, governments are instituted among men, deriving their just powers from the consent of the governed.
Though the profundity of these words may distract us, consider the word secure. We institute governments because we are afraid of losing our rights. By the same token, we institute software processes because we are afraid.
Customers are afraid that
- They won't get what they asked for.
- They'll ask for the wrong thing.
- They'll pay too much for too little.
- They must surrender control of their career to techies who don't care.
- They won't ever see a meaningful plan.
- The plans they do see will be fairy tales.
- They won't know what's going on.
- They'll be held to their first decisions and won't be able to react to changes in the business.
- No one will tell them the truth.
Developers are afraid, too. They fear that
- They will be told to do more than they know how to do.
- They will be told to do things that don't make sense.
- They are too stupid.
- They are falling behind technically.
- They will be given responsibility without authority.
- They won't be given clear definitions of what needs to be done.
- They'll have to sacrifice quality for deadlines.
- They'll have to solve hard problems without help.
- They won't have enough time to succeed."
—"Planning Extreme Programming" by Kent Beck, Martin Fowler
💬 "But it was here, nestled in the white-capped mountains at a ski resort, that a group of software rebels gathered in 2001 to frame and sign one of the most important documents in its industry's history, a sort of Declaration of Independence for the coding set."
—"The Winter Getaway That Turned the Software World Upside Down" by Caroline Mimbs Nyce
Post #288
2.25K
Russian Association of Software Architects Первый час разбирались с тем, какими признаками обладает Agile разработка. Обсудили такие признаки: 1. Responding to change over following a plan 2. Individuals and interactions over processes and tools 3. Working software over comprehensive documentation…martinfowler.com Writing The Agile Manifesto A long-form article entitled: "Writing The Agile Manifesto"
- 🔥 4
- ❤ 2
- 👍 2