“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!

Imagine you are a Mad Agile Scientist and have a diabolical experiment to conduct - what would happen if you exchanged the brains of a Product Owner and Scrum Master? Mwuhahahaha!!! How would the body of a Product Owner with the brain of a Scrum Master act? And vice versa?

Perhaps the Scrum Master would now treat the team like a backlog? This Scrum Master would be focused on value and maintaining a coaching backlog of team and person improvements. This Scrum Master is refining the team, crafting a group that delivers value.

And perhaps the Product Owner might treat the backlog like a team? Rather than backlog refining, they coach the backlog. They would be focused on nurturing, protecting, and empowering the backlog. The backlog might transform from an irritation into a labor of love.

Although this experiment sounds terrible, this change of perspective might be what you need to reanimate your dead team or backlog.

Join the fun and come learn what horrifying results await!

Consumers, like never before, have real choice about where they purchase products and services. Organisations large and small need to adapt quickly, or die.

Leading to a number of Australia's largest organisations deciding to 'go agile', in an attempt to tackle this VUCA world head on.

But is putting a nice, customer-centric, wrapper around a whole organisation transformation what agile is actually about?

During the 30 minute discussion Simon will discuss and provide a perspective on:

• Some of the key design principles that need to be considered when undergoing an agile transformation

• Balancing empowerment and control in search of alignment

• Where change like this works; and where and why it doesn't!

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.

How do we make an impact to the starters in our field regardless of your position in the industry? Let’s put ourselves in the shoes of a newcomer and explore mentoring from a different perspective.

Coming from being a part of an 18 month Graduate Program position at REA Group, my peers and I have been fortunate enough to find ourselves in an environment where mentoring and pairing is a big part of the culture. This talk is designed to give the attendees an insight on what a diverse range of mentees actually wish and crave for, to empower people to mentor and help shape the future of tech.

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. If you are a developer with more experience, you might like to consider Agile Dev Immersion - Refactoring.

Get ready to Level Up your agile developer skills. Inspired by Code Retreat, we have run a similar session 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.

This is an intensive practice event for developers, inspired by the Code retreat movement. It focuses on the fundamentals of software development and design, including pair programming, test-driven development, OO and functional programming techniques, and new languages. By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the format has proven itself to be a highly effective means of skill improvement. Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.

This event is beginner friendly. However it is also suitable for those who have already attended similar sessions as we will be creating a tenpin bowling scorer rather than solving Game Of Life again. There is also a concurrent workshop for Refactoring legacy code that is aimed at more experienced devs.

Following the opening session, The Agile Developer Immersion 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!

Most organisations now understand why they need insights on customers’ needs and behaviours to drive customer-centred outcomes within agile teams. But many organisations struggle to convert insights from their quantitative and qualitative research into value that actually gets delivered to customers.

And whilst many organisations are employing researchers, and building agile teams, organisational behaviours—at a team level, and also at a leadership level—often get in the way of those teams converting insights into value, leaving teams feeling lost at sea.

But there are behaviours and principles that teams and leaders can put into practice to create an culture of effective experimentation based on insights. By being more human, we can enable our teams to deliver efficient value to customers, and even within the organisation itself.

Come on a swashbuckling journey with us, as we show you how to navigate the oft-treacherous waters of organisational culture, to help your teams reach the mystical location we call Value Atoll.

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!

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.

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.

Do you spend a lot of your time trying to solve people’s problems? What if you could learn a simple tool that you could use to help them learn to solve these problems for themselves? A tool that would enable team members to think more creatively and take more ownership of their work. By using coaching conversations to provide support and feedback, you can help individuals or teams to make sustainable changes and improve their effectiveness.

This workshop is based on the Wall Street Journal bestseller The Coaching Habit by Michael Bungay Stainer. You will learn and practice his seven essential questions to help you coach people to find their own solutions to their problems.

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.

There are some awesome prioritisation methods out there.

However, which one do you choose and use?

Often they can be so unwieldy and time consuming that at best all you can do is practically just use one.

In this session, we'll explore how you can quickly utilise multiple prioiritisation methods against each other in order to facilitate healthy discussions.