“Agile Software Development: Principles, Mode, and Practice (C# . Revised Edition)” Agile Development Part 1 Part 1

Chapter 1 of Book 1 “Agile Software Development: Principles, Models, and Practices (C# Edition)” is in the asynchronous community in this section. Editor-at-Chief Sun Ming: Yang welcomes, more chapters can access the “asynchronous community” public account in Yunqi community.

The first part of the rapid development

Agile Software Development: Principles, Mode, and Practice (C# Edition. Revised Edition)


The interaction between people is complex and it was always difficult to predict their impact, but they are the most important aspects of the job.

DeMarco and Timothy Lister, Human Temperament

Principle, pattern, and practice matter, but so do the people who make them work. As Alistair Cockburn said: “Processes and technologies only have a leading influence on the outcome of a project. The first influence is human.

If a team of programmers is regarded as a component (component) system that is controlled by a system, it cannot be controlled by them. According to Alistair Cockburn, people don’t “plug in compatible programming hardware”. If we want the project to be successful, we must build a team that is both spiritual and self-organised.

Companies that encourage such team building are more competitive than unrelated, which is the same group of unrelated people and similar groups of people. The intensive software team is the strongest force in software development.

1 He said in a private conversation with me.
This article is for educational and communication purposes only and is not an asynchronous view of the community. For non-blank typography, please credit the translators and sources and keep the original link to this article.

Leave a Comment