Survey Templates Surveys Analysis of Software Testing in Icelandic Scrum Pr

Analysis of Software Testing in Icelandic Scrum Pr

Analysis of Software Testing in Icelandic Scrum Projects

Preview this template

Dear recipient

I'm working on a final research project in computer science at Reykjavik University. In this research, I'm analysing software testing in Icelandic Scrum projects. The project is supervised by Marta Kristin Larusdottir.

It is very important for me and my studies at Reykjavik University that you are willing to complete the questionnaire. If you belief that someone else at your company is better suited to complete the questionnaire, please forward it to the right person.

The survey should on average take some 15 minutes to complete. If you have questions at any time about the survey or the procedures, you may contact Emma Run by email at the address specified below.

Thank you very much for your time and support.
Emma Run Bjarnadottir

Please start the survey now by clicking on the Continue button below.

Background information (1)

1.What kind of software development process(es) does your company use (please select all that apply)?

Scrum

XP (Extreme Programming)

Waterfall model

RUP (Rational Unified Process)

Our own process

Other, please specify:

2.What percentage of your company's software development department (i. hugbúnaðardeild, þróunarsvið) uses the Scrum development process (or a similar Agile development process if it applies)?

0 - 20%

21 - 40%

41 - 60%

61 - 80%

81 - 100%

3.Does your company have internal Software Testers?

Yes

