Is lean agile and agile lean? A comparison between two software development paradigms

Modern Software Engineering Concepts and Practices: Advanced Approaches

Volumn , Issue , 2010, Pages 19-46

  Petersen, Kai ^a  

^a ERICSSON RESEARCH   (Sweden)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84898571696     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.4018/978-1-60960-215-4.ch002     Document Type: Chapter

References (31)

1. Andersen, B., & Fagerhaug, T. (2000). Root cause analysis: Simplified tools and techniques. Milwaukee: ASQ Quality.
2. Anderson, D. (2003). Agile management for software engineering: Applying the theory of constraints for business results. Prentice Hall.
3. Beck, K. (2000). Extreme Programming explained: Embrace change. Reading, MA: Addison-Wesley.
4. Beck, K. (2003). Test-driven development: By example. Boston: Addison-Wesley.
5. Beck, K. (2004). JUnit pocket guide. Sebastopol, CA: O'Reilly.
6. Beck, K., et al. (2001). Manifesto for agile software development. Retrieved from http://agilemanifesto.org
7. Beecham, S., Baddoo, N., Hall, T., Robinson, H., & Sharp, H. (2008). Motivation in software engineering: A systematic literature review. Information and Software Technology, 50(9-10), 860-878. doi:10.1016/j.infsof.2007.09.004
8. Biffl, S., & Aurum, B. B. A. (2005). Value-based software engineering. New York: Springer.
9. DeMarco, T., & Lister, T. (1999). Peopleware: Productive projects and teams. New York: Dorset House Publishing.
10. Dybå, T., & Dingsøyr, T. (2008). Empirical studies of agile software development: A systematic review. Information and Software Technology, 50(910), 833-859. doi:10.1016/j.infsof.2008.01.006
11. Fagan, M. E. (1976). Design and code inspections to reduce errors in program development. IBM Systems Journal, 15(3), 182-211. doi:10.1147/sj.153.0182
12. th International Conference on Software Engineering (ICSE 2005), (p. 38).
13. Höst, M., & Regnell, B., och Dag, J. N., Nedstam, J. & Nyberg, C. (2001). Exploring bottlenecks in market-driven requirements management processes with discrete event simulation. Journal of Systems and Software, 59(3), 323-332. doi:10.1016/S0164-1212(01)00072-3
14. Karlsson, C., & Ahlström, P. (2009). The difficult path to lean product development. Journal of Product Innovation Management, 13(4), 283-295. doi:10.1016/S0737-6782(96)00033-1
15. Kerievsky, J. (2005). Refactoring to patterns. Boston: Addison-Wesley.
16. Koch, A. S. (2005). Agile software development: Evaluating the methods for your organization. Boston: Artech House.
17. Larman, C. (2004). Agile and iterative development: A manager's guide. Boston: AddisonWesley.
18. Leon, A. (2005). Software configuration management handbook. Boston: Artech House.
19. Morgan, J. M., & Liker, J. K. (2006). The Toyota product development system: Integrating people, process, and technology. New York: Productivity Press.
20. 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. Journal of Systems and Software, 82(9), 1479-1490. doi:10.1016/j.jss.2009.03.036
21. Petersen, K. & Wohlin, C. (2010). Software process improvement through the lean measurement (SPI-LEAM) method. Journal of Systems and Software.
22. Petersen, K., Wohlin, C., & Baca, D. (2009). The waterfall model in large-scale development. In proceedings of the International Conference on Product-Focused Software Process Improvement (PROFES 2009), (pp 386-400).
23. Poppendieck, M., & Poppendieck, T. (2003). Lean software development: An agile toolkit. Boston: Addison-Wesley.
24. Poppendieck, M., & Poppendieck, T. (2007). Implementing lean software development: From concept to cash. Boston: Addison-Wesley.
25. Poppendieck, M., & Poppendieck, T. (2009). Leading lean software development. Boston: Addison-Wesley.
26. Royce, W. (2009). Managing the development of large software systems: Concepts and techniques. In Proceedings IEEE WESCOM. IEEE Computer Society.
27. Schwaber, K. (2004). Agile project management with Scrum. Redmond, WA: Microsoft Press.
28. Mujtaba, S., Feldt, R. & Petersen, K. (2010). Waste and lead time reduction in a software product customization process with value stream maps. Proceedings of the Australian Software Engineering Conference (ASWEC 2010).
29. Sun Microsystems. (1999). Java code conventions. Retrieved from http://java.sun.com/docs/codeconv/
30. Weinberg, G. M. (1999). Egoless programming. IEEE Software, 16(1). doi:10.1109/MS.1999.744582
31. Womack, J. P. (2007). The machine that changed the world. London: Simon & Schuster.