Agile delivery! = Iterative development

I heard many people say: "We are doing agile development. Every release is divided into multiple iterations for development ."

However, I found that at the end of each iteration, the developed software could not meet the quality requirements of "launch", and even the software could not run.

 

They only focus on whether the story test of this iterative development has been completed, and some even focus on whether the development activity has been completed.

 

To achieve agile delivery, at least:

 

1. The story test of this iteration has been completed, and the bug has been fixed and verified;

2. The regression test has been completed, and the previously completed functions have not been damaged.

 

If you want to deliver in this way, and the automated testing is not complete, the solution seems to have only one "Increase the number of testers ".

Because regression testing is required after each iteration. As the development progresses, the number of developed functions increases, and the regression workload increases exponentially.

However, "adding Testers" is just a "leeching thirst", and HR can only recruit testers desperately.

 

Therefore, for agile delivery, automated testing is a required course, not an optional course.

 

Here, you may think that your team cannot do this at all.

 

So, my question is: Why can't I? Can't it be done now, or can't it be done all the time? What efforts should be made to achieve this? How long can it be achieved?

 

If you use agile delivery to develop software, answer these questions first!

 

 

If you want to do agile development without pain, you can open a website to split stories, play poker, and create backlogs. These are easy, but the results will not be very effective.

 

You will encounter more difficult problems, and even deny what you insisted on. At this time, your pain is apparent.

 

Only by healing these pains can you enjoy the joy of agile development!