Agile 2-Overview of Agile Software Development

Agile Software development overview

As mentioned above, agility can be seen as a solution to problems. Next we will explain agile software development from the perspective of agile problem solutions.

Agile Software Development

Software development is a typical situation in which the problem itself and the ability to solve the problem are uncertain. Software Projects originated from the concept of human beings and are constantly changing over time. The project team's understanding of the project has been deepened over time, the member capabilities have been constantly improved, and the work style and process changes have led to the constant change in the Team's development capabilities.

Agile Software development is divided into three layers.

Product Layer

1.
Questions and question participants

The problem is the product concept. The problem Reporter is the customer (business manager) and the problem solver is the feature team.

2.
Problem decomposition and Test

A)
Problem breakdown

Resolve the problem from product conception to business characteristics. Business characteristics are issues that can be tested by the problem Reporter.

B)
Problem Test

Verify the completed business features in workable software. Workable software is the basis for the customer to verify the integrity of the problem.

3.
Iteration

The iteration size ranges from 1 to 4 weeks, which is a customer's acceptable frequency (rhythm ).

Business feature layer

1.
Questions and question participants

The problem is the business characteristics. The problem initiator is a feature team, and the problem Releaser is a feature team or a person responsible for business characteristics.

2.
Problem decomposition and Test

A)
Problem breakdown

Break down the problem from business characteristics to units. Unit is a unit issue that can be tested by the feature team.

B)
Problem Test

Check the unit completion status in the operational business characteristics.

3.
Iteration

The iteration size ranges from hour to day, which is an acceptable frequency (rhythm) for the feature team ).

Unit Layer

1.
Questions and question participants

The problem is the unit. The problem initiator is a developer, and the problem solver is the developer or another developer (Pair programming ).

2.
Problem decomposition and Test

A)
Problem breakdown

Resolve the problem from unit to unit responsibility.

B)
Problem Test

Test the fulfillment of unit responsibilities in the expected unit test.

3.
Iteration

The iteration size ranges from hour to hour, which is an acceptable frequency (rhythm) for developers ).

Common agile software development methodology scrum

Scrum and agile software have a lot in common. Compared with agile software development, we can see that the agile practices of scrum focus on the high-level, but lack the low-level agile practices.

Extreme Programming XP

XP is more consistent with agile software development. It is composed of a series of simple but interdependent practices, which are combined to form a whole better than partial integration.