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.

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.

As organisations have become more agile and try to build “high-performing” teams, they have started to hire for cultural and team fit. As a result they search for people who can collaborate and are team players; who are willing to develop a deep trust in each other and in the team’s purpose; who freely express feelings and ideas; who engage in extensive discussion; who are adaptable and embrace change and who are comfortable managing constructive conflict towards a better outcome.

There are however, many people who do not meet that criteria, and for various reasons, may struggle to meet that criteria in the future.

Everyone brain is wired slightly differently and not everyone’s wiring fits the mould described above.

Does the exclusivity of the above criteria result in certain people missing out who could have significant positive value.

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.

Have you ever learnt something that, at the time, you thought would be life-changing, only to look back at yourself a year or so later and realise that you hadn't changed in the slightest? Why is that? Why is change so hard?

In this workshop which was presented at 1st Conference, we will show some of the neuroscience behind learning and change and explain why change is so hard, and provide some concrete techniques about how to learn more effectively and change your behaviours to put those learnings into practice.

Research into employee engagement asserts that what we want is "autonomy, mastery and purpose" not necessarily a corner office, a ping pong table, or a fancy job title.

Anecdotally though I have seen a different story where particularly those closer to the start of their career are very focused on job titles as evidence of progress.

Super-flat structures such Holacracy (where you perform a collection of roles rather than having a job title) only exacerbate this... there's really no concept of "promotion".

As managers/employers how do we attract, support, grow and retain our staff - is the answer more likely to be a giant skills matrix allowing progress through a level system than flat circles of autonomy?