Although DevOps practices deliver incredible benefits to organizations looking to improve their software delivery practices, the larger positive impact of DevOps to delivering value is often harder to realize. A set of practices we’ve found to help organizations is something we call the 4 Maps of DevOps. 

Fitting nicely in between the 3 ways and 5 ideals, the 4 maps consist of Outcome Mapping, Value Stream Mapping, Dependency Mapping and Capability Mapping. They help you create a powerful roadmap that is outcomes-focused and targeted at the most important problems.

Through this talk, I’ll walk through the benefits these maps produce, how they relate to one another and the problems you can target with them.  I’ll go through some real-life examples of using these maps to help organizations.

This talk is for anybody who is struggling to work out where to start or where to go next with their adoption of DevOps.

This talk is about my journey to become an ICF certified coach and how I apply those skills both to my role as a strategy consultant and business leader.

Coaching is a powerful discipline that differs from mentoring, teaching and consulting. Applied correctly it can help you have better, more powerful conversations and allow you to overcome difficult challenges.

I'll talk through the skills what I learned and where they align and differ from Agile coaching practices. I'll talk to the most powerful tools I learned that I now apply to all my work such as logical levels. Throughout this, I'll do a couple of simple exercises for the audience to take with them and use.

These skills are valuable to people at every level of the organization and equally, can be applied to all aspects of your life.

TACO is an acronym I use with clients to help them map controls from their software delivery pipelines to the organizational controls.

TACO stands for Traceability, Access, Compliance, and Operations.

The approach consists of a base list of 25 automatable controls that are documented and the control activity, artifacts and SOR identified. After mapping how these controls are handed we map them to the organizational controls and identify any gaps.

This model allows for the creation of opinionated pipelines and helps create a common understanding across teams as to what is required in order to be secure.

Taking a TACO approach can be considered a part of implementing a DevSecOps program and I’ve used this approach at multiple banks. I’ve given the base talk at three conferences and multiple times to internal teams. It helps build organizational confidence in the automation of software delivery.

During the talk, I’ll run through the different categories of controls, how they are implemented, what the purpose of them is, how to create robust feedback loops for controls such as SAST and how to handle long-running processes such as DAST.

Content is fairly high level but I can dig into specifics of each given area as questions arise.

This talk is about my journey to become an ICF certified coach and how I apply those skills both to my role as a strategy consultant and business leader.

Coaching is a powerful discipline that differs from mentoring, teaching and consulting. Applied correctly it can help you have better, more powerful conversations and allow you to overcome difficult challenges.

I'll talk through the skills what I learned and where they align and differ from Agile coaching practices.I'll talk to the most powerful tools I learned that I now apply to all my work such as logical levels. Throughout this, I'll do a couple of simple exercises for the audience to take with them and use.

These skills are valuable to people at every level of the organization and equally, can be applied to all aspects of your life.

TACO is an acronym I use with clients to help them map controls from their software delivery pipelines to the organizational controls.

TACO stands for Traceability, Access, Compliance, and Operations.

The approach consists of a base list of 25 automatable controls that are documented and the control activity, artifacts and SOR identified. After mapping how these controls are handed we map them to the organizational controls and identify any gaps.

This model allows for the creation of opinionated pipelines and helps create a common understanding across teams as to what is required in order to be secure.

Taking a TACO approach can be considered a part of implementing a DevSecOps program and I’ve used this approach at multiple banks. I’ve given the base talk at three conferences and multiple times to internal teams. It helps build organizational confidence in the automation of software delivery.

During the talk, I’ll run through the different categories of controls, how they are implemented, what the purpose of them is, how to create robust feedback loops for controls such as SAST and how to handle long-running processes such as DAST.

Content is fairly high level but I can dig into specifics of each given area as questions arise.