Some Research on Agile Software Development

Transcription

1 Some Research on Agile Software Development Robert Feldt SAST Väst, Lindholmen, Division of Software Engineering HOSE Lab (Human-fOcused SE)

2 Motivation in 22 agile devs [Whitworth2007]

3 Motivation in 22 agile devs [Whitworth2007] Daily meeting Ease of Interaction Enjoyment & Excitement

4 Motivation in 22 agile devs [Whitworth2007] Daily meeting Ease of Interaction Enjoyment & Excitement Planning Game Adjust to individual needs

5 Motivation in 22 agile devs [Whitworth2007] Daily meeting Planning Game Ease of Interaction Re-prio & re-planning Adjust to individual needs Enjoyment & Excitement

6 Motivation in 22 agile devs [Whitworth2007] Daily meeting Planning Game Ease of Interaction Re-prio & re-planning Adjust to individual needs Collective Participation Enjoyment & Excitement Motivation

7 Motivation in 22 agile devs [Whitworth2007] Daily meeting Planning Game Short iterations Ease of Interaction Re-prio & re-planning Adjust to individual needs Collective Participation Regular Delivery & Feedback Enjoyment & Excitement Motivation

8 Motivation in 22 agile devs [Whitworth2007] Daily meeting Planning Game Short iterations Business Value Focus Ease of Interaction Re-prio & re-planning Adjust to individual needs Collective Participation Regular Delivery & Feedback Clear Objective Enjoyment & Excitement Motivation Common goal

9 Personality and Teams [Acuna2009]

10 Input - Process - Output Model [Acuna2009]

11 Personality and Teams [Acuna2009]

12 Linking Personality to Views & Attitudes

13 Linking Personality to Views & Attitudes 47 Industrial SW Engineers

14 Linking Personality to Views & Attitudes Personality Test 47 Industrial SW Engineers

15 Linking Personality to Views & Attitudes Personality Test SE Views & Attitudes 47 Industrial SW Engineers

16 Linking Personality to Views & Attitudes Personality Test Patterns? SE Views & Attitudes 47 Industrial SW Engineers

17 Linking Personality to Views & Attitudes Personality Test Patterns? SE Views & Attitudes 47 Industrial SW Engineers

18 Linking Personality to Views & Attitudes Personality Test Patterns? SE Views & Attitudes Younger, Many things same time, Parts of projects, Male 47 Industrial SW Engineers

19 Linking Personality to Views & Attitudes Personality Test Patterns? SE Views & Attitudes 47 Industrial SW Engineers

20 Linking Personality to Views & Attitudes Personality Test Patterns? SE Views & Attitudes Prefer working (with)? 47 Industrial SW Engineers

21 Linking Personality to Views & Attitudes Personality Test Patterns? SE Views & Attitudes Prefer working (with)? Take decisions affecting quality? 47 Industrial SW Engineers

22 Personality and Software Engineering [Feldt2010] Intense personality <-> multiple projects parts of projects Age & Gender differences Higher Extraversion <-> prefer team work prefer plan & schedule Higher Openness <-> whole project responsibility

23 Agile (RE) Practices - Pro / Con Face2Face communication & User stories Saves time Requires trust Customer on site Customer drives Not all user groups represented Iterative req engineering [Cao2008] Clearer reqs Customer relation Minimal docs when problems Cost & schedule estimation Non-functional requirements

24 Agile Practices - Pro / Con Extreme Prioritization Clearer reasons Re-prio is easier Business Value to narrow Instable with re-prio Managing Change through Constant replanning Fewer changes Smaller changes Architecture suffers Refactoring not enough [Cao2008]

25 Agile Practices - Pro / Con Prototypes Quicker feedback Unrealistic dev speed expectations Test-driven Development Tests capture reqs Requires close customer collab Freedom to experiment Developers resist Reviews & Acceptance tests [Cao2008] Status report to customers Hard to create acc.tests

26 ? [Kniberg2008]

27 Up to 2006

28 Introduction & Adoption Human & Social Factors Perceptions Comparisons

29 Introduction & Adoption Human & Social Factors Perceptions Comparisons Agile practices easy to introduce and work well Difficult to intro in large/complex organizations Benefits: Customer collaboration Defect handling processes Learning among developers Estimation of time/cost easier Some studies saw pair programming as inefficient XP works best with experienced teams

30 Introduction & Adoption Human & Social Factors Perceptions Comparisons XP well accepted in different organizations (hierarchical structure to little or no control) Good interpersonal skills and trust important for successful XP teams Individual autonomy must be balanced with team autonomy Making progress tracking visible and audible important Important standardization of collaborative work

31 Introduction & Adoption Human & Social Factors Perceptions Comparisons Customers liked more (give/get) feedback On-site customer stressful/unsustainable Developers more satisfied with work and product Pair programming considered tiring since it required focused concentration Pair programming hard when skills differ much Test-driven development was difficult

32 Introduction & Adoption Human & Social Factors Perceptions Comparisons Agile can more easily incorporate changes and show business value Can be combined with traditional stage-gate project management Subjects believe agile increases productivity

33 XP Buy-in [Gray2006]

34 Sources Dybå & Dingsöyr, What do we know about agile sw dev?, IEEE Software, 2009 Feldt et al, Links Between the Personalities, Views and Attitudes of Software Engineers, IST, 2010 Whitworth et al, Motivation & Cohesion in Agile Teams, XP Conf 2007 Gray et al, Forming successful XP teams, AGILE Conf Cao et al, "Agile Requirements Engineering Practices: An Empirical Study," IEEE Software, vol. 25, no. 1, pp , Jan./Feb Kniberg, H., Slides on Agile and Lean Software Development, Crisp AB, Acuna et al, How do Personality, Team Processes and Task Characteristics Relate to Job Satisfaction and Software Quality?, IST, 2009.