I went on to see the next chapter of the Dream Break code. The method of the Nineth chapter is more impressive. It mentions IBM. Ibm (1 (2< Span style= "font-family: the song Body;" ) plan must conform to the reality ----" bottom up " " " then 2001 year 17 xp and scrum > It's starting to pop . During the learning process, I learned about Agile software development. As far as I know, it is very efficient, but it does not apply to all, need to change according to circumstances, rather than copy copy.
In short, throughout the full text, this is a software development failure case. In the author's account, we can see a lot of the shadow of our own software development, as well as the problems they encountered. Ignoring their approach in the end is not good, we can see that software development is really a very difficult thing. We have a lot of problems, whether it is teamwork or technical problems, it is always bumpy on this road. But I still hope, anyway, "Dreaming in Code", this beginner's mind has not changed, we can continue to move forward.
Dream Break Code Read Note 03