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

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

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.

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.

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.