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.

 
1 favorite thumb_down thumb_up 6 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

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 5 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Alhad Akole
    By Alhad Akole  ~  5 months ago
    reply Reply

    I like these aspects of the submission, and they should be retained:

    • Changes expected in 2020 and beyond. Also include the aspects which you mentioned in comments in reply to Tathagat and Naresh.

    I think the submission could be improved by:

    • reducing the content of history about scrum/ scaled agile. Many participants will know this.
    • If you can focus on "Future of Agile: Digility 2020" more that will help.
    • Also experiments which you have run to change to Diglity will add value.
    •  
  • Tathagat Varma
    By Tathagat Varma  ~  5 months ago
    reply Reply

    Arijit, I would need a strawman of your proposed talk to understand what exactly you will cover? The slideshare link is on another topic and doesn't tell us much on what you want to cover.

    Please also share the link to your video.

    • Arijit Sarbagna
      By Arijit Sarbagna  ~  5 months ago
      reply Reply
      1. I don't have a video
      2. This is a new topic - so my shared links don't talk about this

      I do understand the hesitation & reservations towards accepting this topic as-if. So, I will withdraw this. No issues.

  • Naresh Jain
    By Naresh Jain  ~  5 months ago
    reply Reply

    Thanks, Arijit for the proposal.

    Can you please share with the committee what according to you is the possible change that we may expect to see in the next couple of years? Also on what basis have you come to this conclusion? Is there real research data backing this?

    Also, I searched online, but could not find any video from any of your past presentations. Can you please share at least one to help the team understand your presentation style?

    • Arijit Sarbagna
      By Arijit Sarbagna  ~  5 months ago
      reply Reply
      Unfortunately I never cared about doing a video. So, if video presentation is a mandate - I will not waste your time. :) 

      Thanks and regards
      Arijit Sarbagna

      Sent on the move, pardon brevity!

      On Wed, 10 Oct 2018, 8:19 pm Agile India 2019, <info@confengine.com> wrote:
      Dear Arijit Sarbagna,

      Please note that the proposal: Future of Agile: Digility 2020 has received a new comment from Naresh Jain

      Thanks, Arijit for the proposal.

      Can you please share with the committee what according to you is the possible change that we may expect to see in the next couple of years? Also on what basis have you come to this conclusion? Is there real research data backing this?

      Also, I searched online, but could not find any video from any of your past presentations. Can you please share at least one to help the team understand your presentation style?


      Visit https://confengine.com/agile-india-2019/proposal/7863#comments to respond to the comment OR simply reply to this email (Please make sure, you delete the previous comment's content from the email before replying.)

      Regards,
      Agile India 2019 Team
      comment-9949@reply.confengine.com
      You have received this important update from ConfEngine on behalf of Agile India 2019.
      Download ConfEngine's Mobile App to totally personalise your conference experience.
      If you are 100% sure, that this email was sent to you by mistake, please click here to un-subscribe from all future email updates from ConfEngine.
      --0000000000009721700577e14f97--
      • Arijit Sarbagna
        By Arijit Sarbagna  ~  5 months ago
        reply Reply

        Hi Naresh,

        If audio works - I managed to dig one vintage recording at:

        https://vimeo.com/192610176 

        You have to struggle through to 12:30 of the presentation - where I had a few minutes to talk (though not related to Agile at all).

        Unfortunately, this is what I seem to have available online.

         

        Regarding your other question, the changes I foresee are based on:

        1. My experience so far while working with customers across domains
        2. Being part of several large scale transformation initiatives - which presented the changing market dynamics in a very transparent manner (e.g. starting with a notion of delivering an Agile Project - to eventually converting towards "becoming an Agile organization"). This allowed me to see the changes Industry expects from service or consulting partners.
        3. Additionally, the overwhelming excitement around Digital Transformation calls for certain changes in the typical Agile delivery approach - which is what I coin as "Digility" (i.e. Digital & Agility)  

        What could be those changes? Some are w.r.t. what we understand and deliver under the wrapper of "Agile". It calls for a focus shift - from process to engineering & then back to process.

        It also expects changes w.r.t. how we train and groom new comers in to this Industry. Gone are the days of a standard Scrum Workshop of 2 days - leading one to drive an Agile engagement. We need way beyond those.

        My talk is going to be around these areas. 

        Hope it helps.

        Thanks & regards

        Arijit Sarbagna


  • Liked Rashina Hoda
    keyboard_arrow_down

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

    Rashina Hoda
    Rashina Hoda
    Sr. Lecturer
    University of Auckland
    schedule 5 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    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.

  • Liked Jutta Eckstein
    keyboard_arrow_down

    Jutta Eckstein - CD – Continuous Delivery and Cultural Difference

    20 Mins
    Talk
    Intermediate

    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.

  • Liked Vincent FUCHS
    keyboard_arrow_down

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

    20 Mins
    Demonstration
    Intermediate

    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 !