Many organizations are using DevOps to speed the ability of organizations to gain value from the software investments.  Too many organizations attempt to reduce DevOps to just a series of technical tools and practices. Organizations to address organizational and cultural issues in order to effectively bring development and operations groups together.  In this section we will present a play to illustrate how DevOps requires communication and understanding to be successful.

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

Outline/structure of the Session

We will present a short scene depicting a development and an operations organization working as separate groups with distinct, misaligned objectives.  They will make an initial attempt at DevOps by adding a continuous deployment tool, but it does not work as they expect.  Finally, they will talk to each other and will each change their practices in order to fully realize the DevOps vision.

Table discussion about what differed in the three scenes of the play, and why that made a difference.

Share table discussion with the larger group

Table discussion about what kinds of communication (or lack thereof) that folks have seen in their own organizations attempting to start DevOps

Share table discussion with the larger group

Wrap-up with a presentation of our thoughts on how the development and operations groups can collaborate more effectively.

 

Learning Outcome

Participants will learn to look for and address the organizational and cultural issues required to be successful with DevOps

Target Audience

DevOps Practitioners and Management

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked David Bulkin
    keyboard_arrow_down

    Build Righter Stuff with HDD (Hypothesis Driven Development), a.k.a., HDD is TDD for the Business Case

    David Bulkin
    David Bulkin
    Managing Director
    Grow-Lean LLC
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    With TDD (Test Driven Development) a coder writes a small test, and then just enough code to make the test pass, cleaning up the code along the way.  Imagine applying the same concepts to the business case.  Now stop imagining and use HDD (Hypothesis Driven Development) to test your business case and refactor it for success.

    Our hands on session will cover the basics of ATDD (Acceptance Test Driven Development) and BDD (Behavior Driven Development) to specify by example, so all stakeholders get on the same conceptual page, developers build what the business really wants, and testers can prove it. 

    But building what we want it not enough, so we will go further and use HDD to validate, or invalidate, business outcomes, focusing us on value instead of on adherence to specification.

    This is a hands on session, so come with pen, paper and a readiness to learn by doing!

  • Andrea
    Andrea
    Agile Coach
    Santeon
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Project success =  f (listening, feedback, intentionality, practices) 

    To make your agile practices and processes come to fruition, you need to cultivate an environment that promotes listening, learning, inquisitiveness, intentionality and top notch feedback that everyone is comfortable with. 

    Agile projects succeed when there are frequent high-quality reinforcing feedback loops. I will share communication models based on Clean Language questions of David Grove and the Systemic Modelling techniques of Caitlin Walker that can greatly increase clarity, sense of purpose and listening skills within your team and collaborative endeavors.  These include: Clean Questions, Clean Feedback, and Clean Setup.

    This is a hands-on, try it out, concrete practice session.

  • Liked Shawn Faunce
    keyboard_arrow_down

    Engaging a Product Owner on a Government Contract: Challenges and Solutions

    30 mins
    Talk
    Beginner

    Great systems require active, capable Product Owners.  Functional innovation is not possible without their commitment and involvement in the project.  Too often in government contracting, the Product Owner is an Absentee Owner.  Agile Development teams often seek out tools and techniques to create great systems, however too frequently what is holding them back is the lack of an engaged Product Owner. Teams in this situation must face the elephant in the room if they desire to build a system that brings positive change in efficiency, productivity, quality, usefulness, and adoption.  This talk shares solutions I have used for challenges I see again and again on government contracts.

    The talk begins with some introductory material on the problem, its causes, what I mean by functional innovation, and why this is required to build great systems.  I describe four challenges with Product Owner engagement that are not unique to government contracting, but that I see recurring on projects: committing staff, procurement practices, role ambiguity, and absentee ownership.

  • Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    So what does Collaboration really mean?  It's just ensuring people understand what each other is doing right?

    The Power of 13 Collaboration Game illustrates what true collaboration means.  We'll do work by rolling dice over a 3 week Sprint. We'll then explore the results and start our next Sprint. In each Sprint, we're going to increase the participation across players and see what the effect is on productivity.  Prepare to be surprised!

    Should there be enough time remaining in the hour; we'll then specifically apply true collaboration to better understand the effects of pair programming by playing Pair Poetry.  This simulates the power of pair programming and demonstrates why the one screen, one keyboard concept works.

  • Jason Tice
    Jason Tice
    Agile Coach
    Asynchrony
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Agile and Lean principles call for teams to delay decisions and activities until the “last responsible moment” so as to minimize rework and waste.  While this sounds good in concept, sometimes teams fall victim to waiting until it is “too late” to make a decision or get started on a needed activity resulting in missed opportunities and/or down-to-the-wire heroic efforts to meet a deadline.  This workshop entails a competitive LEGO simulation where participants will divide into small teams, each team will be given the same simple LEGO build challenge, and then each team will be able to conduct their own experiments as to when the “last responsible moment” really is.  Following the LEGO build challenge, participants will engage in a debrief to discuss the outcome of the challenge, identify factors that helped to successfully identify the last responsible moment, establish linkages between the LEGO simulation and agile software development activities, and of course congratulate the winners of the challenge.  During the debrief, participants will complete a debrief worksheet to reinforce key learnings and takeaways from the simulation that they will be able to take with them from the session.  Best of all, this is a LEGO session, so you will get to play with LEGO and fun will be had by all!

  • Liked David Kane
    keyboard_arrow_down

    Making Movies and Software at the Speed of Thought!

    David Kane
    David Kane
    Senior Agile Coach
    Santeon Group
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Director Robert Rodriguez (Spy Kids, El Mariachi, Sin City) is an Agile Director. He enjoys making highly creative movies quickly and cheaply. His ambition is to make movies at the speed of thought. To achieve this goal, he works in small teams to develop the ideas, visualize them quickly, shoot the movie fast, and build the movie in layers. This workshop will introduce Rodriguez's approach to film making by screening several of his 10 minute flick school featurettes and we will explore how these techniques translate to Agile software development in a lively group discussion.

  • Liked Philip Rogers
    keyboard_arrow_down

    Lean Coffee: Creative Uses of this Technique to Rapidly Surface Ideas and Encourage Team Collaboration

    Philip Rogers
    Philip Rogers
    Scrum Master
    NPR
    schedule 2 years ago
    Sold Out!
    30 mins
    Workshop
    Intermediate

    Lean Coffee is frequently used in meetup and conference settings. The beauty of Lean Coffee is its simplicity, and it is this very simplicity which makes it an appealing choice in various Agile team contexts. Specifically, Lean Coffee is particularly good for ad hoc training sessions and for retrospectives. The focus of this workshop will be on the use of Lean Coffee in these two types of settings, where we will split up into small groups and practice using Lean Coffee to cover ad hoc training topics and to do a mini-retrospective.

     

  • Liked Alexei Zheglov
    keyboard_arrow_down

    Lead Time: What We Know About It and How It Can Help Forecast Your Projects

    60 mins
    Tutorial
    Intermediate

    The session is about just one metric, but a very important one - lead time.  Simply put, lead time is the time between the start of work and delivery.  And there is a catch: if the work has to wait in a queue or if we switch from it to work on something else, the clock keeps ticking until we deliver.  Lead time has proven to be a difficult metric to game.  Even when people try, they often end up delivering faster, with less delay - win-win.

    We will look at examples of real-world lead time data for several different types of work from different companies.  We will discuss the very recent new insights into lead time distirbutions.  Those will then lead us to building useful probabilistic delivery forecast models for your process.  Building such models is surprisingly easy and takes surprisingly few data points.  The models, in turn, enable better decisions.

    Are your ready to embrace the probabilistic approach?

  • George Paci
    George Paci
    Agile Coach
    Santeon
    schedule 2 years ago
    Sold Out!
    30 mins
    Talk
    Intermediate

    Agile planning tools started simple: index cards, markers, and a table or wall. On many projects, for many reasons, these old stalwarts have been supplemented (or even replaced) by software solutions: Rally, VersionOne, Jira Agile, Trello, Trac, Scrumy, and literally dozens more, even BaseCamp. These tools have undeniable advantages over cardboard and ink in some aspects, but they're not superior in every situation.

    This session will highlight the pitfalls of centering planning meetings around software tools—even the best ones, like [your ad here]—and make a badly-needed sales pitch for index cards on a wall (compensating for Oxford's oddly anemic marketing effort). You'll see how cards can make better use of your team's time and brainpower, promote parallelism in meetings, and increase engagement by all participants.

  • Liked Shannon Ewan
    keyboard_arrow_down

    The Art of Facilitating Agility

    60 mins
    Workshop
    Intermediate

    From an agile implementation perspective, emphasizing the art of facilitation is an incredibly powerful tool for creating a culture of collaboration, and then leveraging that culture as a springboard to organizational transformation.  With strong facilitators at the gateway between business and IT, within IT delivery teams, and at key intersection points within an organization, the challenges to achieving organizational agility diminish. Strong facilitators bring forth the wisdom of teams and provide a container for self-organization. Facilitation is the cornerstone of servant leadership. 

  • Liked Richard Cheng
    keyboard_arrow_down

    A Roadmap for (Agile) Engineering Best Practices – What Every Non-Technical Person Needs to Know

    Richard Cheng
    Richard Cheng
    Principal
    Excella Consulting
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Beginner

    Summary: Presenting a roadmap explaining engineering best practices, why it’s needed, supporting tools, level of effort to implement, and sequence for implementing.

    21st Century IT development requires building quality into our development practices yet many software teams fail to implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Without these practices, the quality of software goes downhill and teams can no longer sustain their initial high levels of productivity.

     

    However, understanding and implementing the practices can seem daunting.  This session presents an easy to understand roadmap for implementing engineering best practices.  The roadmap explains what the practices are, the tools that support the practices, a recommended sequence to implement, and effort to implement.

     

    Though this topic is about engineering best practices, attendees do not have to be technical to get value from this session.  The session gives a non-technical look at a technical concept and is great for any person in the organization managing, working with, or working on IT teams/programs.

     

     

  • Liked Derek Huether
    keyboard_arrow_down

    At home and work, how to get more stuff done. An introduction to Personal Kanban

    3 mins
    Workshop
    Beginner

    With a world of constant distraction, it feels like it’s getting harder and harder to get stuff done, regardless if it’s on a personal or organizational level. At some point, we’ve been sold the lie that multitasking is great and maximum utilization is even better. If we all agree with that, why are we doing more and getting less done? If there were a relatively simple way for you to get more stuff done, wouldn’t you want to know what it was? If there were a way for you to measure and improve your processes over time, wouldn’t you want to know how to do that as well? When getting stuff done is a primary measure for success, we need to introduce people to concepts that are simple but can be leveraged at scale.

    In this session, participants will be introduced to the principles of Lean and the application of Kanban to visualize their personal work, limit distraction and waste, and get stuff done. I’ll cover the core concepts outlined in Jim Benson and Tonianne DeMaria Barry's book, Personal Kanban, to get you started. I’ll talk about how Kanban can be applied to everyday work and why you should do it. 

    Through my years of struggling with ADD/ADHD and my years of management, leadership, and coaching, I have learned and applied Personal Kanban techniques in my everyday life and Lean Kanban at both government and private organizations. This is your opportunity to learn a few simple strategies that you can start using before you even leave AgileDC. This workshop can help you map your work and navigate your life.

  • Liked bchaplin1
    keyboard_arrow_down

    Minimizing Technical Debt Via Agile Metrics and Techniques

    bchaplin1
    bchaplin1
    Metrics Architect
    Chaplin Solutions
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Automate and mine those code quality statistics from Sonar and use Agile techniques to transform your team and codebase!

    Studies show that poor code quality can cut your velocity in half as early as the second release.  But there's hope.  Yes, you can make your deadlines and still have little or no technical debt.  

    Using proper metrics 50% of the 100 committing developers had no tech debt and 100% test coverage for all their code submitted in 2013.  

    Use key code quality metrics to manage your team's quality and ensure your second release is just as productive as the first.    

  • Liked shentonfreude
    keyboard_arrow_down

    Making a Better Salad: Behavior-Driven Development with Lettuce

    30 mins
    Tutorial
    Intermediate

    Is your organization still using brittle GUI driven-tools to ensure applications can be tested? Do you find these difficult to map to the user stories that describe product owner/business needs? One of the current Agile practices to doing this is Behavior-Driven Development (aka Acceptance Test-Driven Development) and writing user stories and acceptance criteria in a Specifications by Example format.  This has real power in that business people can understand the tests and the delivery team can ensure the code meets the tests, thus they serve as an example.

     

    This tutorial will give a short background on Specs by Example/BDD and the show you how to write such tests in Lettuce.  You will gain a deeper understanding of how you can apply this to writing your applications.

     

  • 60 mins
    Workshop
    Beginner

    Many agile initiatives suffer from a feeble launch.  As Aristotle once stated “Well begun is half done”.  Performing the activities associated with developing a sound charter can help increase the likelihood of success for a team or organization .  

    Beginning with the end in mind, we use retrospective techniques to develop consensus around objectives, vision, and mission.  In this workshop we introduce the components of a good charter and how those components help focus the teammates toward a common goal.  In addition, the development of the recommended charter components ensures that key questions are succinctly answered during the kickoff of a team.

    Participants will learn the various types of charters and their recommended content.  During the workshop activity teams will develop a complete charter based  team of their choice or a provided case study.

  • Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 2 years ago
    Sold Out!
    3 mins
    Talk
    Intermediate

    Creating an approach for change is difficult. There is a fine line between imposing an Agile adoption and creating a Transformation where people are collaboratively working together for the change. Based on my experience and in large US Federal Government organizations where imposed adoptions seem the norm, I’ve been working on combining many concepts into a transformation model that can work for large organizations that have ingrained cultures. This starts by helping the organization’s people take ownership and personalize what Agile means to them. Believe it or not, this can work.

    Intended for senior executives and their immediate staff (and the coaches that help them), the Taking Flight approach presents the importance of culture and how creating an organizational aspiration will help guide people. For large organizations, culture has been built up over decades and changing this is of the utmost importance to have an Agile Adoption stick. There are 3 main points I’ll address:
    - how to get people ‘onboard’ with a cohesive direction that they accept by collaboratively building their aspiration
    - how to develop and select strategies for incremental improvement towards the aspiration
    - how to realize changing from old routines into new ones aligned with the aspiration

    To help establish cohesive direction, I use an Aspirational model (your Guiding Star) to help organizations develop the direction they want to go. I show how the differences between an Aspirational model and an End-State. I explain that aspirations are inspiring and allow for a mindset change by not expressing the final state in terms of structure our expected metrics. From there, I discuss different techniques for assessing the current state of the organization and its people and developing strategies and actions for the necessary change management to move towards the organizational Aspiration; this is where the concrete steps come into play. Throughout this portion, I have the group try out various techniques for building an aspirational model and how to build the backlog of work to undertake the transformation. I introduce the Power of Habit as a means to help the organization undergo the necessary behavior changes. I close with a discussion to help the audience think around limiting change-in-progress and how to grow capacity to become more responsive to change.

    In this, you’ll get exposed to a few of many hands-on techniques that can be used to develop your Aspiration and execute on it. These are:

    • KrisMap
    • Business Model Canvas
    • Habit Loops
  • Liked David Kane
    keyboard_arrow_down

    The Role of Architecture in Agile Development

    60 mins
    Workshop
    Intermediate

    In large Government and Commercial organizations with many interacting systems, architecture is necessary to collaborate effectively across disparate entities and systems. Traditional command and control approaches to architecture are often ineffective and cause great tension, especially when Agile efforts are part of the portfolio. We will discuss two principles, Vision and Partnering.  These principles provide insight and get results for both architects and Agilists; and present tools and approaches on how to effectively engage architects and architecture.

  • Liked Mark Grove
    keyboard_arrow_down

    Four Easy To Adopt Agile Metrics for Teams Just Getting Started

    60 mins
    Workshop
    Beginner

    Using metrics to track agile team performance can be an important tool to reinforce the need for continuous improvement. Metrics can serve as valuable input during retrospectives, the daily standup, and sprint planning allowing teams to continuously adapt their practices and performance based on the observed patterns the metrics reveal. In our experience, many new agile leads and teams are not sure which agile metrics would be the best metrics to begin using. Some teams may be tracking various data points, but lack the skill and understanding of what the metrics are actually revealing and how the teams can use this information to self-improve.

    Our presentation/workshop introduces four "light-weight" agile metrics any team can easily adopt and begin using immediately. They are: Velocity, Comitted vs. Done, Sprint Build-up (Burn-up), & Cycle Time.

    We introduce each of these metrics and explain what each one measures, how to obtain the data, and when it should be updated. But most importantly, our presentation provides a workshop component where we provide sample scenarios for each metric. These scenarios represent possible real-life data patterns teams could experience. In the workshop, we ask the audience to work in small groups to consider what each scenario may be representing and what they would do, in the spirit of continuous improvement, to respond to these patterns. We also discuss with the audience how to use the metrics in tandem to help provide a more robust interpretation of team performance.

    We realize there are many agile metrics teams can adopt. However, for teams just starting out we recommend these easy to use yet powerful metrics to help teams monitor and assess team performance.

  • Liked Paul Boos
    keyboard_arrow_down

    Understanding the Relationship of Optimization, Prioritization, Throughput, Impediments, Métier, Utilization, and Sizing

    90 mins
    Workshop
    Intermediate

    Some of the key aspects of successful Agility are slicing our work into small chunks, prioritizing this work, and having our people pull the work at a rate they can sustain.  How do we do that? What does limiting work in progress mean? Is it more beneficial to have people working across stories individually or swarming on stories? What is the effect when specialists have to work on specific stories due to their unique skill sets? Why do we slice stories? When we choose to not have people remove impediments, what impact can that have?

    This session will immerse you in a simulation of what a team goes through when pulling work in an iterative approach such as XP or Scrum.  It was created in response to seeing teams make poor choices in what they optimizing; often choosing to optimize the utilization of resources as opposed to maximizing the effectiveness of the people.  This team also had chosen an architecture where specialized talent was hard to come by, limiting the overall effectiveness.  

    We'll explore what prioritization does for us; how limiting work in progress and slicing stories helps in getting us to done. We'll introduce impediments and make choices whether to work on something else or work to remove them.  We'll introduce a specialist and see what the impact of that is. 

  • Liked George Paci
    keyboard_arrow_down

    Lean Software Development: Principles and Tools

    George Paci
    George Paci
    Agile Coach
    Santeon
    schedule 2 years ago
    Sold Out!
    30 mins
    Talk
    Beginner

    Lean Software Development, largely created and popularized by Mary and Tom Poppendieck, is a set of principles and tools for approaching software with a value-focused mindset.  Heavily influenced by Lean Product Design, itself the result of porting Lean Manufacturing insights over into the design realm, it can change the way you think about what you're doing and why.  Lean emphasizes the performance of the entire software-development system, and strongly cautions against optimizing pieces at the expense of the whole.


    This session will be a whirlwind tour through seven principles of Lean Software Development, and one thinking tool associated with each principle.  The common thread of focusing on value, instead of on requirements or process or utilization, ties the concepts together.