Thanks in advance for taking time to read and complete this survey.

Objective: This data will be used for my research paper at Monmouth University. Please forward this to other credidble friends or colleagues that may be interested.

Disclaimer: Only the data entered in the form will be recorded, saved, and reused. Other common traffic data (i.e. IP Address, etc) may be collected by ISP, DNS Registrar, or other site hosting vendors, but will not be associated with any data submitted in this survey.

The last date that I will collect data is at end of day Sunday, 12/13/2009. All data up to that point will be used. All data afterwards will be continued to be collected and may be checked periodically.

 

Survey - Lying in Software Projects

This survey should take about 5-10 minutes of your time. The second half is optional, but any feedback would be much appreciated.

For the purpose of this survey, distorting the truth means to manipulate information, data, or features due to external factors not directly related to the task. For example, if a project leader tells a superior that a project is on schedule when it is not, then project leader distorted the truth. If the project leader estimates higher due to poor resources, then the project leader did not distort the truth.

 

Years of experience  
CurrentTitle    
Background Information  (anything to do with software projects that you think would be relevant)

Approximate number of projects you've participated on  


Please answer the following in increments of 10% (i.e. 0%, 10%, 20%, ..., 100%). The answer is the percentage of projects that you know some form of lying occurred.

Estimation
(e.g. estimating lower time/cost knowing that they cannot complete within time/cost budget, estimating higher for more profit, lighter workload, or compensate for other poor estimates, etc.)
% of projects where someone is intentionally distorting the truth
Distorting the truth to management
Distorting the truth to project lead
Distorting the truth to developer
Distorting the truth to customer/user
Distorting the truth to other departments
Estimation is unreasonably high (e.g. padded for profit)
Estimation is unreasonably low (e.g. to win bids)

Status Reporting
(e.g. on schedule but is behind schedule to cover underperformance, on schedule but ahead of schedule to maintain budget buffer, work completed but is not, etc.)
% of projects where someone is intentionally distorting the truth
Distorting the truth to management
Distorting the truth to project lead
Distorting the truth to developer
Distorting the truth to customer/user
Distorting the truth to other departments
Overly optimistic
Overly pessimistic
   


Political Maneuvering
(e.g. taking credit for others work, say what the superior wants to hear, hiding errors or underperformance, etc.)
% of projects where someone is intentionally distorting the truth for political maneuvering (e.g. self-promotion, shifting credit, blaming scape goats, etc.)
Distorting the truth to management
Distorting the truth to project lead
Distorting the truth to developer
Distorting the truth to customer/user
Distorting the truth to other departments
To cover up underperformance
For personal gain


Hype
(e.g. embellishing features to sell the product, marketing features that do not exist, etc.)
% of projects where someone is intentionally distorting the truth to manipulate hype
Distorting the truth to management
Distorting the truth to project lead
Distorting the truth to developer
Distorting the truth to customer/user
Distorting the truth to other departments



[OPTIONAL]
What are your thoughts on the motivation/cause of distorting the truth in software projects?
Estimation

Status Report

Political Maneuvering

Hype




What are your thoughts to solve or minimize lying in software projects?
Estimation


Status Report

Political Maneuvering

Hype



Have you already implemented changes? Did it work? Did it not work? Any new concerns?


Any suggestions to improve this survey?


Other thoughts?




Thanks!