Research of the Use of Agile Methodologies in the Czech Republic

Abstract

Agile methodologies have recently been widely gaining ground. We assumed another situation in the Czech Republic. Therefore we decided to conduct our own research based on a survey. The research objective was to determine the rate of agile approaches usage and practical experience with these approaches in companies in the Czech Republic. This paper presents the results of that research.

Appendix – The Survey Instrument

The questionnaire consisted of 18 questions, which are presented here in an abbreviated form. Offered answers are listed here only if they have an impact on the agility index.

• 1. Order the four parameters of a software development project (time, quality, cost, project scope) according to their priority and to how important you think it is to observe them. Please start with the most important parameter.Impact on the agility index: Total of values according to Table1.

  Table 1 Values for the agility index calculation

• 2. How do you deal with requirements changes?

  • (a) Changes are rejected (0 points)

  • (b) All changes are under the change management (1 point)

  • (c) Small changes are implemented, bigger ones under the change management (4 points)

  • (d) Only coarse grained requirements initially, further changes are accepted (6 points)Impact on the agility index: Number of points for a certain answer in brackets.

• 3. Do you use any software development methodology? (one of listed answers)

No impact on the agility index

• 4. Do you adapt your methodology to individual projects (e.g. according to the project scope or criticality)? (multiple answers allowed)

  • (a) No adaptation. (0 points)

  • (b) We do not adapt it because our projects have similar character (1 point)

  • (c) We scale our manner of work for large projects to more formality (2 points)

  • (d) We make our manner of work for small projects more flexible (1 point)

  • (e) We adapt our manner of work according to the particular client (2 points)

  • (f) Our methodology itself provides adaptation. (2 points)

    Impact on the agility index: Total of points for certain answer (max 3 points)

• 5. What principles are considered crucial in your methodology? If you are not using any specific methodology what do you personally consider crucial? To each question you can attach from 1 point (not included) to 7 points (CSF for the methodology)

  • (a) Sequence of development phases (analysis à design à implementation à deployment à maintenance) (indicator weight = 1)

  • (b) Big design up front (indicator weight = 1)

  • (c) Sophisticated change management (indicator weight = 0.3)

  • (d) Sophisticated requirements management (indicator weight = 0.8)

  • (e) Frequent delivery of functional software versions (indicator weight = 1)

  • (f) Source code quality (indicator weight = 0.6)

  • (g) Start programming as soon as possible (indicator weight = 0.8)

  • (h) Continuous testing (indicator weight = 1)

  • (i) Detailed project documentation ( (indicator weight = 1)

  • (j) Effective communication among team members and user (indicator weight = 0.4)

  • (k) User is integrated into development process (indicator weight = 1)

  • (l) People motivation (indicator weight = 0.6)

  • (m) Decision power (indicator weight = 1)

  • (n) Maximum compliance with original requirements (indicator weight = 1)

  • (o) User satisfaction (indicator weight = 0.3)

  • (p) Methodology adaptation (indicator weight = 0.6)Impact on the agility index: The assessment of the answers to questions which are important for traditional methodologies (a, b, c, d, i, n) is reversed. Values are then multiplied by an indicator weight and totaled up.

• 6. What are the weaknesses of the methodology you are using? To each question you can attach from 1 point (not a problem) to 7 points (critical problem)

  • (a) Low level of detail (indicator weight = 0.3)

  • (b) Large scope, very complicated (indicator weight = 0.5)

  • (c) Low level of this methodology knowledge (indicator weight = 0.2)

  • (d) Low flexibility (indicator weight = 1)

  • (e) User is not involved (indicator weight = 1)

  • (f) Methodology is concentrated mainly on technology (indicator weight = 0.3)

  • (g) Methodology demands highly qualified people (indicator weight = 0.7)

  • (h) No description of SW processes (indicator weight = 0.2)

  • (i) High skilled project manager (indicator weight = 0.7)

  • (j) Slight stress on design quality (indicator weight = 0.5)

  • (k) Strong stress on design quality (indicator weight = 0.8)Impact on the agility index: The assessment of the answers to questions which are important for traditional methodologies (b, d, e, f, k) is reversed. Values are then multiplied by an indicator weight and totaled up.

• 7. Do you know the terms “agile methodologies” or agile approaches to software development, and do you know what they mean? (one of listed answers).No impact on the agility index.

• 8. What do you think the advantages of agile methodologies are?No impact on the agility index.

• 9. What do you regard as being the disadvantages of agile methodologies?No impact on the agility index.

• 10. Assess the methodology you use in your company (if you do not use any specific methodology, assess your style of software development) according to the degree of its agility.No impact on the agility index.

• 11. Are you considering using any specific methodology in the future (if you do not use any) or are you considering any alteration to your current methodology? (one of listed answers).No impact on the agility index.

• 12. Assess the possible future methodology according to the degree of its agility.No impact on the agility index.

• 13. What risks do you see in the transition to a new methodology? (multiple answers allowed).No impact on the agility index.

• 14. What risks can you see in using agile approaches and what are your reasons for refusing them? (multiple answers allowed).No impact on the agility index.

• 15. Agile methodologies often have more significant demands on people. Do you consider your employees’ level of knowledge and readiness to agile development to be sufficient?No impact on the agility index.

• 16. Agile methodologies often lead to a significant increase in the “creative freedom” of programmers. Do you consider your employees’ character to be sufficient?No impact on the agility index.

• 17. Based on your experience, is there any difference between Czech and foreign employees as far as the use of agile methodologies is concerned? Choose the relevant option and give a brief description of where you see any differences. If possible, give a simple example from your practice.No impact on the agility index.

• 18. Do you consider the method and quality of software development methodologies education at Czech universities to be sufficient? If you do not, please give a brief explanation of any possible deficiencies.No impact on the agility index.