Software developer motivation in a high maturity company: A case study

Software Process Improvement and Practice

Volumn 11, Issue 3, 2006, Pages 219-228

  Baddoo, Nathan ^a   Hall, Tracy ^a   Jagielska, Dorota ^a  

^a UNIVERSITY OF HERTFORDSHIRE   (United Kingdom)

Author keywords

Motivation; Performance; Project outcomes; Software developer

Indexed keywords

DATA ACQUISITION; KNOWLEDGE ACQUISITION; MOTIVATION; PROBLEM SOLVING; PROJECT MANAGEMENT; QUALITY OF SERVICE; SOFTWARE ENGINEERING;

INTERPERSONAL SKILLS; PRODUCT QUALITY; PROJECT OUTCOMES; SENIOR MANAGEMENT SUPPORT; SOFTWARE DEVELOPER;

COMPUTER SOFTWARE;

EID: 33745790492     PISSN: 10774866     EISSN: 10991670     Source Type: Journal    
DOI: 10.1002/spip.265     Document Type: Conference Paper

References (28)

1. Ahuja S. 1999. Process improvement in a rapidly changing business and technical environment. In Fourth Annual European Process Group Conference. Amsterdam, NY, Holland, c303.
2. Baddoo N. 2001. Motivators and de-motivators in software process improvement: An empirical study. In Faculty of Engineering and Information Sciences. University of Hertfordshire: Hatfield, 259.
3. Baddoo N, Hall T. 2002. Motivators of software process improvement: An analysis of practitioners' views. Journal of Systems and Software 62(2): 85-96.
4. Baddoo N, Hall T. 2003. De-motivators of software process improvement: an analysis of practitioners' views. Journal of Systems and Software 66(1): 23-33.
5. Baccarini D. 1999. The logical framework method for defining project success. Project Management Journal 30(4): 25-32.
6. Berdie DR, Anderson JF. 1974. Questionnaires: Design and Use. The Scarecrow Press: Metuchen, NJ.
7. Black TR. 1999. Doing Quantitative Research In The Social Sciences: An Integrated Approach To Research Design, Measurement And Statistics. Sage Publications.
8. Boehm B, Papaccio P. 1988. Understanding and controlling software costs. Ieee Transactions on Software Engineering 14(10): 1462-1477.
9. Couger JD. 1988. Motivators and demotivators in the is environment. Journal of Systems Management 39(6): 36-41.
10. Couger JD, Adelsberger H. 1988. Comparing motivation of programmers and analysts in different socio/political environments: Austria compared to the United States. Computer-Personnel 11(4): 13-16.
11. Couger JD, O'Callaghan R. 1994. Comparing the motivators of Spanish and finish computer personnel with those of the United States. European Journal of Information Systems 3(4): 258-291.
12. Diaz M, Sligo J. 1997. How software process improvement helped motorola. IEEE Software 14(5): 75-81.
13. Fitz-Enz J. 1978. Who is the DP professional? Datamation 24(9): 125-128.
14. Hall T, Wilson D. 1997. Views of software quality: a field report. IEE Proceedings - Software 144(2): 111-118.
15. Jones C. 1995. Patterns of large software systems: failure and success. IEEE Computer 28(3): 86-87.
16. Kaltio T, Kinnula A. 2000. Deploying the defined software process. Software Process: Improvement and Practice 5: 65-83.
17. Likert R. 1932. A technique for the measurement of attitudes. Archives of Psychology 140(22): 55.
18. Linberg K. 1999. Software developer perceptions about software project failure: a case study, The. Journal of Systems and Software 49:177-192.
19. Mata Toledo RA, Unger EA. 1985. Another look at motivating data processing professionals. Computer-Personnel 10(1): 1-7.
20. McDermit JA, Bennett KH. 1999. Software engineering research: A critical appraisal. IEE Process on Software Engineering 146(4): 179-186.
21. Mellis W. 1998. Software quality management in turbulent times-are there alternatives to process oriented software quality management? Software Quality Journal 7: 277-295.
22. Pitterman B. 2000. Telcordia technologies: The journey to high maturity. IEEE Software 17(4): 89-96.
23. Procaccino JD, Verner JM, Shelfer KM, Gefen D. 2005. What do software practitioners really think about project success: an exploratory study. Journal of Systems and Software 78(2): 19-38.
24. Turley RT, Bieman JM. 1995. Competencies of exceptional and nonexceptional software engineers. Journal of Systems and Software 28(1): 19-38.
25. Warden R, Nicholson I.1995. IT quality initiatives at risk. Software Quality Management 1(24): 24-27.
26. Willis RR, Rova RM, Scott MD, Johnson MI, Ryskowski JF, Moon JA, Shumate KC, Winfield TO. 1998. Hughes aircraft's widespread deployment of a continuously improving software process. In Software Engineering Institute. Canergie Mellon University: Pittsburgh, Pennsylvania, USA.
27. Wilson D, Hall T. 1998. Perceptions of software quality: a pilot study. Software Quality Journal 7(1): 67-75.
28. Wilson D, Hall T, Baddoo N. 2000. The software process improvement paradox. Approaches to Quality Management: Software Quality Management VIII 97-101.