Agile process cracking waterfall Process

Next let's take a look at how agile processes solve waterfall-style process problems one by one:

Ø deployment process problems:

The release time is getting longer and longer. In an agile process, a version is composed of a series of incremental integration, which are developed in an iterative and sequential manner. We can also stop iteration at any time. Once you find that the product has reached the maximum value, especially when you find that more than half of the software's functions are rarely used, you can stop iteration. We can also stop iteration and release software when the delivery deadline or budget limit is reached. We only develop and accumulate valuable incremental data.

Ii. waterfall process:

Cannot be released on time. In an agile process, the release delay of a version is no more than 30 days, because the maximum duration of each iteration is only 30 days. When the delivery deadline is reached, you can deliver the cumulative increment. Because it does not develop low-value functions in iterations, a complete system can be released earlier than before. In traditional development processes, common functions account for less than half of all functions. In agile processes, we do not waste time on uncommon features.

Iii. waterfall process problems:

In the final stage of version release, software stability is getting longer and longer. In an agile process, the incremental data produced by each iteration is complete and available. The incremental data generated by subsequent iterations will contain the incremental data generated by all previous iterations, therefore, the incremental data generated by any iteration is complete and available. That is to say, there is no software stabilization period because the software remains stable.

Question 4 of the waterfall process:

It takes longer and longer to make the plan and is inaccurate. In agile processes, we no longer make big and comprehensive plans, but simply set the final goal and then determine the high-value features and features required to achieve the goal, the delivery date and estimated cost are also determined. In this way, it usually takes only 20% of the waterfall or prediction process to make a plan before the first iteration starts. We will only make detailed plans for the coming iteration requirements, so we call each iteration plan a "timely rain plan ". It is also worth noting that the demand is emerging. when reviewing the software increment generated by iteration, we may find the best requirement to be achieved in the next iteration.

Question 5:

It is difficult to make changes during release. The concept of mid-term version release no longer exists in iterative incremental projects. We can discover or propose requirements at minimum cost before each iteration starts.

Question 6:

Quality continues to deteriorate. In an agile process, the increments produced by each iteration are completely available. Therefore, incremental data must have passed the quality test. The increment produced by subsequent iterations must also meet the same quality requirements. That is to say, we no longer have to sacrifice quality in the final stage of the project to catch up with the delivery deadline, because quality is always accompanied by the entire development process of this software.

VII of the waterfall process:

The competition effort frustrated employees' morale. The version stabilization phase is no longer needed, so the "death Journey" of working overtime also follows.