Agile Development pursues simple design

My point of view-agile development pursuing simple design

 

1. What is simple design?

Introduction: There is a famous lazy principle in extreme programming, called the KISS Principle. KISS is the abbreviation of Keep it simple and stupid. To put it simply, the design should be as simple as possible.

Naresh Jain explains the simple design in this way. "A simple design doesn't affect my work schedule ".

My point is: To provide a strategy to extract simple scenarios from complicated business areas, and to focus on practical design, it is simple design.

 

2. Significance of simple design

The agile development idea is to embrace changes, pursue simple design to solve software complexity, build a reasonable and appropriate structure, and have a good testability, reusability and scalability architecture. To put it simply, the system software to be developed uses agile development: on the one hand, we need to maintain a simple design without making meaningless functional predictions; on the other hand, we need to embrace changes, meet future requirements with minimal changes to the structure and code.

> Dynamic and clear workflow.

> Supports "embracing changes" to promote control and balance over changes.

> Facilitate communication between developers and users.

> Good support for testing and maintenance. Simple testing requires neat Code (No reusable, redundant, useless code, well-organized Code, etc ).

 

3. How can we use simple design ideas for agile development?

> Effective use of UML

> Develop neat code

> The function runs normally as expected.

> Effective communication and clear business logic

> Open management and innovative thinking

 

Agility is just a tool, not a means to reach the end.