The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I filled in the survey, so beware your stats are going to be skewed.
A few comments:
Do you use code reviews or have used it previously?
There is no option for "I have introduced code reviews" which is what happened here.
What is the main business of your team?
What do you mean by "standard software?"
How is the software development process in your team done?
Agile software development process (software development takes place with few rules, mostly iterative and with little bureaucratic effort).
Your definition of Agile is amusing.
Is your team striving towards short-term or long-term success of the product?
What the heck does that mean? Why would anyone choose short-term success?
Have you made personal experiences to negative effects of code reviews?
Awkward working -- "have you had negative experiences with code reviews?" perhaps is better.
What is the handling of errors (such as mistakes in planning or thinking) in your team?
Consider: "How are errors handled by your team?"
Supervisors pass on guilt of their own mistakes to other employees.
I think you mean "Supervisors blame other employees for the supervisor's mistakes" ???
Some general comments:
When my gf did her masters thesis in psychology, she did a survey on nutrition. Doing a survey is part science, part art. It's important to ask a question both in the positive and in the negative, for example: "Do you consider yourself skilled at writing surveys" and later on, another question "Is writing surveys one of your weaker points." It's really hard to come up with a good balance of positive and negative questions, and to ensure if the negative questions are truly the opposite.
Some things I'm surprised you didn't ask, such as some statistics about the survey taker -- their age, # of years of experience in their field, perhaps even what their field is, and what their favorite programming language and OS is. It would be fascinating to cross-reference the answers with language/OS skills.
Anyways, I'd be interested in seeing the results, but having helped my gf put together a survey that had some hope in hell of being statistically meaningful, which of course also had a lot of involvement with her adviser and her learning some of the fundamentals of statistical analysis, I (apologies in advance) really think your survey needs some fine tuning.
Wow, thanks for your long post . When you already have started a survey it's very uncommon to edit some points, so that all participants have the same questions. i will try to consider your points in the analysis. In general it's hard to consider all cases when it's comes to creating answers, that's a reason why i wrote: You should always select the answer which applies to you the most.
in detail: 1.)your case should be: 'Code reviews are currently used.' 2.)main business/standard software: if you are developing software which can buy everyone 3.)There are different definitions on agile, it could be a better one. First i wrote it without a description, but also can't be a solution. 4.)There are projects with a short-term success. There are already answers which confirm this
and the english: like in this post you can see my english isn't that good, but i checked it with an UK friend. Maybe he does'nt saw the faults..