Abstract
Agile and lean approaches are disruptive approaches for the established software development approaches. Furthermore agile approaches are going step by step out of the software area into other areas like individual services outside the production, which is the root of lean. In this work we present an overview and outlook about agile and lean approaches to help to find answers to some questions: What is the difference between agile and lean? What kind of continuos improvement is inherent in agile and lean? How can lean and agile approaches be combined with software process improvement approach?
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
The term procedure is used instead of process because the ISO 9000:2015 defines procedures as optional documented to emphasis the more formal character. This makes the term procedure more adequate for agile teams because many teams do not focus on too much consolidation and reinforcement of processes to be able to change them easier if needed.
- 2.
The value chain is a core business procedure to make money. In agile environments, teams are organized around a value chain in independent teams to deliver entire functions to the value chain. In a web-shop a value chain could be “search product”, “put it on the shopping card”, “check out/buy” depending on complexity additional functions like “manage customer profile” etc. are also individual function teams instead of be part of check out “shipping address fields”.
- 3.
Self-organized teams are setup and organized to act business centric and autonomy. They are empowered with their comprehensive know how to decide and act self-organized and independent from other teams – for fast reaction on incidents etc.
- 4.
Feature or function teams are agile teams to handle a business functionality. Focus is to bring all relevant know how to run a “part” of business in an end-to-end fashion in the team. This is orthogonal to many IT setting with stacking teams in for example 3-tier applications in a frontend, business logic-and database-team to group specialists into competence teams.
.
- 5.
Transition: The way from the status quo to an ideal agile organization is often called transition or agile transition. By definition, a transition never ends because something is always to optimize to have a better agile organization.
References
Ishikawa, K.: What is Total Quality Control? The Japanese Way. Prentice Hall, Upper Saddle River (1988)
[SQU07] The SQuBOK Project Team, SQuBOK (Software Quality Body of Knowledge) Guide, Version 1, 42 (2007). (in Japanese)
The TQM Committee: Total “Quality” Management in the 21st century. JUSE Press (1998). (in Japanese)
Ohno, T.: Toyota Production System: Beyond Large-Scale. Productivity Press (1988). ISBN: 978-0915299140
Goldratt, E.M., Cox, J.: The Goal: A Process of Ongoing Improvement. North River Press, Great Barrington (1992)
Womack, J.P., Jones, D.T., Roos, D.: The Machine That Changed the World: The Story of Lean Production. Harper Collins, New York City (1991)
Womack, J.P., Jones, D.T.: Lean Thinking. Simon & Schuster, New York City (1996)
Takeuchi, H., Nonaka, I.: The New New Product Development Game. Harvard Business Review, January–February 1986
Beck, K.: Extreme Programming Explained: Embrace Change. Addison-Wesley, Boston (1999)
Sutherland, J.: Scrum: The Art of Doing Twice the Work in Half the Time. Crown Business, New York (2014). ISBN: 978-0385346450
Sutherland, J.: SCRUM Development Process 10th Annual Conference on Object-Oriented Programming Systems, Languages, and Applications Addendum to the Proceedings. OOPS Messenger 6:4, pp. 170–175. ACM/SIGPLAN, October 1995
Anderson, D.J.: Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results. Prentice Hall, Upper Saddle River (2003)
Anderson, D.J., Reinertsen, D.G., Kanban: Successful Evolutionary Change for Your Technology Business. Blue Hole Press (2010). ISBN: 978-0984521401
Poppendieck, M., Poppendieck, T.: Lean Software Development: An Agile Toolkit. Addison-Wesley, Boston (2003)
Senge, P.: The Fifth Discipline: The Art and Practice of the Learning Organization. Currency – Doubleday, New York (1990). ISBN: 0-385-51725-4
The Agile Manifesto (2001). https://www.agilealliance.org/agile101/the-agile-manifesto/
Plattner, H., et al.: Design Thinking: Understand, Improve. Apply. Springer, Heidelberg (2010)
Ries, E.: The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Crown Business, New York (2011). ISBN: 978-0-307-88789-4
Ladas, C.: Scrumban: Essays on Kanban Systems for Lean Software Development. Modus Cooperandi Press (2009). ISBN: 978-0578002149
Larman, C., Vodde, B.: Large-Scale Scrum: More with LeSS, 1st edn. Addison-Wesley Professional, Boston, 20 August 2016. ISBN: 978-0321985712
http://www.scrummingman.com/2014/09/scrum-retrospective-technique-mood-chart/
ISO IS 15504
CMMI Dev V1.3. http://www.sei.cmu.edu/reports/10tr033.pdf
Conway, M.E.: How do committees invent? Datamation 14(5), 28–31 (1968)
Poth, A.: Sunyaev. Effective quality management: value- and risk-based software quality management. IEEE Softw. 31(6), 79–85 (2014)
Beck, D.E., Cowan, C.: Spiral Dynamics: Mastering Values, Leadership and Change. Wiley-Blackwell, Hoboken (2005). ISBN: 978-1-4051-3356-2
Drobietz, M., Poth, A.: A new approach: not agile vs. traditional QM but applying the best of both. In: Stolfa, J., Stolfa, S., O’Connor, R.V., Messnarz, R. (eds.) EuroSPI, pp. 486–494. Springer, Heidelberg (2017)
Poth, A., Wolf, F.: Agile Procedures of an automotive OEM – views from different business areas. In: euroSPI (2017)
Doss, O., Kelly, T., Stålhane, T., Haugset, B., Dixon, M.: Integration of the 4+1 Software Safety Assurance principles with Scrum. In: Stolfa, J., Stolfa, S., O’Connor, R.V., Messnarz, R. (eds.) EuroSPI, pp. 72–82. Springer, Heidelberg (2017)
Mesquida, A.L., Karać, J., Jovanović, M., Mas, A.: A game toolbox for process improvement in agile teams. In: Stolfa, J., Stolfa, S., O’Connor, R.V., Messnarz, R. (eds.) EuroSPI, pp. 302–309. Springer, Heidelberg (2017)
Kösling, M., Poth, A.: Agile development offers the chance to establish automated quality procedures. In: Stolfa, J., Stolfa, S., O’Connor, R.V., Messnarz, R. (eds.) EuroSPI, pp. 495–503. Springer, Heidelberg (2017)
Siqueira, A.A., Reinehr, S., Malucelli, A.: Using a statistical method to compare agile and waterfall processes performance. In: euroSPI (2017)
Aldahmash, A., Gravell, A.M., Howard, Y.: A review study on the critical success factors of agile software development. In: EuroSPI (2017)
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2017 Springer International Publishing AG
About this paper
Cite this paper
Poth, A., Sasabe, S., Mas, A. (2017). Lean and Agile Software Process Improvement - An Overview and Outlook. In: Stolfa, J., Stolfa, S., O'Connor, R., Messnarz, R. (eds) Systems, Software and Services Process Improvement. EuroSPI 2017. Communications in Computer and Information Science, vol 748. Springer, Cham. https://doi.org/10.1007/978-3-319-64218-5_38
Download citation
DOI: https://doi.org/10.1007/978-3-319-64218-5_38
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-64217-8
Online ISBN: 978-3-319-64218-5
eBook Packages: Computer ScienceComputer Science (R0)