The purpose of Agile is defined in the “Manifesto for Agile Software Development ”, and the purpose is to provide developers, engineers, computer scientists and programmers the best possible environment for fast and efficient development of software that satisfies the users.
Instead of this, focus has shifted to project management, SCRUM, and methods like SAFe for improving predictability and manageability of large, distributed IT projects. This understanding of Agile emphasizes certifications and expensive courses for managers; while dismissing the original principles for an Agile culture and its empowerment of the developers. This has led to a tyranny of processes and lack of understanding that Agile only works when it encompasses engineering methods and values.
This is expressed as: “If the developers are not competent – then send them to programming courses!” Such comments completely miss the point and show fundamental ignorance of what Agile really is: A culture of collaboration and empowerment supported by specific engineering practices and intended to achieve success and satisfaction of customers, users and developers alike. So today, we will look at the developer side of Agile to make it visible and important again.
It is time, we engineers take back ownership of Agile!
Intended Audience:
IT developers and managers – with an interest in development methodology and IT engineering practices.
About our presenter - Peter Michael Bruun:
Peter has a master in electronics engineering and a Ph.D. in Computer Science from DTU in 1989. He has also studied philosophy at the University of Copenhagen. He started with agile development as early as 2000 and today he does advanced software development as a Senior Distinguished Technologist at Hewlett Packard Enterprise in Allerød. He has done many customer facing IT projects as well as development of software products using Agile methods, all while having retained his “License to Code” throughout the years and so he views Agile from the developer’s perspective, and has great experience at making the methods work in practice.