Teams need a process!

This paper begins with a discussion of the importance of software development and the problems encountered by those trying to work effectively on software project teams. It is argued that for students to be effective in working on teams they need the discipline and organization offered by a rigorous team software process. The author describes his experiences in using the Team Software Process (TSP) to teach an introductory course in software engineering. The structure and key elements of the process are presented, along with techniques used in selecting and forming teams. The paper examines the TSP quality assurance features and finishes with a discussion of the techniques used to acquire feedback and to evaluate the affect of the TSP on student learning.

[1]  Watts S. Humphrey,et al.  Introduction to the Team Software Process , 1999 .

[2]  Peter J. Denning,et al.  Educating a new engineer , 1992, CACM.

[3]  Alain Abran,et al.  Guide to the Software Engineering Body of Knowledge - A Stone Man Version , 2000 .

[4]  Thomas B. Hilburn,et al.  Integrating the Personal Software Process (PSP) across the undergraduate curriculum , 1997, Proceedings Frontiers in Education 1997 27th Annual Conference. Teaching and Learning in an Era of Change.

[5]  Michael J. Lutz,et al.  Guidelines for Software Engineering Education Version 1.0 , 1999 .

[6]  Alain Abran,et al.  The Guide to the Software Engineering Body of Knowledge , 1999, IEEE Softw..

[7]  Watts S. Humphrey.  The Personal Software Process , 1997, Proceedings Frontiers in Education 1997 27th Annual Conference. Teaching and Learning in an Era of Change.

[8]  W. Wayt Gibbs,et al.  Software's Chronic Crisis , 1994 .

[9]  Watts S. Humphrey,et al.  Introduction to the Personal Software Process , 1996 .