What Is Agile Software Development?

Agile software development (also known as Agile software development) is a new software development method that has gradually attracted widespread attention since the 1990s. It is a software development capability that can respond to rapidly changing requirements. Their specific names, concepts, processes, and terminology are all different. Compared to "non-agile", they emphasize the close collaboration between programmer teams and business experts, face-to-face communication (think more effective than written documents), and frequent Delivering new software releases, compact and self-organizing teams, code writing and team organization methods that are well adapted to changing needs, and paying more attention to the role of people in the software development process.

Agile development is a new type that has gradually attracted widespread attention since the 1990s

• Incremental, not continuous: If development practices are truly agile, then the working software delivered is incrementally small. There is no need to wait until one stage is completely completed before starting another, and work is not to work towards a big release date. The work done, but not the business deadline, drives agile delivery. But agile spirit also acknowledges that business manipulates deadlines.

• Avoid unnecessary overhead: If practice is still truly agile, the team is committed to reducing project plans and documentation as much as possible. Rather than discussing what to do and then writing it down, it is better to do it quickly, otherwise, you are wasting time on work. In work-to-work, the agile spirit is conducive to actual work-for delivering work software. And it's also worth face-to-face communication via email and other written documents.

• Collaboration: Team members have been interacting with others, as well as some external stakeholders, as needed. In the world of agile coaching, Lisa Crispin, the head of the entire team, is able to solve all problems before they arise. A true agile team is self-help. They allocate the work that needs to be done. Although each member's tasks are within their expertise, they still need to work with the team. No one's work is isolated, and no team itself works independently. Without significant input from business stakeholders and external experts such as user experience, the team cannot move the project forward,

• To tell the truth: To ensure true agility, everything the team discusses about the project must be true. In some critical areas of expertise, such as sprint testing coding skills, they acknowledge gaps. Regarding actual productivity, they have to tell the truth; that is, whether the team is capable of doing x in time y. They admit their mistakes. Telling the truth is a challenge, because they are afraid to admit that shortcomings make them look weak. But Agile knows that it takes courage to tell the truth. Acknowledge the problem requires confidence, then quickly solve it. ^[1]

  in

  There are already some

  Included

  • Test-Driven Development, TDD / Test-Driven Development

  • Behavior-Driven Development, BDD / Bahavior-Driven Development

  • Scrum ^[2]