Agile Software Development Practice Adoption Survey Narendra Kurapati, Venkata Sarath Chandra Manyam, and Kai Petersen Blekinge Institute of Technology.

Agile Software Development Practice Adoption SurveyNarendra Kurapati, Venkata Sarath Chandra Manyam, and Kai Petersen

Blekinge Institute of Technology

Ericsson AB

XP 2012

100522039 曾毓傑

Outline• Introduction• Survey Design• Results

Introduction• Agile methodologies are often not used “out of the box” by

practitioners, instead they select the practices that fit their needs best.

• We investigated used agile practices, combinations, degree of compliance, and how successful practitioners perceive the adoption.

Introduction (Cont.)The following survey aims at answering the following research questions:• RQ1: How commonly used are individual agile practices?

• RQ2: Which agile practices are used together by practitioners, and how common are the combinations?

• RQ3: To what degree does the software industry comply to Extreme Programming (XP) and Scrum?

• RQ4: As how successful do the practitioners perceive the adoption of agile practices in terms of customer satisfaction and employee satisfaction?

Survey Design• Find 25 agile practices used in global software

development• Send survey out to 600 practitioners, and post survey on

LinkedIn, Yahoo, and Google groups• Survey structure

• Introduction: Shortly explain the purpose• Demographics: Ask information about organization• Agile Practice Adoption: Select agile practices that they use in

their project• Agile Practice Adoption: Select agile practices that they use in

their organization• Employee Satisfaction and Customer Satisfaction• Contact Details

Agile Practices Selected1. Office Structure

2. Pair Programming

3. Planning Game/On-Site Customer

4. Tracking Progress

5. 40 Hour Week

6. Refactoring

7. Retrospective

8. Short/Small Release

9. Simple Design

10. Sprint/Iteration

11. Sprint Planning Meeting

12. Sprint Review Meeting

13. Stand-ups

14. Stories/Features

15. Team Work

16. Test-Driven Development

17. Testing

18. Coding Standards

19. Collective Ownership

20. Communication

21. Configuration and Change Management

22. Continuous Integration

23. Documentation

24. Informative Workshops

25. Metaphors

Results: Response Type

Results: RQ1 in Project Level

Results: RQ1 in Organizational Level

Results: RQ2 in Project Level

Results: RQ2 in Organizational Level

Results: RQ3

Results: RQ4 Employee Satisfaction

Results: RQ4 Customer Satisfaction