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.

Every organisation has legacy systems, and people who know "where the bodies are buried" -- hidden aspects of dependency, communication, process flow and whatnot which every system relies on to function. These are the dirty secrets swept beneath the rug of "business as usual", and they represent risk and friction alike.

As Peter Drucker is famously quoted, "if you can't measure it, you can't manage it", and the first step towards measuring it is to be able to describe it. How can you do this with gigantic, complex, intertwined systems whose origins are buried in mystery and legend, whose very operation and continued existence is dependent, frequently, on specific people, high priests who may not want to share their arcane knowledge?

This session provides evidence-based techniques for uncovering this complexity, visualising it in a machine-friendly but fundamentally human-centric manner, and using the results to drive real organisational awareness that facilitates conversations and change.

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.

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.

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.

We seem to try to foster a mindset of continuously and relentlessly striving for improvement with mainly one practice: retrospectives have been our default and often only continuous improvement tool for years. I certainly used to think that retrospectives were the most important ceremony and as a coach I used to consider them as my main tool to drive improvement.

However, retrospectives are often disjointed from each other. The insights of one retrospective might be lost right after the end of it or until they are rediscovered in a future one. In addition, if we need to wait for the end of an iteration to look at improving, then can we really talk about continuous improvement?

In this talk, I want to look beyond retrospectives and explore which other tools (Toyota Kata, Improvement Boards, etc.) and other concepts we can inject and explore to foster a continuous improvement mindset. I will present my own journey by sharing experiments I conducted and am planning to carry out, what has worked for me but more importantly what hasn't and where I failed.

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.

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.

Being a member of a cross-functional team – such as Front End, Back End, API, UX, Product Owners, Scrum Masters, BA – comes with problems. In this workshop we will gather our problems relating to cross functional teams and form groups to complete simplified A3 Improvement Themes (lean improvement canvas). Our purpose is to clearly identify our problems and the steps which will assist us in tackling these problems.

We will share our experiences and walk away with a set of A3 Improvement Themes complete with the first steps ready to implement at your own workplace the very next day. Personally, I will walk away with a whole lot of Improvement Themes. It’s a win-win

Software development has embraced techniques like TDD (Test Driven Development) to help reduce the cycle time between developing code and validating it works.

As application development practice evolved, we needed to respond to change faster while still maintaining our quality - the way we developed our solutions needed to change - and so did our tools.

Now that we have Infrastructure as Code (IaC) a whole new range of cycle time challenges have emerged. No longer are we building simple proof of concept systems using IaC, many of todays cloud deployments are multiple complex servers composed of tens or hundreds of servers.

In this session we take a look at the tools and practices available to Infrastructure developers to reduce the cycle time of change while maintaining a high level of quality and confidence.

Diagramming and mapping our thoughts changes the way we think. It makes our thoughts and ideas broader and helps us to see patterns. These approaches are great for both individual problem-solving and team collaboration and co-creation.

By learning and applying these visual techniques we follow in the foot-steps of great thinkers such as Leonardo, Edison, and Feynman who used visualisation as a major guide, more so than language and equations, which came later.

Many of us have tried our hand at mind-mapping, which is an excellent tool for expanding our ideas and solving problems by breaking away from linear thinking. In this talk, I will demonstrate other powerful ways we can map our ideas and thoughts to solve problems, both as individuals and as teams.

Techniques include:

- Lotus blossom technique

- Systems mapping

My objective is to offer you options so that you can choose the technique that best suits you.

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

You were created for a specific and unique purpose - there is a special mix of gifts and talents in you that need to be shared with the world. In today's workplaces, it's critical to have the skills to continually self-evaluate, evolve and inspire others to change. We apply continuous improvement to our products, but not often enough to ourselves and our cultures. So how do we access the greatness within ourselves and call it out from those we’re leading? This session will look at 4 principles that promote growth and foster transformative collaboration. You’ll come away with a combination of mindset and action points to put into practice.

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.

The communication tools of Liberating Structures will teach you how to facilitate the discussions your org needs. I am going to demonstrate how to use these techniques in the workshop. And all the attendees are going to be fully immersed and ready to wield their new knowledge the very next day at work.

If you are a recent convert to LS, come learn a new set of techniques to continue the journey. If you are new to LS, this will start you on your path of facilitation mastery.