TEAM BUILDING IN AGILE SOFTWARE DEVELOPMENT:

Transcription

1 Prof. Dr. Eckhart Hanser, Hanser: DHBW TEAM Lörrach, BUILDING Bio-Systems IN AGILE PROJECTS Informatics / Software-Engineering loerrach.de e TEAM BUILDING IN AGILE SOFTWARE DEVELOPMENT: THE PROJECT MANAGEMENT LABORATORY OF BA LOERRACH Prof. Dr. Eckhart Hanser Duale Hochschule Baden-Württemberg Lörrach Baden-Württemberg Cooperative State University Head Department Applied Informatics/Bio-Systems Inform. hanser@dhbw-loerrach.de Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 1

2 Stein Biosystem-Informatik des Anstoßes: Eigene Projekte in der Praxis Förderung des Teambildungsprozess unter Studierenden an der DHBW Lörrach / Bereich Technik: Ziel: Informationstechnik (IT) Biosystem-Informatik Vorstellung des Meta Agile Process Model (MAP) Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 2

3 There are Projects with changing specifications Refactoring necessary Documentation has a short lifetime! project aim #3 Aim changes! #3 project aim #2 Project start t Iter. 3 Iteration 1 Iter. 2 Aim changes! #2 Original project aim Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 3

4 Agile Manifesto Kent Beck, Alistair Cockburn, Martin Fowler, Jim Highsmith, Robert C. Martin et.al., Four principles: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 4

5 Famous agile representative: Kent Beck s extreme Programming g (XP), Important XP rules to be analyzed: Designing User Stories Collective Code Ownership and Software Integration Pair Programming Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 5

6 IT laboratory / DHBW Lörrach 2004, 2005, 2006, 2007, th semester of Applied Computer Science / Information Technology each spring: 11 sessions with 5 (4) hours => Up to 800 project hours each spring. The size of each course determines the number of the team members => Up to 20 team members (students + prof.) : about project hours. Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 6

7 Project: Development of an marketing software Test content for the interpm Hi $Title$ $Name$, I m glad to be here in Düsseldorf. Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 7

8 IT laboratory of session 2005 BA Loerrach Prerequisites: Development platform: The lecturer fills the positions of project and quality manager with suitable managers (i.e. students). In the beginning the rest of the team has no structure, should however form XP pairs. Members know about process models, especially XP. The customer (i.e. the lecturer) is a team member. MS Visual Studio.NET Team aims: Success? Common programming of a fully featured marketing system. XP is required (= decision of the lecturer). Successful product, successful process (in the end). Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 8

9 Introduction - Agile Manifesto - extreme Programming IT laboratory Questions Psychology - Conclusions Key questions, I want to investigate: 1. Roles of Project and Quality Manager in agile projects? 2. Which (XP) practices are not the result of the selforganization of the team? 3. Is there an ideal mini i team size (other than 2) for successful teams? Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 9

10 Introduction - Agile Manifesto - extreme Programming IT laboratory Questions Psychology - Conclusions Q1: The project manager in an agile project (i.e. session 2005) characterizes his project role as coordinator of the project problem solver communicator.net expert co-designer of user stories (together with the client) Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 10

11 Q1: The quality manager in an agile project (i.e. session 2005) characterizes his project role as product and project quality assurance (reviews, testing) ti problem solver communicator.net expert co-designer of user stories (together th with the client) Agrees with the view of the project manager! No classical project roles in this agile project. Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 11

12 Introduction - Agile Manifesto - extreme Programming IT laboratory Questions Psychology - Conclusions Key questions, I want to investigate: 1. Roles of Project and Quality Manager in agile projects? 2. Which (XP) practices are not the result of the selforganization of the team? 3. Is there an ideal mini i team size (other than 2) for successful teams? Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 12

13 Introduction - Agile Manifesto - extreme Programming IT laboratory Questions Psychology - Conclusions Q2: Design of user stories In every session only project manager, quality manager and few team members where interested in creating user stories. Only when the mini teams had chosen their story cards, they began actively to make a detailed low level design. We saw no readiness in the team for collective design or code ownership. No collective code ownership Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 13

14 Introduction - Agile Manifesto - extreme Programming IT laboratory Questions Psychology - Conclusions Q2: Integration XP says: Only a pair integrates code at a time. But our experience in all sessions: Integration is not a result of the self-organization of the team (> 3 programmers) integration only took place after heavy interventions of the customer. The lecturer had to take over the role of a communicator not of a typical customer! not to solve the problem, but to communicate its existence. Integration had to be centralized. Not only one machine but also one team member (with full responsibility) New role: Integration Engineer This has to be controlled strictly by the project management. => We need a project management! Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 14

15 A new team role: Integration Engineer sits a little aside Lone Wolf session 2005 Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 15

