“Agile has become overly decorated. Let’s scrape away those decorations for a minute, and get back to the center of agile.”
— Dr. Alistair Cockburn, co-author of the Agile Manifesto.

“When encouraging getting back to the center of agile, I found I kept emphasizing four things:

– Collaborate
– Deliver
– Reflect
– Improve

The nice thing about these four words is that they don’t need much explanation. They don’t need much teaching. With the exception of “Reflect”, which is done all too little in our times, the other three are known by most people. You know if you’re doing them or not.”

Agile has become overly decorated. Let’s scrape away those decorations for a minute, and get back to the center of agile.”
— Dr. Alistair Cockburn, co-author of the Agile Manifesto.

“When encouraging getting back to the center of agile, I found I kept emphasizing four things:

– Collaborate
– Deliver
– Reflect
– Improve

The nice thing about these four words is that they don’t need much explanation. They don’t need much teaching. With the exception of “Reflect”, which is done all too little in our times, the other three are known by most people. You know if you’re doing them or not.”

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.

Design Council's 'Double Diamond' model requires teams to shift between divergent thinking and convergent thinking with regular cadence. But what does that actually feel like and how do we do it?

In this session we'll play some Improv games together that prime divergent thinking (creating options), convergent thinking (making decisions) and the pivot point between the two.

This is a participatory session with a pinch of theory and whole lot of game playing.

In this session we will cover a brief introduction to the research by Kegan and Lahey where they discovered that behind each of our habits is a strongly held belief that not only keeps us in our groove, but also fights any change that threatens the status quo.

We will discuss why personal growth and increasing our mental complexity is so important for agile and business transformations in today's VUCA world to succeed.

We will create your Immunity To Change Map which is a simple way to bring to light the your personal barriers to change. We will start by outlining your commitment to an improvement goal. Then we will sketche out the things that you are either doing or not doing that prevent progress towards the achievement goal. The Map then identifies competing commitments, as well as the big underlying assumptions behind those competing commitments.

The objective is to pinpoint and address whatever beliefs and assumptions are blocking you from the changes you want to make.

You will leave this workshop with a better understanding and tools to overcome the forces of inertia and transform your life and your work.

Is your team or organisation in a funk? Seeking some fun ways to shake things up, or change behaviours?

Put simply, a culture hack is an intentional action to affect positive change within a team or organisation.

This session will take you through 10 easy to implement hacks to create an Agile culture within your team or organisation.

Come away with:

• A deeper understanding of how culture hacks work
• The excitement to try one of the ready-made culture hacks
• The confidence to create your own culture hack!

Scrum is a great framework but there are many ways to do it poorly. The average IT worker is interrupted every 15 minutes, which equates to 2000+ interruptions for a Scrum team every sprint. Unthinkable on a production line, yet too often the norm in offices.

I conducted original research with Scrum teams in Australia last year as part of my Master of Management thesis (and achieved an A), to understand the causes, patterns and impacts of these interruptions on the team's effectiveness and their happiness. And, how mature teams control interruptions rather than let themselves be controlled by interruptions.

Attendees will play a short game to demonstrate how destructive the context switching from handling frequent interruptions is.

My talks are always highly practical and I provide 3 takeaway actions for teams to improve their 'flow' and reduce interruptions.

This is essentially the same session that I did at the recent Scrum meetup. The presentation material is here:

https://www.slideshare.net/DanielPloeg/scrum-and-kanban-92219317

I will need to go through the material a little more rapidly for the timebox and perhaps restrict questions.

Management and managers have not gone away with the advent of Agile.

Old-fashioned carrot and stick management may have worked wonders back in the early days of industrialisation, but is woefully inadequate for undertaking complex knowledge work in an uncertain and volatile world.

At the other extreme, dropping all structure in favour of radical self-management — mocked as "everyone gathering around a campfire singing kumbaya" — doesn't instantly lead to effective coördination, let alone organisational success.

In this workshop we explore the state of the art of management with a mix of design thinking and facilitated discussion to uncover rich insights and perspectives into the nature of management, and what a re-boot could look like.

Let's level-up management!

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

Many software engineers are lead into the false assumption that we are hired to write code. This talk challenges that perception and discusses the real reason we are paid to turn up to work every day.

Coding is fun, but we are paid to solve problems.

I will try and convince you that you can add more value, and have more fun, by concentrating on the problem, not the code.

Over the years REA has mastered the art of delivering products following the lean startup principles, however, working with a bank to create a home loans product was a different ballgame. Functioning in the Build-Measure-Learn cycles requires a fundamental change in the way people (or organizations) think and work.

In spring of 2017, REA made a big leap from being purely a media organization to venturing into financial services. As a result, there is now an innovative product offering in the Australian home loans market that allows consumers to sort out their home finance needs while they are still in the market looking for their dream home, all from the comfort of their living room couch.

This talk is about how to shape up your products with decisions based on data, metrics, and evidence over personal opinion.

Agile Mindset is highly talked about and prized amongst agilists. Claims for its benefits range from 10x improvement, can’t be agile without it and requires organisational and cultural change to achieve.

Social psychology presnets a different view where mindset is a cognittive toolkit used to understand and taking action in a complex world. This defintion implies everyone posesses an agile mindset.

Is agile mindset a nirvana state which will enable you to levitate and be at peace with the world? Is it what is constraining everyone from achieving life, love and happiness. Or is it something more practical, humanistic and useful.

Looking through the lenses of behavioural and social psychology we will understand what mindset is, how it works and how you can become more aware of how yours and others mindset are operating within the agile domain.

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.