Waste identification and elimination in information technology organizations

Empirical Software Engineering

Volumn 19, Issue 6, 2014, Pages 2019-2061

  Al Baik, Osama ^a   Miller, James ^a  

^a UNIVERSITY OF ALBERTA   (Canada)

Author keywords

Agile; Lean production; Lean software development; Lean thinking; Software process improvement; Waste in IT

Indexed keywords

CUSTOMER SATISFACTION; KNOWLEDGE BASED SYSTEMS; LEAN PRODUCTION;

AGILE; BUSINESS PROCESS; IT ORGANIZATIONS; KNOWLEDGE BASED; LEAN SOFTWARE DEVELOPMENT; LEAN THINKING; SOFTWARE PROCESS IMPROVEMENT; WASTE ELIMINATIONS;

SOFTWARE DESIGN;

EID: 84910012247     PISSN: 13823256     EISSN: 15737616     Source Type: Journal    
DOI: 10.1007/s10664-014-9302-3     Document Type: Article

References (58)

1. Addy R (2007) Effective IT service management: to ITIL and beyond! Springer-Verlag Berlin Heidelberg, New York
2. Ammerman M (1998) The root cause analysis handbook: a simplified approach to identifying, correcting, and reporting workplace errors. Productivity, Inc., Portland
3. Argyris C (2004) Reasons And Rationalizations: The Limits to Organizational Knowledge. Oxford University Press
4. Bellingham R (2004) HR optimization: from personnel administration to human and organizational capital development. HRD Press, Inc., Massachusetts
5. Besterfield DH (2009) Quality control. Pearson Prentice Hall, New Jersy
6. Bhagat RS, Steers RM (2009) Cambridge handbook of culture, organizations, and work. Cambridge University Press, New York
7. Boeg J (2011) Priming kanban: a 10 step guide to optimizing flow in your software delivery system. Chronografisk, Denmark
8. DeMarco T (2011) All late projects are the same. IEEE Softw 28(6):103–104
9. Dennis P (2007) Lean production simplified. Productivity Press, New York
10. de-Ste-Croix A, & Easton A (2008) The Product Owner Team. Agile ‘08 Conference (pp. 274–279). IEEE
11. Dittrich Y, Rönkkö K, Eriksson J, Hansson C, Lindeberg O (2008) Cooperative method development. Empir Softw Eng 13(3):231–260
12. Easterbrook S, Singer J, Storey M-A & Damian D (2008) Selecting Empirical Methods for Software Engineering Research. In Guide to Advanced Empirical Software Engineering (pp. 285-311). Springer London
13. Goldratt EM, Cox J (1992) The goal: a process of ongoing improvement. North River Press, Massachusetts
14. Harvard Business Review (2011) Management tips. Harvard Business Press, Massachusetts
15. Hino S (2002) Inside the mind of Toyota. Productivity Press, New York
16. Humble J, Farley D (2011) Contiinuous delivery. Addison-Wesley, New Jersey
17. International Institute of Business Analysis (2009) A Guide to the Business Analysis Body of Knowledge (BABOK)
18. Jaisingh S (2012) Lean manufacturing [class handout]. department of mechanical engineering, University of Alberta. Edmonton, Canada
19. Kim H, Pries J (2011) Testing complex and embedded systems. CRC Press, New York
20. Liker JK, Hoseus M (2008) Toyota culture: the heart and sould of the Toyota Way. McGraw-Hill, New York
21. Magee D (2008) How Toyota became #1. Penguin Group, New York
22. Martin A, Biddle R & Noble J (2009) XP Customer Practices: A Grounded Theory. Agile Conference, AGILE ‘09. (pp. 33–40). IEEE
23. McConnell S (1996) Rapid development: taming wild software schedules. Microsoft Press, Washington
24. McGovern J, Shelly S (2008) The happy employee: 101 ways for managers to attract, retain, & inspire the best and brightest. Adams Business, Massachusetts
25. Middleton P (2012) Lean software management: BBC worldwide case study. IEEE Trans Eng Manag 59(1):20–32
26. Morgan JM & Liker JK (2006) The Toyota Product Development System: Integrating People, Process, and Technology. Productivity Press
27. Murugaiah U, Benjamin SJ, Marathamuthu MS, Muthaiyah S (2010) Scrap loss reduction using the 5-whys analysis. Int J Qual Reliability Manag 27(5):27–540
28. Nottonson K (2011) Yahoo! sports: sprint 100 & beyond. agile conference (pp. 252–255). IEEE
29. OhnoT (1988) Toyota production system: beyond large-scale production. Productivity Press
30. Packlick J (2007) The agile maturity map a goal oriented approach to agile improvement. agile conference 2006 (pp. 266–271). IEEE
31. Petersen K, Wohlin C (2009) A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case. J Syst Softw 82(9):1479–1490
32. Petersen K, Wohlin C (2010) Software process improvement through the lean measurement (SPI-LEAM) method. J Syst Softw 83(7):1275–1287
33. Poppendieck M & Poppendieck T (2003) Lean software development: an agile toolkit. Addison Wesley
34. Poppendieck, M & Poppendieck T (2006) Implementing lean software development: from concept to cash. Addison Wesley
35. Programmers Forum (2012) What is the difference between requirements and specifications? Retrieved October 20, 2012, from http://programmers.stackexchange.com/questions/121289/what-is-the-difference-between-requirements-and-specifications
36. Project Management Institute (2008) A guide to the project management body of knowledge (PMBOK guide). USA, Philadelphia
37. Przekop P (2006) Six sigma for business excellence: a Manager’s guide to supervising six sigma projects and teams. McGraw-Hill, New York
38. Rand C & Eckfeldt B (2004) Aligning strategic planning with agile development: extending agile thinking to business improvement. agile development conference, (pp. 78–82)
39. Runeson P, Höst M (2009) Guidelines for conducting and reporting case study research in software engineering. Empir Softw Eng 14(2):131–164
40. Schyff A (2011) Lean software development
41. Schwaber K, Sutherland J (2012) Software in 30 days: how agile managers beat the odds, delight their customers, and leave competitors in the dust. Wiley, NJ
42. Shah R, Ward PT (2007) Defining and developing measures of lean production. J Oper Manag 25(4):785–805
43. Shelton C (2010) Business process reengineering with commercial off-the-shelf software. department of defense, department of the air force Washington DC. Defense AT&L, Washington
44. Singer J, Sim SE, Lethbridge TC (2008) Software engineering data collection for field studie. In: Singer J, Sim SE, Lethbridge TC, Shull F, Singer J, Sjøberg DI (eds) Guide to advanced empirical software engineering. Springer, London, pp 9–34
45. Spearman WJ (2004) To pull or not to pull: what is the question? Manuf Serv Oper Manag 6(2):133–148
46. Staats BR, & Upton DM (2011) Lean knowledge work. Harvard business review
47. Staats BR, Brunner DJ, Upton DM (2011b) Lean principles, learning, and knowledge work: evidence from a software services provider. J Oper Manag 29(5):376–390
48. Stober T, Hansmann U (2010) Agile software development: best practices for large software development projects. Springer-Verlag Berlin Heidelberg, New York
49. Tapping DT (2002) Value stream managemenet: eight steps to planning, mapping, and sustaining lean improvements. Productivity Press, New York
50. Walsh R (2008) Time management: proven techniques for making every minute count. Adams Media, MA
51. Wang X, Conboy K, Cawley O (2012) “Leagile” software development: an experience report analysis of the application of lean approaches in agile software development. J Syst Softw 85(6):1287–1299
52. Waterhouse P (2008) Improving IT economics: Thinking ‘Lean’. CA White Paper
53. Watkins J (2009) Agile testing: How to succeed in an extreme testing environment. Cambridge University Press, New York
54. Watkins J, Mills S (2011) Testing IT: an Off-the-shelf software testing process, 2nd edn. Cambridge University Press, New York
55. Womack JP (2007) The machine that changed the world. Free Press, New York
56. Xingjian Y (1992) A database design method for finite element analysis. Comput & Struct 44(4):911–914
57. Yap M (2006) Value-based extreme programming. Agile conference (pp. 175–184). IEEE
58. Younker J (2008) Foundations of agile python development. Apress