Five questions about fast Software Development

1. In the first case about square_tech in the article, code testing and optimization are conducted only after all programs are completed. This should not meet the requirements of fast software development. If a test engineer joins software development at the very beginning, will the software development process be faster?

2. I have never been clear about the differences between several PM. Although I checked some information online, I still don't understand the difference between product manager and program manager. In the book the beauty of programming, I learned that PM in Microsoft belongs to R & D, that is, Program Manager belongs to R & D personnel, but when the company was founded, the "mountain migration" said PM didn't need to write code. Is that true?

3. In fact, I don't know why quick development is required because of effective development. From the comparison of quick software development, we can see that effective product development is better than rapid development, and the progress and cost are not too bad. I know that the software industry is very competitive. Whoever comes out first may seize the market, but if there are not enough good products, when better products come out, will it be replaced? Even if you can make adjustments after you go public, you may spend more energy and time.

4. Are there only one product manager or test engineer in a small project team who knows this product better?

5. The core of a chief programmer team is the chief programmer, but such a team has great requirements for risk control. If the chief programmer of this team leaves the project team halfway for any reason, to ensure the normal operation of this project, how can this team be saved and what form of team should be transformed.

Five questions about fast Software Development