Are you directly/indirectly involved with Agile software delivery? If yes, you may have already started questioning yourself “what next”? We have seen the evolution of Agile software delivery over years. Kent Beck took best practices to extreme levels way back in the nineties. We saw Agile Manifesto for Software Development coming out in 2001 and Scrum gaining popularity. And gradually organizations realizing that simple Scrum (or pure Scrum) may not work for large scale deliveries - leading to formation of multiple competing Agile Delivery Frameworks like SAFe (Scaled Agile Framework), Nexus, LeSS (Large Scale Scrum) and many others.

But as we get uprooted by the wave of Digital Transformation - what is in store for us in the near future? Does Agile stand a chance to exist (or co-exist) as is? Or will it need to run through a sea change to survive?

We explore the future of Agile (for software development) in this talk and see the possible change that we may expect to see in the next couple of years.


Outline/Structure of the Talk

  1. Intro
  2. Why Agile came in to existence?
  3. How it evolved?
  4. Saturation
  5. Deformation
  6. Survival through adaptation
  7. Future possibilities

Learning Outcome

By participating, you learn how Agile way of working went through an entire life cycle from inception, to maturity, to eventual state of conflict and then a re-invention in the lights of Digital Transformation.

Target Audience

CXO, Agile Practitioners, Agile Enthusiasts

Prerequisites for Attendees

Familiarity with Agile delivery frameworks, its inception, growth, challenges (at a high level)


schedule Submitted 2 years ago

Public Feedback

    • Rashina Hoda

      Rashina Hoda - Becoming Agile vs Doing Agile (Research Talk)

      45 Mins

      After 20 years since the manifesto, the latest state of agile reports more than 80% of organizations as "still maturing" in their agile practice. As agile methods expand beyond small teams and software itself, we are still struggling to answer these questions:

      • Why is it that some teams are more 'agile' than others even though they all claim to be practicing agile methods?
      • What all dimensions need to change as teams, managers, and entire organizations attempt to become agile?
      • How do these dimensions interact with each other?
      • Overall, what does it take to become agile and how does that differ from doing agile?

      This talk is based on my original theory of becoming agile developed from 10+ years of industrial research of agile practice in New Zealand and India, which received the distinguished paper award at the IEEE/ACM international conference on software engineering (ICSE), in 2017.

      In this session, I will explain the key dimensions that need to transition during agile transformations, using industrial examples, and highlight what you can do to progress beyond simply doing agile, to harness the most from your agile transformations.

      This keynote will add a unique research perspective to the conference program, sharing agile research in an industry-friendly format and delivery style.

    • Jutta Eckstein

      Jutta Eckstein - CD – Continuous Delivery and Cultural Difference

      20 Mins

      DevOps and continuous delivery is typically elaborated technically - what kind of tools, technologies, or skills are necessary for being able to deliver continuously. Often it is forgotten that continuous delivery requires also a culture change - in development, operations, marketing, sales, and not least for the customer.

      This can be recognized for example, that although it is technically possible for a team to deliver continuously, but it seems that this delivery isn't welcomed. This means the actual system will not be directly used.

      Therefore, in this session by taking into account the necessary cultural change, I want to answer the question how to implement continuous delivery successfully and what kind of pitfalls you need to be aware of when doing so.

    • Vincent FUCHS

      Vincent FUCHS - Keeping hundreds of code repositories consistent, and staying sane !

      20 Mins

      With the move to microservices architecture, a lot of teams end up managing dozens of code repositories (vs just a couple before), and some tasks that were done quickly manually are now becoming very time consuming : consistency of the repositories, and eventually of your platform, gets impacted, making it more and more difficult to manage.

      Surely, there must be some tools existing to take care of boring tasks like finding where a given dependency is used, and upgrade it automatically (this is just an example)... Well actually, we didn't find anything, so we implemented them ourselves and made them available for everyone !