Page 107 -

92 DUBINSKY, HAZZAN, TALBY, AND KEREN
APPENDIX 6.1. SOFTWARE DEVELOPMENT CULTURE QUESTIONNAIRE

For each of the following, please mark + in the appropriate column according to your agreement
with the statement.
Tend to Tend to
Statement Agree agree disagree Disagree
It is important to me that development tasks are
allocated equally among team members.
It is preferable to develop software by planning at the
design level, not at the development task level.
It is accepted in the software industry that developers
who frequently go home at 5 p.m. do not invest
enough effort at work.
It is preferable to minimize, as much as possible, the
dependency level among software team members.
Customers expect that software development will not
be completed on time, thus, it is reasonable to commit
to an unreasonable timetable.
The Israeli hi-tech industry is characterized by
unplanned software development.
It is preferable to work in small teams in order to foster
decision-making processes as much as possible.
Single-release software development is preferable to a
gradual development process consisting of several releases.
It is important to enable software developers to work flexible
hours (“come when you want, leave when you want”).
If a software project does not proceed as planned, the
team must work nights and weekends to catch up.
No one on my team cares about how the software is
written as long as it works.
A team should extend the development period if it
ensures improvement of software quality.
When I chose a profession, I took into consideration
that I would have to devote many hours every day to
work and give up my personal life.
It is better not to estimate development periods a
priori since software development is characterized by
unexpected problems.
During software development, it is preferable to invest
in code readability in order to help future developers
whose job will be to maintain the software.
If software development does not proceed according to
the planned schedule, the schedule should be replanned.
Intuition and improvisation are important in software
development processes.
It is not important to integrate a reflective process
(analysis of the past and learning of lessons) into the
software development process.
When it is difficult to check software, it is okay to move
forward and not to insist on testing.
There is a tendency on my team not to take personal
responsibility.
My team tends to adhere to the timetable.
Even if I see an opportunity to shorten the development
period by skipping tests, I will not take it.
My team tends to build tight timetables (sometimes by
compromising the software quality).