| 摘要: | 現今軟體專案通常以團隊的方式進行。團隊的運作，有時能讓工作更有效執行，但有時也會產生一些負面效果，因此，如何讓成員之間的共通合作更有效率已成為今日的管理議題。有學者提出會議流的概念來導入專案管理，嘗試解決專案中片面溝通與片段管理的問題，但今日相關研究當中，尚缺乏實際導入會議流後的效益探討，因此，本研究嘗試將會議流導入到組織中的軟體開發專案中，針對軟體專案的通病與該公司面臨的問題，提出一套會議流模式，協助組織解決相關問題，以達成務實的溝通與嚴謹的驗證。 本研究將以個案研究的方式進行，依據個案公司之作業制度，塑模出會議與會議流模式，並建立出團隊成員間的溝通管道以及會議流的調適做法，然後藉由討論溝通的本質與目的來提升組織溝通的效率。在導入會議流一段時間後，我們將從這些專案的成員當中選出代表，以焦點團體法的方式進行訪談，從中了解每位成員對於會議流的看法與觀點，並且探討是否可達到會議流中所述之效益、以及能否解決公司所面臨的問題。最後將研究結果進行討論，針對實際運用與公司限制情形說明，並進一步提出未來相關研究的方向與建議。 Nowadays software often developed in team. Although teamwork may be more efficient, however, sometimes negative effect may occur too. Therefore, how to make team members work together more efficient has become a managerial issue today. Scholars have proposed the concept of meeting flow in the implementation of project management, trying to resolve the problems of one-sided communication and discontinuous management in the project. However, there is no research about the analysis of the result of the implementation of meeting flow until now. According to this, the research tries to use meeting flow in the software project development in the organization. For the common failing factors in software project and the problems which the company encountered, we have designed a meeting flow model to help them resolve above problems, and to achieve effective and efficient communication and careful and conscientious verification. This research is a case study about software project. By the standard operation and regulation, we modeled a meeting flow model, and then created a communication channel between team members, and planned a tailoring guideline for meeting flow. Next, we improved the efficiency of the communication in the organization by discussing the essences and the purposes of communication. After the implementation meeting flow for a while, numerous members from the project teams were chosen and interviewed with focus group method, viewpoints and experiences regarding the meeting flow collected. The collected data were discussed and analyzed to see if the benefit of meeting flow in reality is the same as in theory, and whether it can resolve the problems the company has encountered or not. Finally, we made a conclusion about this research, comment on the process of implementation and the restraints in this company, and furthermore proposed a suggestion and guideline for the future work. |
