Toward a Whole(er)
team
by Matt Ganis
Presented at the Nov. 13th
meeting of APLN-NYC
the powerpoint or pdf version
In this presentation (which is part of my
Doctoral Dissertation at Pace
University's Siedenberg School of Computer Science) I present
the results of various retrospectives and team evaluations taken
over a 3 year period to access the value of the "Whole team"
practice in Agile methods.
There are various practices that surround
Agile methods such as pair programming, coding standards, planning
games, etc. One that seems to implied (I rarely see it mentioned as
one of the key practices) is that of the whole team - the concept
that everyone that is required for a successful launch of a project
should be part of the Agile team.
In this work, I evaluated the various
team configurations we've gone through at ibm.com (an organization
within the Sales & Distribution division of IBM) in an attempt to understand the
ramifcation of not implementing a whole team. While the results are
preliminary, it appears there is a marked increase in customer
satisfaction as well as team satisfaction when the use of "whole
team" is employed.
|