Agile Software Development: Part I agile development

Man piece: interaction between people is complex, and its effect is never expected, but it is the most important aspect in the work.

People are not "plug-in is compatible with programming devices ". -- Cohesion

 

1. agile practices

Agile Software Development Declaration

More individuals and interactions than processes and tools

Ø software that can work is better than comprehensive documents

The software used for work is the primary progress measurement standard.

Customer cooperation is better than contract negotiation

Responding to changes is better than following the plan

Make a detailed plan for the next two weeks, make a rough plan for the next three months, and then make a rough plan in the future.

2. Extreme Programming

Extreme Programming.

Ø short delivery cycle (iteration every two weeks-customer feedback)

Testing-driven development (test script)

JUnit, nunit

3. Plan

When you can measure what you say and express it with numbers, it means you understand it. If you cannot measure it, you cannot express it with numbers, it means that your knowledge is scarce and unsatisfactory.

4. Test

Test-driven development method:

Ensure that every function is correct

Develop programs from the perspective of program callers and design software that facilitates calls

The program is testable and decoupled, prompting isolation between modules

For example, remove the coupling between the user interface and business rules.

Testing is an invaluable form of documentation

5. refactoring