Information systems project management: an agency theory interpretation
Journal of Systems and Software
Software Effort, Quality, and Cycle Time: A Study of CMM Level 5 Projects
IEEE Transactions on Software Engineering
The effects of change control and management review on software flexibility and project performance
Information and Management
Investigating the relationship between schedules and knowledge transfer in software testing
Information and Software Technology
Achieving it consultant objectives through client project success
Information and Management
Proceedings of the the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
A demands-resources model of work pressure in IT student task groups
Computers & Education
Journal of Systems and Software
Proceedings of the 33rd International Conference on Software Engineering
Reliability, mindfulness, and information systems
MIS Quarterly
Electronic Commerce Research and Applications
Technostress: technological antecedents and implications
MIS Quarterly
Case study: Service quality from the other side: Information systems management at Duquesne Light
International Journal of Information Management: The Journal for Information Professionals
International Journal of Human Capital and Information Technology Professionals
Information Technology as a Target and Shield in the Post 9/11 Environment
Information Resources Management Journal
More testers - The effect of crowd size and time restriction in software testing
Information and Software Technology
Global software testing under deadline pressure: Vendor-side experiences
Information and Software Technology
Organizing knowledge workforce for specified iterative software development tasks
Decision Support Systems
| Hi-index | 0.00 |
An agency framework is used to model the behavior of software developers as they weigh concerns about product quality against concerns about missing individual task deadlines. Developers who care about quality but fear the career impact of missed deadlines may take "shortcuts." Managers sometimes attempt to reduce this risk via their deadline-setting policies; a common method involves adding slack to best estimates when setting deadlines to partially alleviate the time pressures believed to encourage shortcut-taking. This paper derives a formal relationship between deadline-setting policies and software product quality. It shows that: (1) adding slack does not always preserve quality, thus, systematically adding slack is an incomplete policy for minimizing costs; (2) costs can be minimized by adopting policies that permit estimates of completion dates and deadlines that are different and; (3) contrary to casual intuition, shortcut-taking can be eliminated by setting deadlines aggressively, thereby maintaining or even increasing the time pressures under which developers work.