The sentiment of "rapid software development"

In the book, different people have different motives to make some more detailed analysis. For example: Developers have a sense of accomplishment (of course I think anyone who participates in this is a sense of accomplishment), development opportunities, work fun, etc. As for managers, the motivation is mainly: sense of responsibility, sense of accomplishment, and degree of recognition. Because they are not very clear at the beginning of these things, some of the work does not go very well. Now that you know something about it, it's very useful to motivate people. This chapter also gives examples of motivational failures such as exaggerated praise, which are useful for PM. So recommend PM to read this chapter.

Teamwork is a good introduction in Chapter 12, which tells you some examples of why teams fail. For example, lack of common aspiration, lack of identity, communication efficiency is low. I am more willing to read this chapter, the failure of the case also sounded a wake-up call for us. For example, before the alpha version of the communication is not very efficient, and we have some places motivation is not the same. Some students want to do a feature, some students want to do b feature. This is a typical example of a lack of identity. So these tips and lessons are very important to a team's classmates. PM, it's best to read some examples of how to inspire common motivation, which is very advantageous for a team.

Team assignments are important, especially in the book, which mentions how to monitor individual performance effectively.

Overall, the main reading is the three chapters on team work, which are worth reading for teamwork and how to control the process. Because all the work is done with a team entity.

In the process of software development, code writing and unit systematization test are carried out synchronously, which is very effective to improve the speed of software development.

The sentiment of "rapid software development"