Agile Lunch and Learn: Past events

  • Good retrospectives (you know, the ones that actually lead to real change?) rest on three pillars:

    • people,
    • process, and
    • follow-through

    What makes retrospectives so difficult is that if any of these three pillars starts to crack, it's very difficult for the retrospective to be a success.

    Getting the right people in the room, facilitating an effective conversation, and following-through on the meeting are both incredibly important and terribly challenging.

    Join me to explore how effective retrospectives can transform you and your team into engines of learning and growth.

  • What Mob Programming Is NOT - Austin Chadwick

    What Mob Programming Is NOT - Austin Chadwick

    253 people attending

    Join us as we delve deep into the world of Mob Programming, separating fact from fiction. In this Agile Lunch and Learn, we will debunk common misunderstandings and anti-patterns associated with Ensemble Programming, seeking to provide you with some valuable insights and practical takeaways.

  • Paradox of Team Size

    Paradox of Team Size

    212 people attending

    Most organizations assume that a team of 20 will finish a software project before a team of five. This isn't irrational, but if you look carefully at the data, you'll find a much more nuanced story. In this talk we are going to look at a study showing how team size impacts projects and discover some useful ways to think about how to propertly size a team in order to set them up for success.

  • 5 Agility Tricks For Your Team - AgileLnL

    5 Agility Tricks For Your Team - AgileLnL

    248 people attending

    In this AgileLnL we are going to explore five simple tricks that can help bring agility to your team. I've sorted a number of things I often do when coaching teams to identify the ones that were the easiest to try but seemed to have the biggest impact on aligning the team with the Agile principles.

  • Attendees have asked for more examples of creating and splitting user stories. In this talk we are going to walk through the evolution of an application story by story. We'll look at how to split stories down to the smallest thing that can be experience as progress and how that enables growth of an application where each story can be delivered in a few days while demonstrating clear value to the user.

  • Test-Driven Development is a process that has obvious parts (the well-known Red-Green-Refactor), but also has subtle nuances that make the difference between a good process and a great one. Ted's "Predictive TDD" builds on TDD, adding an important step to the process: predicting how a test will fail. As part of teaching TDD, Ted created a game that's not only fun, but provides a great opportunity to discuss how TDD works.

  • Creating a (Healthy) Sense of Urgency - Agile LnL

    Creating a (Healthy) Sense of Urgency - Agile LnL

    308 people attending

    In this 45 minute session, we are going to discuss ways to create a sense of urgency that will help create a healthly working environment for your team. We'll also look at pitfalls -- things to avoid that create unhealthy urgency and drive counterproductive behavior.

  • You've probably heard about "splitting" user stories, but often the idea is mentioned without any real concrete idea of what it involves. In this talk we are going to look at why splitting user stories is valuable, some theory about how to do it, and then look at some real world examples of splitting users stories.

  • Effective Daily Standup Meetings - AgileLnL

    Effective Daily Standup Meetings - AgileLnL

    291 people attending

    Your daily standup meeting can be your most important secret weapon for getting work done quickly and efficiently, but this doesn’t happen by accident. Effective daily standups are the result of a lot of intentional decisions to help your team reach its peak potential. In this talk, we’ll look at the goals of the daily standup and then work through how different approaches and common practices support or detract from those goals.

  • Predicting the Future - Forecasts vs. Estimates

    Predicting the Future - Forecasts vs. Estimates

    325 people attending

    In this session, we are going to look at the differences between estimating and forecasting. We will start out looking at examples of sizing work to make sure there aren’t hidden parts and then look at estimation approaches and finally at ways to produce forecasts that let us better predict the future. If you are looking to create more transparency and drive more efficient software development, this session will give you some good theory as well as simple concrete steps to accomplish your goal.