16 Introduction - Agile Manifesto - extreme Programming IT laboratory Questions Psychology - Conclusions Key questions, I want to investigate: 1. Roles of Project and Quality Manager in agile projects? 2. Which (XP) practices are not the result of the selforganization of the team? 3. Practical experience shows that t teams with more as about 5 members subdivide into mini teams : 1. In XP such a mini team is called a pair (2 members). Are these pairs successful? 2. Is there an ideal mini team size (other than 2)? 3. Do we see a self-organization process of successful mini teams? 4. What is the member structure? Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 16

17 Q3: Mini i team size session 2004 session Mini teams with 3 members as starting point. Result: XP pairs do not occur. XP pairs as initial mini teams. Minimal mini team size remains 3. The most successful mini team has 4 members. Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 17

18 Project start Q3: Mini i team size We see 3 pairs A triplet First pair grows into a triplet! session 2005 Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 18

19 2 weeks later But also one Super team with 6 members for integration ti session 2005 Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 19

20 4 weeks later Only 1 "classical XP pair XP pairs decrease! session 2005 Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 20

21 Mini Team Size session 2004 session 2005 Session 2008 Mini teams with 3 XP pairs as initial mini XP pairs as initial mini members as starting teams. teams. point. Result: XP pairs do not Result: Number of XP Result: 3 XP pairs occur. pairs seems to decrease. survive. Minimal mini team size Most mini teams grow in 50% of the team are XP remains 3. size (3, 4 or more). pairs! The most successful mini team has 4 members. In special phases, e.g. integration, we see a team size of 6 members. Integration: several pairs form a larger integration team. Mini team size oscillates depending on the phase/activity. Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 21

22 Inter XP pair relations (2008) Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 22

23 Super team explained: 5 members Integrates the code in a critical phase. The members take responsibility for the integration. The project would fail, if they did not succeed. Integration Engineer session 2005 Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 23

24 Organizational psychology: discussed with Rainer Baldegger, Erfolgreich im Team Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 24

25 A successfull Mini Team needs particularly Creative Mind Technical Expert Team Worker Communicator Technical Problem Solver Quality Tester Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 25

26 Details of the super team Project Manager external Communicator (Project manager) Problem solver / integrator Lone wolf Expert, creative mind Integration Engineer Team worker Team worker internal communicator, creative mind Expert, creative mind session 2005 Quality tester Quality Manager Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 26

27 Introduction - Agile Manifesto - extreme Programming IT laboratory Mini team size Psychology Actual results IT-Labor 2007 Prozess Crystal Clear Bewertung des Prozess durch das Team / Umfrageergebnis: Schulnoten! Wissenschaftliche Begleitung: aus Studienarbeit Niko Hättich 2007 Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 27

28 Introduction - Agile Manifesto - extreme Programming IT laboratory Mini team size Psychology Actual results Crystal Clear 2007 (1) Note nur für interne Osmotische Kommunikation nachvollziehbar (2) Reflektion nicht festgestellt. (3) Lieferungen unregelmäßig. 2007: Team fährt fährt seinen eigenen agilen Prozess! Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 28

29 Meta Agile Process Model (MAP Methodology) A successful project in a small to medium-sized team needs the following ingredients : Customer available to the team One or two Communication managers, good and flexible for project and quality management Integration engineer continuous software integration Well-balanced project team with a good psychological process 6 characters / types of project members (organizational psychology) Mini-Team-Size is oscillating! Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 29

30 MAP Referenzprojekt aus der Chemie-Industrie: Sep. 2008: Erfolgreiche Diplomarbeit als Feldversuch zur agilen Methodology MAP Laborergebnisse werden im Wesentlichen bestätigt! Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 30

31 Rollen: Kunde Rotes Telefon Projektleiter 1 Qualitätsmanager 1 1Person Entwickler 5 (im Schnitt 3) Integrierer Tester 1 1 (hier = PL) Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 31

32 Probleme mit Pair Programming bestätigt: Voraussetzung: Sozialkompetenz Problem: Effizienz PP im Team als nicht notwendig erachtet! Truck-Faktor durch Kommunikation reduziert. Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 32

33 Allg. Projekt mit IT-Fokus (Okt. 2008): LKW-Abfertigung in einer Ölraffinerie Highlight: Impl. eines Zugangskontrollsystems Der Kunde kommt aus dem operativen Betreiber-Bereich mit starken DV-Kenntnissen Projektleiter kommt aus der Projektabteilung für Neubau- Projekte (eigene Anlagenbauprojekte bis 15 M pro Proj.) hohe Schnittstellen zu vom Projekt Betroffenen, Beteiligten und Interessierten; vor allem zu den Gewerken Tiefbau, Elektrik und Mess- und Regeltechnik MAP wird bestätigt! siehe auch GPM-Newsletter Prof. Dr. Eckhart Hanser, Duale Hochschule BW Lörrach, BW Cooperative State University, Department of Applied Informatics /Bio-Systems Informatics Folie 33