With so many changes coming to organizations - agile, devops, products, etc - how do you learn these new practices and apply them in your context with your constraint? Enter the dojo - an immersive, team based learning environment where teams come together to learn and apply new skills to their work.

How do you grow a continuously learning organization? If certifications and wikis were enough, organizations would be crushing it. In this session we look at how we learn in complex domains - focusing on tacit vs explicit knowledge; context learning; and growing coaches and teachers.

This session is an evolution of our talks around growing Dojos (though awareness of dojos is not necessary for this talk).

In this session we will look at the challenges facing organizations and people today trying to learn new skills (committment, context, multitude of needs).

From there we will look at how we learn exploring explicit vs tacit knowledge.

We will wrap up with tangible ways you can start growing an organization that continuous learns - looking at addressing the whole value stream to provide context and growing an organization that has internal coaches and teachers (along with models for that).

Metrics are the bane of many organizations, getting fascinated on measurements that don’t matter or can drive improper behaviours. In this session, we walk through a simple grouping for metrics where the groupings not only call out the metrics, but their limits, and help guide to better metrics.

Metrics are the bane of many organizations, getting fascinated on measurements that don’t matter or can drive improper behaviours. In this session, we walk through a simple grouping for metrics where the groupings not only call out the metrics, but their limits, and help guide to better metrics.

How do you grow a continuously learning organization? If certifications and wikis were enough, organizations would be crushing it. In this session we look at how we learn in complex domains - focusing on tacit vs explicit knowledge; context learning; and growing coaches and teachers.

Product Thinking - understanding the use and need - is critical to not over engineering a product. In this session, we explore and use simple tools that help teams blend architecture with the need of the product.

Metrics are the bane of many organizations, getting fascinated on measurements that don’t matter or can drive improper behaviours. In this session, we walk through a simple grouping for metrics where the groupings not only call out the metrics, but their limits, and help guide to better metrics.

In the DevOps Handbook, Gene Kim introduces the Third Way - The Technical Practices of Continual Learning. Enter the DevOps Dojo - an immersive environment where whole teams come together to learn and practice their skills while solving real business problems.

Joel Tosi and Dion Stewart say teams learn better in the immersive eco-system of Dojos than they do using traditional forms of training. They explain why and how Dojos help teams bond around product, foster rapid experimentation, and reframe small failures as learning.

In this session, we will frame the need for dojos. From there we will walk attendees through the dojo format, including things they need to think about when creating their own. We wrap up with simple calls to actions for people to take to bring learning forward.

Come to this session not only to learn about what works in creating a Dojo but also how Dojos help upskill your teams and support the cultural DevOps change.

How do you grow a continuously learning organization? If certifications and wikis were enough, organizations would be crushing it. In this session we look at how we learn in complex domains - focusing on tacit vs explicit knowledge; context learning; and growing coaches and teachers.

Too much design up front and you are bumping into the design all of the time (and losing time). Not enough design and your system can crumble in reality. How do you blend architecture so you have the right decisions at the right time, and give them enough due dilligence? How do you embrace cloud and microservices and not risk getting into different failure scenarios or overly complicated maintenance and ripple effects?

In this session we will walk through visualizations that help teams blend product thinking with architecture. Along the way, we will look at microservices and domain modeling as well as chaos engineering and fault tolerance - blending all of these into a context that is consumable by all and gives the right emphasis at the right time.

Leave this session with simple visualizations and approaches that you can apply immediately to start blending product with architecture, especially if you are looking to run in a cloud world.

In this hands on workshop, teams (4-5) will use Product Chartering, Personas, Storymapping, and User Journeys along with Experience Tests to explore a product of their choice.

Along the way we will touch on how you blend architecture needs into this as well as chaos engineering - especially if the audience is more technical

The takeaways are hands on approaches to product discovery and how it blends into delivery

How do you grow a continuously learning organization? If certifications and wikis were enough, organizations would be crushing it. In this session we look at how we learn in complex domains - focusing on tacit vs explicit knowledge; context learning; and growing coaches and teachers.

This is an extension of our talks on Dojos - immersive learning environments.

As a scrum master, manager, or director, you are looking for meaningful ways to measure progress or success with your product or change initiatives. These measurements can't just celebrate success, they need to expose reality and help you make decisions. You've read about the fallacies of measuring velocity or trying to compare teams - but what else can you do? The DevOps space talks much about mean time to recover, but is that making a difference?

Metrics are the bane of many organizations, getting fascinated on measurements that don’t matter or setting goals that drive improper behaviours. In this session, we walk through a simple grouping for metrics where the groupings not only call out the metrics, but their limits as well, and help guide us to better metrics.

Leave this session with a simple structure for metrics along with a plan to get you to more impactful metrics.

Product transformations, cloud native, agile practices, design thinking - so many concepts to learn and apply. Many organizations struggle with making one practice stick or, even moreso, transforming their organization into a learning organization where experimentation is the norm. We know that in knowledge work, ideas cannot just be codified and transferred but rather need to be experienced. Courses are great but are challenging to bridge over into the constraints within an organization.

Enter the DevOps Dojo - an immersive environment where whole teams come together to learn and practice their skills while solving real business problems.

Joel Tosi and Dion Stewart say teams learn better in the immersive eco-system of Dojos than they do using traditional forms of training. They explain why and how Dojos help teams bond around product, foster rapid experimentation, and reframe small failures as learning.

In this session, we will frame the need for dojos. From there we will walk attendees through the dojo format, including things they need to think about when creating their own. We wrap up with simple calls to actions for people to take to bring learning forward.

Come to this session not only to learn about what works in creating a Dojo but also how Dojos help upskill your teams and support the cultural DevOps change.