本論文嘗試分析團隊溝通的內容，以 abstraction level 來分類，整理出週期規律，且提出一些準則。團隊溝通一開始會從 high level的需求，往 low level 的架構設計討論，然後再往更 low level 的實作。之後會在這些層級來回移動，循序漸進。本文提出開發環境監測系統的例子，在兩組人員的討論過程，可以明顯的看出這些規律。最後根據這些規律提出一些準則: 1) 循序漸進的溝通， 2) 文件的重要性， 3) 討論人數與abstraction level 的關係。We tried to analyze communication of an agile team, classified contents of communication according to abstraction level, cleaned up a cycle rule, and proposed a number of practices. At the beginning, the team communicated from the highest level requirements, then go down to a lower level architecture design, eventually go to the lowest level implementation. After that, the communication will move back and forth in abstraction levels. In our example of developing the surveillance system, the cycle rule is obviously observed in the interaction of two pairs. At the end, we proposed three practices according to our observation: 1) communicate step by step, 2) the importance of documents, 3) the relationship between the number of people and the abstraction level.
