So you walk into a new company, get the lay of the land and then realise, crap! Their development processes are like they were design by a bunch of first-year uni students doing a group project.

There is no DevOps to speak of. There are snowflake servers everywhere. Their git branching strategy is unmanageable. They run tests only every 3 or 4 releases. Their deployment is manual and different for each release. The have no real alerting.

Ok. Take a deep breath! Calm down.

So much to do, but where to start? The business has produced a list of improvement actions, but those actions are focussed around fixing the symptoms of the problems, not solving the root cause. The business does not understand that the path to DevOps improvement is complex and each task has many inter-relations and dependencies.

This is the problem that I faced about a year ago. To overcome this, we went through a process of defining all of the DevOps tasks we could think of and mapped them into a dependency diagram. This diagram was useful to communicate both internal and external to the team.

In this case study, I’ll go through the process to design the dependency diagram, but also our progress through the diagram one year later.

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.

A couple of years ago Christiaan Verwijs and Johannes Schartau coined the term ‘Zombie-Scrum’. What's it all about?

Well, at first sight Zombie Scrum seems to be normal Scrum. But it lacks a beating heart. The Scrum teams do all the Scrum events but a potential releasable increment is rarely the result of a Sprint. Zombie Scrum teams have a very unambitious definition of what ‘done’ means, and no drive to extend it. They see themselves as a cog in the wheel, unable and unwilling to change anything and have a real impact: I’m only here to code! Zombie Scrum teams show no response to a failed or successful Sprint and also don’t have any intention to improve their situation. Actually nobody cares about this team. The stakeholders have forgotten the existence of this team long time ago.

Zombie Scrum is Scrum, but without the beating heart of working software and its on the rise. This workshop will help you understand how to recognise the symptoms and cuases of Zombie Scrum and what you can do to get started to combat and treat Zombie-Scrum. Knowing what causes Zombie Scrum might help prevent a further outbreak and prevent the apocalypse

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!

This is a practical workshop where the participants will work in two sprints to build a city using the material given to them.

The intention of this workshop is for people to understand all the ceremonies better and it also helps teams understand that collaboration and working together as a team is the best way to achieve the results.

This is going to be a very interactive workshop while teams get to learn Agile while having fun.

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.

Hearing a lot about Objectives & Key Results (OKRs), but still a little unclear what they're about? Maybe you're hearing all the chatter and it's tweaking your interest! Well, join me for a farside chat and all will be revealed.

In this session we'll get under the hood of OKRs to understand the history, the core concepts and cut our teeth in a manner which allows us to take them back to our teams for further exploration.

At minimum, you'll walk out of the session with some clear goals for the coming quarter!

Do we know our stuff?
OKR Quickstart coaches and consults businesses on how to create strategic clarity, achieve audacious goals and build high performing teams. We've helped hundreds of people and businesses introduce OKR so that everyone finds crazy value out of them (not just the exec team). We've made every mistake in the book and this session summarises some of our biggest learnings!

What could it be like to work through a real-life security incident at your company? As awareness about security in our industry improves, we hear much about how to keep our applications secure, but rarely do we consider what happens with your employees when something goes wrong. Allow me to share my story about the emotional highs and lows of working through a security incident, as we look past its technical surface and into the human experience behind it instead.

Does the question "Can I give you some feedback?" strike fear into you? You're not alone! We've probably all been on the receiving end of what someone has called feedback but which we know is anything but. We may well have also been given the proverbial "sh*t sandwich", which most certainly is not palatable! This sessions aims to remedy the situation by examining what feedback is truly meant to be and how to apply it appropriately.

Feedback is all the rave with both management and Agile, yet it is so poorly understood and, unfortunately, so badly practiced. We know for organisations and individuals to grow that feedback is essential, but we rarely stop to reflect on how to do this effectively and in a considerate way.

This session will explore the fundamentals of what is genuine feedback, why it is valuable, and where, when and how to provide it in a way that creates desirable outcomes.

Using a simple model of feedback, we will share personal experiences where feedback has and hasn’t worked, and the learning obtained from these situations. With some light role playing, we’ll also experiment with the delivery of feedback, exploring the patterns and anti-patterns of common scenarios you may encounter in the workplace.

This presentation will have a close look at what makes high performing software development teams, as well as what hinders them. It will cover each level of the organisational hierarchy starting at individual software developer, then group of engineers, full cross-functional product-engineering team, wider product-engineering department, and finish at the entire company. At each level, we will see multiple examples of teams to see what factors contribute to high performing software teams, as well as less performant teams.

Seeking to understand how you can be a change agent in your organisation beyond Agile Team Coaching?

At this interactive session we’ll explore the world of Enterprise Agile Coaching.

Learn how to:

1. Radically interrogate your organisation’s reality
2. Diagnose the reinforcing behaviours affecting change in your organisation
3. Uncover the stories folks tell themselves that limit change
4. Implement a lean change model to fuel Agile adoption

An interactive session where we’ll play a short version of the Kanban pizza game to demo how you can supercharge your team to see great flow of work.

We’ll explore classic limiters to flow and how you can overcome these.

Expect to:

• Delve into the world of Kanban in a non-scary way
• Understand how to become a waste removal superhero
• Learn three easy metrics to fuel your team’s continual improvement

Facilitation is among the most important skills for Scrum Masters and Meeting Leaders. This highly interactive 45 minutes workshop session intend to provide any individual with an understanding and a toolset to create and structure their own meetings and workshops. Master the art of facilitation in only 45 minutes.

As a coach there are natural tensions that come into play as you execute your role to affect the system of work, influence culture and change behaviours. The EGDE that good coaches are able to find allows them to navigate these tensions whilst maintaining the balance of stance in the moment that the situation requires.

Think of seeing the "trees versus the forest" but on multiple levels/layers concurrently. Being an actor on the stage versus maintaining distance from the system of work (being in the audience).

In this workshop I will take the audience through some of the tensions I've recently experienced and navigated as a coach and how I have assisted other coaches to learn this skill and how you can develop it yourself.

I've been lucky to work with some of this city's most skilled of agile coaches scrum masters and agileists. More often than not group sessions are lost to the more mechanistic aspects of facilitation. The straws and lego become the focus instead of impacting the hearts and minds of those participating.

In this brief but jam packed session I'll will convey a brief deconstructed view of 5 key themes for what makes facilitations stick.

I will share with you what they don't teach in agile, coaching or even workplace training certifications.