Agile coaches are mostly not qualified in counselling and therapy.

Knowingly, mistakenly or ignorantly, some coaches divert their coaching instances to personal conversations as if they were therapists. Counselling is a skill which requires practice, experience and certification.

It also has regulatory boundaries. While coaching and counselling are different, there is an overlap. Several coaching approaches had their roots in therapy: e.g. Solutions Focus Coaching came from Brief Therapy, Non-Violent Communication from Marshall Rosenberg (via Carl Rogers).

As coaches, it is imperative to have self-awareness that we do not cross the line in explore in unchartered territories of counselling. Join this panel to learn more about counselling and coaching.

How can an Agile Coach figure out when an Agile “Transformation” is going wrong? Are there signs that they might see, heed, and take action upon? Of course, there are!

Hindsight is 20/20, but in the moment, these warning signs can be hard to see. Let’s explore some of the more common, and frightening, warning signs that your Agile “Transformation” might be exhibiting. We will discuss transformation provider types, frameworks, keywords, and other anti-patterns that might be signs that THE END IS NIGH.

This session will review common themes and help familiarize you with the warning signs. Armed with this new knowledge, you will be able to plan as appropriate, to help navigate your organization through potential impending doom.

In today's world, if businesses aren’t more agile in the way they execute on their strategies, they risk over investing on initiatives that won’t result in the future growth they seek.

In this talk, we will discuss and share stories from organisations driving towards holistic business agility, and present a simple framework that can help organisations better check the performance of future growth strategies, and act earlier when it looks like those strategies are not going to turn up.

This talk is a case study of our architectural evolution over the last 2 years.

Our start-up had licensed a customised warehouse management system in order to demonstrate our innovative new business model. The WMS had a traditional 3-tier architecture based on Java and SQL server, and was lightning fast with most of the business logic encapuslated in stored procedures.

Out our start-up we needed to be able to "test and learn" - ie rapidly develop and deploy new features and test them in the market with our customers. Based on the feedback we would identify tweaks to the business model, and fine-tune the functionality that our customers wanted.

We had a launch date 5 months in future, a need to scale rapidly, growing the team from 2 devs to 20 within 8 weeks. And we needed to be able to work in parallel on multiple features. Whilst ensuring that the application was secure, performant, and reliable.

The answer, according to a bunch of experts, was to adopt microservices.

Three years later, we have a suite of secure, scalable, and resilient applications running in AWS. We deploy to Production multiple times a day, and our MTTR is less than 30 minutes.

And we have Services. Some of them are "micro".

But reflecting on what we learned in that period, there are a lot of things that we wished we had done differently.

In this talk I'll walk you through the evolution of our architecture, explain some of the choices, and highlight what we learned, and discuss what we would do differently if faced with the same decisions today.

This case study talks about the last 9 months of our start-up where we went from “no team, and limited functionality” – to launching a successful and thriving business backed by completely custom trading platform and fulfilment engine.

This presentation will come with the goal of teaching attendees;

- How to look out for gamification and habitual depedance in the real world and digital products

- How these features will try to use your own brain chemistry to their advantage

- How to use these features in your own products and assit your customers into building good habits

After walking away from this presentation the attendees should feel they have a much better understanding of habitual loops companies will put in their products to try and get you onboard, the ways in which they will try to manipulate you, and how you can use these powers for good.

"Before you can kill the monster you have to say its name"

As coaches and practitioners of Agile we see role anti-patterns everywhere lurking, sometimes quietly sleeping and waiting to kill (the momentum!) of our teams.

Have you met the Mr.Frost a.ka. the Frozen Middle Manager? The "Busy Bee-ast" so deep in her hero culture she has become a bottleneck and a crutch for the team. What about Hydra, the 9-headed PO, who can't make up his mind on his 10000 requirements. He comes with an extra technical head that takes joy on the fact he still has code access. The head occasionally makes code changes to "help" the team with the backlog without their permission.

This talk is about these monsters. The monsters around us and potentially within us.

