location_city Melbourne schedule Jul 20th 03:45 - 04:30 PM AEST place EN 205 (C40) people 26 Interested

"If you don't like the weather in Melbourne, wait 10 minutes."

There isn't an application able to correctly forecast what our day will be like. Many people in Melbourne are frustrated by both the weather apps that all look the same and the unpredictability of the weather changing every ten minutes.

This interactive session will see us reflect on Agile and System Thinking principles to build a prototype through one Lean Startup cycle. Using Melbourne's weather, it will highlight how important it is to question the value brought by things that are established.

Shy inventors will have an opportunity to understand that an idea is never too big and learn a good way to start getting their dreams into reality.

 
 

Outline/Structure of the Workshop

  • Short presentation (7 min)
  • Prototype build - first phase (10 min)
  • Prototype build - second phase (10 min)
    • Gather feedback from other teams' members through user testing/presentation in groups
    • Adapt the solution / late build
  • Expo: Presentation of built products (10 min)
  • Take aways (3 min)

Learning Outcome

  • Understand and apply Lean-Startup approach
  • Get familiar with the necessity to quickly build MVPs of our ideas to start testing and get feedback early on.
  • Get to reflect on Agile fundamentals and how they can impact our ways of thinking.
  • Get to understand basics of System Thinking and facilitate a better approach to deal with complex Systems.
  • Understand how our approach toward the Weather reflects the difficulties in transitioning to Agile.

Target Audience

Anyone, especially those furstrated when Weather apps change their mind in the last minute.

Prerequisites for Attendees

Just you.

schedule Submitted 5 years ago

  • Victoria Schiffer
    keyboard_arrow_down

    Victoria Schiffer / Daniel Prager / Tomasz Janowski - Agile Developer Immersion - Refactoring

    300 Mins
    Workshop
    Advanced

    IMPORTANT - As places are limited, please register specifically for this session. Also, please register for day 2 of LAST Conf, if you wish to attend the 2nd day.

    You can also read more about the sessions in this blog post. For a beginner friendly version of this session see Agile Dev Immersion - Fundamentals

    Get ready to level up at refactoring at LAST Conference's first Refactoring Developer workshop. Inspired by Code Retreat, we have run a similar session, for the basics of agile development, at LAST Conference for the past few years. We have felt that it's Important to support learning in technical disciplines that are extremely important in agile software development.

    Too many Agile and DevOps initiatives are stymied by code bases that are hard to change and understand.

    While disciplined teams who rigorously practice pair programming, test-driven design (TDD) and other technical Agile practices avoid producing new legacy code in the first place, cleaning up a pre-existing mess is notoriously difficult and dangerous. Without the safety net of excellent automated test coverage, the risk of breaking something else as you refactor is extremely high. Also, code that wasn't designed and written with testability in mind makes it really difficult to get started. So most don't even try ...

    In the Refactoring workshop developers learn how to build an initial safety net before applying multiple refactorings, and have lots of fun along the way!

    What's it all about?

    We will be following a variation of the Legacy Code Retreat format. Working with legacy code (provided!) participants first learn how to build an overarching electronic safety net using the Golden Master Testing technique, before applying a range of refactorings too dangerous to otherwise attempt (but totally worth it).

    As with regular code retreat, we will practice pair-programming, rotate pairs, and continue to practice rigorous unit test automation, and share our learnings.

    Unlike regular code retreat you do not have to delete your code at the end of each sprint, and the TDD cycle is a bit more relaxed.

    Following the opening session, Refactoring workshop will take the remainder of the day, with breaks synchronised with the main conference. You will also be welcome to attend the end of day drinks!

    What is Legacy Code?

    Legacy code has beed defined "as code without tests" and equivalently "code you are afraid to change". Unfortunately far too much "professional" code is legacy code.

    Why should you come?

    • We need developers and architects with the skill to continuously refactor and redesign, and managers and leaders who understand the value in doing so
    • Come and practice and share some of the fundamental technical skills needed to safely refactor
    • Lift developer engagement and work satisfaction by investing in technical quality rather than drowning in technical debt
  • David Williams
    keyboard_arrow_down

    David Williams - Scaling connection, trust and agility using Management 3.0 practice

    David Williams
    David Williams
    Agile Coach
    ANZ Bank
    schedule 5 years ago
    Sold Out!
    45 Mins
    Case Study
    Beginner

    This interactive session will explore connections and how personal mapping can be scaled to kick-start a platform to build better communications, trust and psychological safety to underpin your agility journey.

  • Bob Martin
    keyboard_arrow_down

    Bob Martin - Are you stuck in a WTF loop? Your choice of words may have something to do with it.

    45 Mins
    Interactive
    Advanced

    Language sets the tone for change, but we continue to use the same tired language that we have been for years. You know the language, that dialog, those words that fill the pages of Linked In, airline magazines, and 'modern' management speak. Meaningful change continues to eludes us; and in the end, if we don't change our language, our dialog, our words, we're just waiting to fail (and not the good kind of fail!).

    Join me for an interactive discussion of my top ~five words / phrases that I believe cause more harm than good. We'll discuss why they're an issue, and I'll suggest alternatives that may help guide you onto a better path.

  • Hamdam Bishop
    keyboard_arrow_down

    Hamdam Bishop - Building great agile teams, but first: Culture.

    Hamdam Bishop
    Hamdam Bishop
    Release Train Engineer
    AGL
    schedule 5 years ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Why are culture, mindset and behaviours so important in growing and transformational agile environments? How is great culture created and killed? What ingredients attract and retain great people?

    In a market where there are so many wonderful and exciting places to work, we need to focus on creating an environment that people feel passionate about being a part of! Come to this session to talk about culture and why it's important, how to create great culture and how to retain and grow that culture in a rapidly changing agile environment.

    You'll walk away with:

    • An understanding of why culture is such an important element of successful agility
    • Practical steps for building and retaining culture in an agile environment
    • An example of what success looks like
  • Jon Gedge
    keyboard_arrow_down

    Jon Gedge / Jasmine Hessel - Accessing Relationship Systems Intelligence with Constellations

    45 Mins
    Workshop
    Intermediate

    Each of us is a member of complex relationship systems - at work, at home and in our communities. Just as emotional intelligence is the ability to understand and manage our own emotions and social intelligence is the ability to empathise and communicate with another individual, relationship systems intelligence is the ability to view a team or group as a unified whole and to work directly with that whole system rather than with a group of individuals.

    In this session, we will use a relationship systems coaching technique called constellations to listen to the ‘voice of the system’ which is created by everyone who attends the session, so we can explore together how comfortable we are in working with conflict.

  • Mike Jones
    keyboard_arrow_down

    Mike Jones - Flufferbot automation at scale & LAST lessons from the TESLA Production System

    Mike Jones
    Mike Jones
    Lead DevOps Engineer
    AGL Energy
    schedule 5 years ago
    Sold Out!
    60 Mins
    Interactive
    Intermediate

    Lean and Systems Thinking is about to get bigger. By several orders of magnitude.

    Will the Tesla Production System inspire the next generation of (autonomous) lean systems thinking?

    Tesla's 'gigafactory' has significantly scaled automated production. But not without problems and bottleneck constraints. Tesla is making a lot of mistakes along the way and CEO Elon Musk recently shared some of his lessons learnt automating Model 3 production.

    Whether you are automating testing, automating devops, or introducing lean agile practices across an organisation, let's get together and reflect on our own experiences of automation at scale and other lessons learnt from the Tesla Production System.

help