Designing a DevOps Dependency Diagram to Decide Development Direction

schedule Jul 30th 11:45 AM - 12:30 PM place EN101 L100

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.

 
2 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Case Study

A case study which will go through the process of designing the dependency diagram, and then walk through how we actually progressed through the diagram over the period of a year.

Learning Outcome

A deeper understanding of the complexities of improving the DevOps processes of software engineering teams, and some concrete ideas of how to go about doing this.

Target Audience

People who want to understand a bit more about how to improve the DevOps capability of a team.

Prerequisites for Attendees

A rudimentary understanding of the process of building software and getting it into production.

schedule Submitted 2 months ago

Public Feedback

comment Suggest improvements to the Speaker

  • Liked Ed O'Shaughnessy
    keyboard_arrow_down

    Ed O'Shaughnessy / Alexandra Stokes - The Good, Bad & Ugly: what we've learned in 10 years of scaling agile -- a panel discussion

    45 Mins
    Panel
    Intermediate

    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 and made available for public consumption. Your attendance will be taken as acceptance to being recorded and publicly broadcast.

  • Liked Jay Hyett
    keyboard_arrow_down

    Jay Hyett / Ruma Dak - 7 Habits of Highly Effective Teams

    30 Mins
    Talk
    Beginner

    Leveraging Stephen Covey's 7 Habits of Highly Effective People and the circles of control, influence and concern to improve the way people work together in teams.

  • Liked Chris Lewis
    keyboard_arrow_down

    Chris Lewis - The Human Side of a Security Incident

    30 Mins
    Talk
    Beginner

    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.

  • Liked Chris Chan
    keyboard_arrow_down

    Chris Chan - Growing your Agile Mindset by Overcoming Your Immunity To Change

    Chris Chan
    Chris Chan
    Adaptive Leadership Coach
    ANZ Bank
    schedule 2 months ago
    Sold Out!
    90 Mins
    Workshop
    Beginner

    Due to requests and feedback, this is a repeat of last year's session for those who missed it.

    How do you develop an agile mindset? You can't teach it, but you can grow it by changing your beliefs.

    In this session we will cover a brief introduction to the research by Kegan and Lahey where they discovered that behind each of our habits is a strongly held belief that not only keeps us in our groove, but also fights any change that threatens the status quo.

    We will discuss why personal growth and increasing our mental complexity is so important for agile and business transformations in today's VUCA world to succeed.

    We will create your Immunity To Change Map which is a simple way to bring to light the your personal barriers to change. We will start by outlining your commitment to an improvement goal. Then we will sketch out the things that you are either doing or not doing that prevent progress towards the achievement goal. The Map then identifies competing commitments, as well as the big underlying assumptions behind those competing commitments.

    The objective is to pinpoint and address whatever beliefs and assumptions are blocking you from the changes you want to make.

    You will leave this workshop with a better understanding and tools to overcome the forces of inertia and transform your life and your work.

  • Liked Mark Grebler
    keyboard_arrow_down

    Mark Grebler - High performing software engineering teams: how to grow then and how to slow them

    Mark Grebler
    Mark Grebler
    Head of Engineering
    Focus HQ
    schedule 2 months ago
    Sold Out!
    30 Mins
    Talk
    Beginner

    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.

  • Aurelien Marando
    Aurelien Marando
    Agile Coach
    -
    schedule 1 month ago
    Sold Out!
    45 Mins
    Workshop
    Beginner

    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.