We will know them, discuss them and identify how we can equip ourselves and the teams we work with to battle their evil rather questionable forces. More importantly in this talk, whether living around us or living within us, we will uncover how we can help guide the monsters to the right path.

‘Industrial Revolution 4.0’ and ‘exponential change’ are two concepts that are creating a lot of buzz lately, and for good reason. Emerging technologies such as artificial intelligence and Internet of Things are being adopted at a staggering pace. Platforms companies such AWS have lowered the barrier to entry, and are enthusiastically supporting organisations to experiment and propel forwards into a new way of doing business.

At DiUS we are fortunate to have a front row seat as this wave of change arrives. With our in-house specialists in areas such as AI and IoT, we have formed broad cross functional teams - including engineers, experience designers and agile delivery leads - to help our customers solve their business problems using emerging technologies.

Through this talk I will provide insights based on case studies of DiUS's recent project experiences. We'll contrast the dynamics with the digital software world that many of us are accustomed to working within, and highlight the constraints introduced by factors such as hardware manufacturing, acquiring training sets for machine learning, and navigating the complex systemic challenges associated with entering immature markets. Finally, we will discuss what we as a community need consider as to how we apply the agile practices and mindset in this new context going forward.

I wrote this blog a short while ago: https://medium.com/@justin.holland/cultivating-quiet-38cec9466feb

I feel like there are other continuous improvement addicts, or perennial impostor syndrome sufferers that feel the compulsive need to be more than they are, and do more in order to reach that unattainable perfect state of being...

And I know that a bunch of us find ourselves in a state of constant information processing & overload... thanks to the infinite information we are exposed to every day.

I have also come to believe this can be super unhealthy, and that there is something fundamental that we are losing, thanks to our perpetual busyness.

Some come and have a little chat, and reflect, about the role of not doing... and instead... being... (quietly)

Given that Kanban is more than just "Post-its on wall", getting started is often misunderstood and leads to shallow implementations that don't give you much bang for your buck. In this talk, I will give you a brief introduction of how to get a Kanban implementation underway effectively using a technique that has been tried and tested worldwide. We will look at STATIK - the "Systems Thinking Approach to Introducing Kanban". As we unpack it, you'll see that it can be very helpful in getting your Kanban system started in the right way and will help guide the conversations that you need to have to get started.

The easy case for coaching looks something like this: a prospective coachee wants to change, can articulate their goals, and is matched up with a suitably experienced and competent coach, the two are a good fit, and they quickly get down to the challenging yet rewarding business of growth and change.

But what if a person (or team) doesn't want to change and would rather not be coached? And despite this an external power deems that change is needed and that coaching will bring this change about. What's a coach to do? What about the coachee(s)? What about the role of the client who's engaged the coach?

This situation is not uncommon, and bears more that a passing resemblance to what often goes on in addiction treatment. A person with a drug addiction (and often other problems) doesn't necessarily welcome therapeutic intervention at the outset. But an external authority has ordered it.

In this session we will explore the parallels between the two modalities of addiction therapy and coaching, including the applicability of the Transtheoretical Model of Change and the related technique of Motivational Interviewing.

These approaches offer insights into how to flex and adapt your coaching approach in the face of some of the most common human impediments to change.

Agile is now all grown up and is pretty much the de facto way of working for most teams, but it's proven to be a challenge for adoption at scale. Over the last ten years or so there has been a lot of trial and error figuring out how to break through the cultural barriers, political resistance and technical hurdles that large organisations present. This panel of luminaries (!) brings a wealth of experience helping many different types of organisations transform themselves to be fit for purpose in the 21st century. Come along to hear their stories, some good, some bad and probably a few ugly ones!

PLEASE NOTE: this session will be recorded live by The Weekly Reboot podcast and made available for public consumption. Your attendance will be taken as acceptance to being recorded and publicly broadcast.

Using Origami, attendees will see how flow can work in a "pull system" and compare that to the way it responds to a "push system". From this simple simulation, attendees will experience how increased WiP actually slows down our ability to deliver something to a customer.

