The Agile version of Cards Against Humanity. You may have seen versions of this on the internet, but rest assured this version has been enhanced to yield a minimum of 156% more awesomeness. Relatively fresh from its stellar debut at the 2017 Xero Unconference!

Autonomous and empowered teams are a key building block of agile organisations but require a great deal of trust to work. Management and leadership must trust people and teams to do the right thing, and teams need to trust that management will support them when needed.

Transparency is a low-cost means of building trust. Transparency gained through the open sharing of information, particularly visual information, has played a large part in agile and lean thinking - from lean's visual controls, to XP's "big visible charts" and beyond.

We will explore how transparency, and the radiation of information, can build trust and cultures where "safe to fail" is more than a theoretical concept.

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

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.

I've been on a journey, and I've come to know that apathy and ambivalence are an awful place to be.

I want to talk about big life changes and the uncertainty that comes with them.

We will look at navigating this kind of journey in your own life. How curiosity and self-awareness can lead to meaningful change that will better equip you for new and exciting things in your life.

We will also discuss the importance of healthy company culture as the undercurrent that enables all of this.

"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.

DevOps engineers fly from job to job doing the same things - the systems differ, but the problems (technical and otherwise) remain the same. Eventually, we ask questions not about implementation or technology, but meaning: what am I doing all of this for?

In this talk, we'll cover how we provided a converged solution (Docker cluster, monitoring, alerting, and security) from 0 to 70% of the company in three months. We'll cover how we did it - the approaches, the workflows, and the rules - but more importantly, the why: to provide an environment where the things that we produce change whole organizations and make people's lives a little better.

But most of all, how it made us a little bit kinder.

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.

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

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.

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.

Working on a software product team can be quite a terrifying experience for new employees, especially when you are a round peg in the square holes.

A year go, I landed in the biggest tech company in town as a non-technical person on a technical team. Looking back on a year full of adventures and scary challenges, I’m here to share with you:

• What to expect in the world of code, API, kanban, MVP and DevOps
• The candid (sometimes, painful) lessons on how individuals can prepare for, survive and thrive in this kind of environment

We naturally crave learning. It is an innate ability that has allowed us to survive, evolve and thrive. Science has also shown us that our brain is quite flexible and can allow us to continue to learn at any point in our lives. Moreover, the Agile community keeps spreading the mindset of continuous improvement and continuous learning. It should therefore be logical to see most organisations using this to their competitive advantage.

However, are we putting enough emphasis on growing people's ability to learn? Do we really understand how learning works? And if we don't how can we possibly tailor our organizations to foster learning?

To explore these questions, I want to look at what scientific research tells us about learning but also explore the concept of having a fixed / growth mindset and help you reflect on how you can use these concepts to create the learning organisations of tomorrow.

Agile is now considered as a "must-have methodology" to be successful in developing software. Even, it starts extending to non-software businesses and its practices and principles are spreading out to many teams and organizations.

But beyond the buzz-words, we often race to apply solutions and miss the true values beyond naming, frameworks or tools provided by Agility.

This session is an Lightning talk to foundation ideas that underpin Agility. It revisits some basic fundamentals that have dropped out of the modern agile discourse when leading the change toward better ways of working. Beyond the buzz-word that Agile became, let remind us what be Agile truly is.

It will be particularly useful to agile consultants, scrum masters, iteration managers and change agents driving the agile agenda.

This session can be adapted to a longer Agile 101 format mixing introduction of fundamentals and debat/experience feedback.