4.Does your company use external Software Testers? (E.g. SJÁ - http://sja.is/)

Yes

Background information (2)

5.What is your primary role in relation to the Scrum development process (or a similar Agile development process if it applies) in your company?

Software Tester

ScrumMaster

Product Owner

Programmer

Other, please specify:

6.If you are a Software Tester, please select the range of years you have worked as a Software Tester:

Less than 1 year

1 - 3 years

4 - 6 years

7 - 9 years

10 - 14 years

15 years or more

I'm not a Software Tester

7.Please select the range of years you have been working in the software industry:

Less than 1 year

1 - 3 years

4 - 6 years

7 - 9 years

10 - 14 years

15 years or more

8.What is your company's main industrial section?

Airline industry

Banking, Insurance or Finance industry

Computer service or Software development company

Government and municipalities (education etc.)

Gaming industry

Shopping or Service

Telecommunications or Telephone company

Other, please specify:

9.Please select the total number of employees in your company's software development department (i. hugbúnaðardeild, þróunarsvið):

1 - 5

6 - 10

11 - 19

20 - 39

40 - 59

60+

Details on Scrum or similar Agile development process

10.Which of the following items applies to the Scrum (Agile) development process practice in your company?

The role of Product Owner is used

The role of ScrumMaster is used

Requirements/user stories are kept in a Product backlog (PB)

Planning poker is played on PB items

A sprint backlog is established at the beginning of a sprint (iteration, during sprint planning)

Each sprint/iteration is 2 - 4 weeks long

Potentially shippable product exists at the end of a sprint

A sprint review meeting is held at the end of a sprint

A sprint retrospective meeting is held at the end of a sprint

Scrum (Agile) metrics are used, like burndown charts

Other, please specify:

11.Communicating is important in practicing the Scrum (Agile) development process, which of the following is used in your company?

Daily scrum meetings/stand-ups are being held

The Scrum (Agile) teams that are located at one site, sit together in the same room/space

Team members (programmers/testers etc.) collaborate with customers if needed

On the wall task board (with post-it notes) is being used to communicate progress in a sprint

A tool (like VersionOne, Jira etc.) is being used to communicate progress in a sprint

Other, please specify:

12.Which of the following, applies to the location of the Scrum (Agile) teams in your company?

All the teams are located at one site

All the teams are distributed to more than one site

Some teams are located at one site, others are distributed

Other, please specify:

13.Please name at least three things you believe to be positive effects of the Scrum (Agile) development process practice in your company and if it applies, please compare with parallel/prior development process:

14.Please tell about the things in relation to the Scrum (Agile) development process practice in your company, that you believe needs to be improved:

15.Are you using any standards accompanying the Scrum (Agile) development process? If so, what standards? (E.g. CMMI, ITIL, IEEEx, ISOxxx, etc.)

Software testing in relation to the Scrum (Agile) development process (1)

Since the usage of terminology used in the questions below may vary, a short definition of each type of software testing is given at the bottom of the page, mostly as defined by ISTQB (International Software Testing Qualification Board).

16.To which extent are the following types of software testing done in Scrum (Agile) projects? Each type may be done by your Scrum (Agile) team members (company internal) and/or customers (company external), see next question.

	5 - Yes, a lot	4 - Yes, some	3 - So and so	2 - Little	1 - No, not at all
Unit/component testing	5 - Yes, a lot	4 - Yes, some	3 - So and so	2 - Little	1 - No, not at all

Integration testing	5 - Yes, a lot	4 - Yes, some	3 - So and so	2 - Little	1 - No, not at all

System testing	5 - Yes, a lot	4 - Yes, some	3 - So and so	2 - Little	1 - No, not at all

Acceptance testing	5 - Yes, a lot	4 - Yes, some	3 - So and so	2 - Little	1 - No, not at all

Usability testing	5 - Yes, a lot	4 - Yes, some	3 - So and so	2 - Little	1 - No, not at all

Alpha testing	5 - Yes, a lot	4 - Yes, some	3 - So and so	2 - Little	1 - No, not at all

Beta testing	5 - Yes, a lot	4 - Yes, some	3 - So and so	2 - Little	1 - No, not at all

Performance/load testing	5 - Yes, a lot	4 - Yes, some	3 - So and so	2 - Little	1 - No, not at all

Security testing	5 - Yes, a lot	4 - Yes, some	3 - So and so	2 - Little	1 - No, not at all

17.If the the following types of software testing are done internally and/or externally, who performs each type in Scrum (Agile) projects? Please regard roles mentioned as individual's primary role on the Scrum (Agile) teams.

	Programmer	Software Tester	External Software Tester	Customers	Others
Unit/component testing	Programmer	Software Tester	External Software Tester	Customers	Others

Integration testing	Programmer	Software Tester	External Software Tester	Customers	Others

System testing	Programmer	Software Tester	External Software Tester	Customers	Others

Acceptance testing	Programmer	Software Tester	External Software Tester	Customers	Others

Usability testing	Programmer	Software Tester	External Software Tester	Customers	Others

Alpha testing	Programmer	Software Tester	External Software Tester	Customers	Others

Beta testing	Programmer	Software Tester	External Software Tester	Customers	Others

Performance/load testing	Programmer	Software Tester	External Software Tester	Customers	Others

Security testing	Programmer	Software Tester	External Software Tester	Customers	Others

18.In the last two questions above, did you miss any kind of software testing? If any, which one? To which extent are you using it as in Q16 and who is performing it as in Q17? Note that you may be using different terminology for types of software testing, please feel free to explain here:

Unit/component testing: The testing of individual software components.

Integration testing: Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.

System testing: The process of testing an integrated system to verify that it meets specified requirements. This type includes test design techniques like boundary value analysis and is usually done by internal software testers.

Acceptance testing: Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the users, customers or other authorized entity to determine whether or not to accept the system.

Usability testing: Testing to determine the extent to which the software product is understood, easy to learn, easy to operate and attractive to the users under specified conditions.

Alpha testing: Simulated or actual operational testing by potential users/customers or an independent test team at the developers' site, but outside the development organization. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing.

Beta testing: Operational testing by potential and/or existing users/customers at an external site not otherwise involved with the developers, to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes. Beta testing is often employed as a form of external acceptance testing for off-the-shelf software in order to acquire feedback from the market.

Performance/load testing: The process of testing to determine the performance and/or measuring the behavior of a component or system with increasing load, e.g. the number of parallel users and/or numbers of transactions, to determine what load can be handled by the component or system.

Security testing: Testing to determine the security of the software product.

Software testing in relation to the Scrum (Agile) development process (2)

19.If you are using some types of software testing less than others in Scrum (Agile) projects, what is the main reason?

	Lack of budget	Lack of time	Lack of training/knowledge	Other	Not applicable
Unit/component testing	Lack of budget	Lack of time	Lack of training/knowledge	Other	Not applicable

Integration testing	Lack of budget	Lack of time	Lack of training/knowledge	Other	Not applicable

System testing	Lack of budget	Lack of time	Lack of training/knowledge	Other	Not applicable

Acceptance testing	Lack of budget	Lack of time	Lack of training/knowledge	Other	Not applicable

Usability testing	Lack of budget	Lack of time	Lack of training/knowledge	Other	Not applicable

Alpha testing	Lack of budget	Lack of time	Lack of training/knowledge	Other	Not applicable

Beta testing	Lack of budget	Lack of time	Lack of training/knowledge	Other	Not applicable

Performance/load testing	Lack of budget	Lack of time	Lack of training/knowledge	Other	Not applicable

Security testing	Lack of budget	Lack of time	Lack of training/knowledge	Other	Not applicable

20.If you have a comparison to any parallel/prior development process, what would you say about the change in software testing practices in the Scrum (Agile) projects?

Software testing became easier

Overall more software testing is done

Overall less software testing is done

Programmers started using more test-driven development/design (TDD)

Software Testers became more involved throughout the whole development

Regression testing became automated

Other, please specify:

21.Which of the following items applies to software testing practice within the Scrum (Agile) projects in your company?

Software testing falls within the frame of "done" in each sprint

Software testing is squeezed into the end of each iteration (each sprint is a mini-waterfall)

Software testing is not well integrated with coding and ends up one sprint behind

Software testing is performed in a separate test environment

Good management of version control (easy to know which build is being deployed)

Before a major version release, there is a bug-fix sprint

Other, please specify:

Further background information

22.What is the level of your education?

PhD

MSc

BSc

University diploma (1 - 2 years study)

Self educated

Other, please specify:

23.What is the field of your education?

Computer Science

Engineering

Other, please specify:

24.What is your gender?

Male

Female

25.I would like to conduct interviews with a few of the survey respondents. Would you be willing to take part in such an interview? If so please leave your e-mail address in the field below. Information about individuals and companies will be confidential.

26.Do you have any comments/suggestions on the survey, if so could you please leave them here:

use this free template

Analysis of Software Testing in Icelandic Scrum Pr

Background information (1)

Background information (2)

Details on Scrum or similar Agile development process

Software testing in relation to the Scrum (Agile) development process (1)

Software testing in relation to the Scrum (Agile) development process (2)

Further background information

Related templates and questionnaires

QuestionPro in your language

Awards & certificates

The Experience Journal