Come along and experience flow and how you can start to improve your customer outcomes, not by doing more but by doing less!

Agile was coined in 2001, building on techniques and methods from the prior 10 or more years. We know that (smaller) software projects are more successful with agile delivery methods than with staged approaches like the SDLC. So why is it that 18 years after a better was was identified that managers struggle to adopt agile in a meaningful way.

This is a facilitated discussion - there are as many answers as there are people! So with the late afternoon timeslot - let's get together and have an interactive chat - with the intent that we all leave with some useful ideas, tools and techniques that we can apply when we get back to the office ...

At Myer, we’re well into our digital product journey. Although we still have plenty of work to do, we would like to start sharing our experiences in taking a Product centric approach to ensure we are delighting our customers and leveraging L.A.S.T practices to change behaviour and enable a positive outcome.

In this discussion, we will look at where we started, where we are now, and what our future path might look like. Our hope is that we can help others avoid (or at least identify) some of the more common pitfalls, and to help others develop a proactive approach to navigating their digital product journey.

Some topics for discussion may include:
- How we are working on creating a Product-centric organisation, and why this is so important.
- How focusing on the work that feeds the backlog(s) is just as important as the backlog(s) them self.
- Experimenting with the Google '20% time' practice, and how this helps create a trusting and inclusive environment.
- Constantly questioning the value of ideas, and initiatives. Like many organisations, there is no shortage of great ideas, but how do we make sure we are working on the most valuable ​at any given time?
- What happens without a strong product organisation? For example, what happens when there is no product guidance for UX. Now that we are working on building out our Product practices - how can we ​start to develop a healthy tension between UX and Product?

Experiences shared by Alexis Stuart, Digital Product Owner and Bob Martin, Agile Practice Lead.

API development is fun! Everyone is doing it, from large organisations wanting to provide developer access to their systems, to small websites wanting to push web application business logic to the browser.

Password security is boring. It's also harder than you'd think. The number of reported system breaches is on the increase, with big names being hit by hackers.

And when it comes to a service-oriented architecture, you have to secure multiple services. That's just tedious.

There are a number of solutions, but few that let you pretty much forget about security and access control.

In this talk and demo, Ben will show how using a third-party identity management system will allow you to ramp up your prototypes and MVPs with more ease, and to concentrate on the core purpose of the APIs, rather than the layers of security that are a must in today's digital world.

In this talk Ruma and Jay will share seven habits of highly effective teams, based on their work at Envato. They'll also share some tips to help build the habits.

Value is often used when designing and deciding on what work to do next. It’s central to both Agile and Lean principles. Together we will explore the question of value and challenge each other on what it is and how we use it?

After defining some language around value and looking at some possible models on how it can be used, we will jump into a group exercise to dig deeper to uncover gaps in our mental models and gain new insights into what this value thing is and how we can use it more effectively.

Story (or, more accurately, capability) slicing is such a core and necessary practice for creating agility at team, portfolio and even organisational level. Yet it is not explicitly included in any of the popular methods and frameworks teams use such as XP, Scrum and Kanban.

Slicing heuristics are collaborative, contextual, evolving techniques for creating focus on value-generating activities, leading to delivering value sooner and with more predictability. They incorporate all of the 4 core agile values from the manifesto, and many of the 12 principles, particularly:

• continuous improvement (inspect and adapt),
• maximising the amount of work not done (simplicity and focus)
• face-to-face conversations
• continuous delivery of value

Best results are obtained if heuristics are applied for all types of work, by all of the folks collaboratively across the value chain, but they can be used as safe-to-fail experiments by individuals and groups wherever they sit in the product delivery pipeline.

From a practical perspective, they involve:

• slicing deliverables at all levels, not only "story"
• flow metrics (cycle times and variation)
• specific inspect and adapt / continuous improvement activities to improve speed-to-market and predictability
• big visible boards (ideally)

Come and learn about this powerful, practical approach to improving agility in your team or organisation from wherever you sit right now.