introduction
The core idea of this book is "any technology has limitations." Therefore, it is impossible to find a best, most correct software development method.
People who report the situation in the software development project will also make similar observation errors because some facts are "facts". Need writers are no exception. They observe the user group and write a document that it is considered to be demand, in fact, there is a lot of observation errors.
Our understanding of "What is this" will go to different directions with how we decompose the elements.
The wrong vocabulary we used will mislead our understanding of the transaction.
In software development, everyone uses his own model to resolve the events experienced in the project, and thus the same mistakes will be made.
The existence of people in the project is an important factor in this influence project, and this factor is often overlooked.
There is an important thinking process in an inaccurate thinking, only the prototypes in the mind, have not been delineated.
Impossible to communicate.
Chapter 1
What I know can be compared with software development, rock climbing is the most appropriate.
Collaboration and pursuit goals
load
team
genius
Focus on skills
training
tool
Limited resources
Plan
Cancellation
interesting
Challenging
Danger
Software development is a collaborative game that creates and exchanges (resource limited). The main goal of the game is to deliver useful workable software. Secondary goals, the sedimentation of the game (the accumulation of knowledge) is preparing for the next game. The next game can be changing or replacing the current system, or create a related system.
A person's career is also a long-term game.
