10 lessons about agile from a non-agile person

As a leader, I'm always looking for new ways to improve the way I lead, the way our projects are run, and the way I can optimise our business. When agile was introduced into a more mainstream business audience, I was one of them - I saw the potential for the values and principles to work for all types of businesses, not just software development.

Since then many years have passed and after being exposed to and in the bowels of all forms of agile mindsets converted into approaches (e.g. Scrum, SAFE, etc.), I've learnt a few things - some good and some bad. I've distilled it to 10 lessons I've learnt about agile, all coming from a non-agile practitioner.


Outline/Structure of the Talk

  • From software to mainstream
  • The "hype" of agile
  • Lesson 1: Agile time - a different concept of "time"
  • Lesson 2: Traditional funding models don't work with agile
  • Lesson 3: Backlog is a never-ending "to-do" list
  • Lesson 4: No one knows what "done" means
  • Lesson 5: Product Owners need "product" training
  • Lesson 6: Practitioners should re-read the manifesto
  • Lesson 7: Moving cards quicker isn't always good
  • Lesson 8: Outcome trumps process
  • Lesson 9: Agile is more about people management than task management
  • Lesson 10: Agile doesn't work if the customer isn't involved

Learning Outcome

The aim is for the audience to walk away understanding that all the discussions and innovation on how to improve the agile mindset and the associated approaches on how to use methods aligned to agile (e.g. Scrum) need to sometimes stop, take a step back, and ask people who have been through it who have not gone through any agile certification what they think about it and how it can be improved. This is my take on the things I've found about agile after being in a dozen projects run with scrum and also employing an agile coach just so that I can understand how it can be used for my own company.

Target Audience

Executives (CxO, Founders), Business and Technology Leaders, Change Agents, VP/Director level Product & Technology Leaders, Product Owners and Designers.

schedule Submitted 1 year ago

  • Michael Nygard

    Michael Nygard - Uncoupling

    45 Mins

    We overload our terms a lot in this industry. "Coupling" is one such. That word covers situations ranging from essential to accidental to comical to cosmic. Coupling seems to be the root of all ills. It is the molasses that slows our every move. And yet, in the industry from which we borrowed the term, "coupling" was not a dirty word. It meant something ingenious. Let us contemplate coupling for a time and see what we can do about it.

  • Dana Pylayeva

    Dana Pylayeva - Journey without fear. Leading your teams to high-performance.

    45 Mins
    Psychological Safety has been identified as a #1 condition for creating high-performing teams by Google’s Project Aristotle. Yet, many organizations today find themselves being affected by fear in the workplace. It manifests itself in employee's disengagement, lack of innovation and toxic working environments.
    How can we start taking the first steps away from the culture of fear and towards a culture of psychological safety?
    Join this interactive session to experiment with a new "Fear in the Workplace" and "Safety in the Workplace" games (designed by the speaker) and start these difficult conversations in a fun way. Discover a number of safety enhancers that can help you, your teams and your organization on this journey.
    Highly experiential, this session is designed with elements of Training from the Back of the Room and brings together “tried and true” practices from the years of coaching teams in US, Canada, Ireland and Japan.
    Join in to learn by doing and bring back a set of practices designed to significantly improve psychological safety in teams and organizations.

  • Manoj Kumar
    Manoj Kumar
    Selenium Project
    schedule 1 year ago
    Sold Out!
    45 Mins

    Digital Transformation is now the holy grail of IT organizations. However, most companies are still struggling with setting up a proper Continuous Delivery process, which shall help the transition into shorter release cycles and faster, more frequent deployments to production.

    Teams may already be familiar with Continuous Integration, Continuous Delivery and Continuous Deployment (the 3Cs) and the differences between them. However, to make these 3Cs possible, we need a fourth C, namely Continuous Testing (a.k.a Test Automation.) Continuous Testing is the fast feedback mechanism that assists the 3Cs and is one of the most difficult challenges for digital transition.

    In this talk, I'm aiming to cover the top continuous testing pitfalls and how companies are solving these problems. This talk is based on practical examples that include key pitfalls around:

    • Test Data management
    • Choosing the right tool/framework
    • Deciding on what to automate?
      • Is In-Sprint Automation possible?
      • Is automation part of Definition of Done?
    • Effective collaboration
    • Test Environments
    • Flaky tests

    It's time the testers took control! And use some of the modern tools that help address those problems. This talk will cover tech stack like Selenium, Appium, PlayWright, Taiko, Docker, Kubernetes, Grafana/Kibana, TestContainers.

  • Saiful Nasir

    Saiful Nasir - Product Owners are the worst customers

    45 Mins

    "We should do this because I think it's what the customers want"

    Product Owners (PO) have a lot of responsibilities, and one of them is to provide guidance to the team on what problems to solve and what is valuable to customers by bringing the voice of the customer and user to the table. However, the situation becomes dangerous when the PO becomes the voice of the customer and user, making decisions based on their working experience, without supporting evidence. This is often even worse in startups, where the pace is faster and the PO has a greater responsibility in steering the team in the right direction.

    This talk is to help Product Owners as well as the teams working with them to ensure that the team is focusing on the "right problem" to solve and backing it up using evidence. I will share some tips on how to use things such as Customer Experience to focus the team to solve problems that matter, and how different types of data can help PO's make more informed decisions for their teams.

  • Satyavrat Nirala

    Satyavrat Nirala - Agile in Marketing