So you want to be a DevOps Engineer?

You’ve worked hard, you have mastered every coding language on the planet, including COBOL. You know jenkins, travis, go, containers, puppet, chef, CFengine, nagios, github, graphite, logstash, ansible, aws, gce, vagrant, cms, cvs, abc, 123, and even a little bit of TFS. Your resume is up to date, and you are ready for your next job.

Well, slow down there… Industry trends in engineering are showing a growing desire in companies to hire people who have proven soft skills, are good at collaborating with others, and can regularly solve the most complex problem we face today: effectively talking to our fellow humans.

Please join Jen for a self-effacing and situationally humorous conversation about the journey of becoming more comfortable with collaboration, open communication and reaching through “the wall.”

Topics will include:

  • “Collaborate or Die” survival skills
  • The dreaded “soft skills” and how to become comfortable with them
  • What to do in common situations all engineers face
  • How to convince others that your idea is the right idea
  • How do you get the time you need to get your work done
 
 

Outline/Structure of the Talk

  • Review where DevOps came from
  • Discussion on why it is important to know about it (e.g. what is the potential impact to your career)
  • Review the new skills that engineers will be required to know
    • Soft skills (communication, collaboration, resolving conflict, compromise)
  • Talk through common scenarios in engineering and how you can apply these skills to effectively resolve them
  • Review "home work" for practicing these skills

Learning Outcome

Primarily this talk focuses on what engineers need to know on how their careers are changing based on new trends in the DevOps & Agile space. This talk gives engineers tips and tricks on how to adjust effectively without too much burden, while also helping the younger generation embrace the newer skill set.

Target Audience

Engineers

Prerequisites for Attendees

N/A

schedule Submitted 2 years ago

Public Feedback


    • Talia Lancaster
      keyboard_arrow_down

      Talia Lancaster / Angie Doyle - T-minus 10… 9… 8… We have lift-off!

      90 Mins
      Workshop
      Beginner

      Getting new teams to work together is hard. Really. Hard.

      Is it because there is so much hype around new Agile teams? Or is it because there is such a focus on “doing things right” (or “doing” Agile right), that we forget about the people actually doing the work? Regardless of the reason, before we can change the way people work... we need to focus on the things that are important for teamwork to work!

      We believe that the key to high-performance teams is creating an intentional culture that respects and embraces diversity - whether it be race, gender, class, culture, age, beliefs, language, skills or background. So join us as we explore the Team Canvas – sort of like a Business Model Canvas for teamwork - covering nine essential teamwork elements:

      • Purpose - Why we are doing what we are doing?
      • People & Roles - What are our names, roles and responsibilities?
      • Common goals - What do we as a group want to achieve together?
      • Personal goals - What do I as an individual want to achieve?
      • Team values - What do we really stand for and believe in?
      • Needs and expectations - What do each of us need to be successful in a diverse team?
      • Rules & Activities - How do we communicate and keep everyone up to date?
      • Strengths & Assets - What skills do we have in the team?
      • Weaknesses & Risks - What are the weaknesses we have, as an individual and as a team?

      We will walk through our agenda for team lift-offs, facilitation posters and preparation work required, materials needed, and facilitation tips and tricks. All packaged in a handy pocket guide, that you can use to explore tried and tested techniques for each essential element. We will also have an opportunity to practice some of these techniques during the session.

      Get ready to lift-off your team in T-minus 10... 9... 8...

    • Tobias Anderberg
      Tobias Anderberg
      Developer/Coach
      Agical AB
      schedule 2 years ago
      Sold Out!
      45 Mins
      Talk
      Intermediate

      Ever wondered why some people prefer to work alone? Or why some people cringe when pair programming is mentioned? It might be that that person, like me, is an introvert. But is is really that simple? Can we really put every person in a box labeled "introvert" or "extrovert" or are we all just ambiverts?

      During this session I will talk about introverts, extroverts and everything in between.
      Drawing from almost 15 years of personal experience being an introvert on agile teams I will talk about the differences of being an extrovert
      or an introvert, how to foster an inclusive team environment, and the importance of psychological safety.
      You will hopefully leave this session better fit to help EVERYONE on your team to reach their full potential!

    • Jutta Eckstein
      keyboard_arrow_down

      Jutta Eckstein / John Buck - Using Beyond Budgeting and Sociocracy for agile-friendly performance appraisals

      90 Mins
      Workshop
      Intermediate

      There are many suggestions dealing with Agile-friendly performance appraisals, which promise to rely on trust, honesty, respect, safety, and servant leadership. The Agile Manifesto does not address performance appraisal although it does generally mention regular and frequent feedback, which can also be applied to performance evaluation. Two related methods, Beyond Budgeting and Sociocracy, offer interesting approaches to agile performance review. In this session we want to present these two different performance appraisal approaches, how they're are supported by the values of BOSSA nova (short for Beyond Budgeting, Open Space, Sociocracy & Agile) and want to invite the participants of this workshop to discuss the synthesis of the two approaches.

      This session looks at several real-world examples from actual companies including Accenture, Equinor, and Google.

      The first principle of Beyond Budgeting asks to “engage and inspire people around bold and noble causes; not around short-term financial targets,” the eleventh principle advocates: “Evaluate performance holistically and with peer feedback for learning and development; not based on measurement only and not for rewards only.” Thus, the main strategy of Beyond Budgeting is to separate (financial) bonuses from performance evaluation and to use relative and not fixed targets as a foundation for the evaluation.

      Sociocracy suggests holding 360 degree in-person meetings. The person being reviewed should request it when needed, not just on a rigid annual basis, and perhaps not just once in the year. In the 360 degree meeting, the organization itself can be critiqued in the review - “the way we organize is causing performance problems.” Similar to Beyond Budgeting there is a focus on the vision and mission of the specific department as well as the overall company as a source of inspiration and motivation. The output of the performance review meeting should be a development plan that the immediate group of supervision, peers, and subordinates consent to.

      Based on BOSSA nova, we invite participants to dive into what Beyond Budgeting and Sociocracy combined offer for performance appraisals. Participants will take away insights that they can use in their organizations.

    • Jutta Eckstein
      keyboard_arrow_down

      Jutta Eckstein / John Buck - Learning Fast & Small - Nourishing Company-wide Agility in a Skeptical Environment

      480 Mins
      Workshop
      Intermediate

      Agile beyond IT and beyond just doing it, but rather being it requires experimenting continuously in order to learn continuously. Thus more important than failing fast is learning fast.

      In this workshop we will learn what learning fast means for every individual and the organization as a whole and we will define experiments for you to use in your company for becoming agile truly. This will allow you to create an environment for continuous innovations.

      In this workshop we will also make use of examples that make:

      • the organizational structure (hierarchy?) more agile
      • the organizational processes faster so that they enable innovation
      • the organizational strategy better aligned with current needs so that your organization is able to drive the market instead of being driven by the market
    • Jutta Eckstein
      keyboard_arrow_down

      Jutta Eckstein - CD – Continuous Delivery and Cultural Difference

      20 Mins
      Talk
      Intermediate

      DevOps and continuous delivery is typically elaborated technically - what kind of tools, technologies, or skills are necessary for being able to deliver continuously. Often it is forgotten that continuous delivery requires also a culture change - in development, operations, marketing, sales, and not least for the customer.

      This can be recognized for example, that although it is technically possible for a team to deliver continuously, but it seems that this delivery isn't welcomed. This means the actual system will not be directly used.

      Therefore, in this session by taking into account the necessary cultural change, I want to answer the question how to implement continuous delivery successfully and what kind of pitfalls you need to be aware of when doing so.

    • Vincent FUCHS
      keyboard_arrow_down

      Vincent FUCHS - Keeping hundreds of code repositories consistent, and staying sane !

      20 Mins
      Demonstration
      Intermediate

      With the move to microservices architecture, a lot of teams end up managing dozens of code repositories (vs just a couple before), and some tasks that were done quickly manually are now becoming very time consuming : consistency of the repositories, and eventually of your platform, gets impacted, making it more and more difficult to manage.

      Surely, there must be some tools existing to take care of boring tasks like finding where a given dependency is used, and upgrade it automatically (this is just an example)... Well actually, we didn't find anything, so we implemented them ourselves and made them available for everyone !

    • Gabor Devenyi
      keyboard_arrow_down

      Gabor Devenyi / Alex Sloley - The magic number is 10

      45 Mins
      Talk
      Beginner

      Why are Agile teams supposed to be small? How big are they supposed to be? Most agilists tend to agree that a team of ten people works well.

      But what is it about the number 10 that makes it the “magic” number?

      Since the start of human evolution, people formed groups to be more effective. Whether it was the hunt for a mammoth or going to war, working in teams ensured a greater chance of success.

      There have been various researches from Dunbar’s paper through the Scrum Guide to military formations about the ideal number of people in a team.

      We’ll discuss the historical, scientific and cultural reasons why 10 seems to be the magic number of forming effective teams.

      Does the number of team members really matter? Is 10 really the magic number. You will get an answer that will help you to create effective teams with the right amount of people.

    • Vivek Ganesan
      keyboard_arrow_down

      Vivek Ganesan / Rejikrishnan Rajan - Reinventing DevOps Practices for Blockchain Applications

      90 Mins
      Workshop
      Intermediate

      With the arrival of distributed applications that run on Blockchain, it is essential to rethink some of the basic aspects of DevOps. Few things that we take for granted in DevOps area are either irrelevant, impossible or too costly for blockchain applications. Join us to explore the changes that the blockchain apps bring to the DevOps arena, using a hands-on demo of a sample blockchain app.

    • Jen Krieger
      keyboard_arrow_down

      Jen Krieger - A Culture of Openness

      Jen Krieger
      Jen Krieger
      Chief Agile Architect
      Red Hat
      schedule 2 years ago
      Sold Out!
      45 Mins
      Talk
      Beginner

      The “Agile mindset” was introduced to the software development community in 2001 in an attempt to foster freedom in the way that we work together. Its intent was to encourage organizational change that focused on people, collaboration and culture.

      But words on a screen don’t mean much in practice, especially if the people using them don’t - or won’t- understand their intent. How can individuals, teams and companies learn to correct these mistakes and break free from the challenges associated with change?

      Jen will share practical advice on effective Project Management, Agile Transformation, and getting things done– all told through the stories of her own journey towards something better at Red Hat.

    • Rajith Raveendranath
      keyboard_arrow_down

      Rajith Raveendranath - Blazing fast Big Data processing - High performance big data processing using Micro-services & Flow Based Programming

      Rajith Raveendranath
      Rajith Raveendranath
      VP
      SunTec
      schedule 2 years ago
      Sold Out!
      20 Mins
      Experience Report
      Intermediate

      An experience share about how we achieved high performance transaction pricing with elastic scaling, for a big T in the US, using Micro-services and Flow Based Programming.

      We start with the challenges faced by the telecom operator in their All IP access network which necessitates high volume, low latency transaction processing.

      We discuss the Micro-services advantage which let us build responsive, resilient and elastic services.

      We further discuss the FBP edge, which help us manage the big data effectively and also work as an event driven framework for Micro-services

      We will have a short discussion on the software stack used.

      We conclude by sharing the results and the lessons learnt

    • Pradeep Kellangere
      keyboard_arrow_down

      Pradeep Kellangere / Zaheerabbas Contractor - Implementing Rapid and Repeatable Pipeline for an Enterprise

      45 Mins
      Case Study
      Intermediate

      Enterprises and their individual feature teams are in a rush to build DevOps Pipelines with all the right reasons.

      While central teams are provisioning tools to be consumed at Enterprise level, individual feature teams are focusing heavily on building pipelines instead of building and enhancing business priorities.

      This results in "duplicate pipelines” solving the same problem of automation for build, test, package, infra, deploy and release using the given toolsets. - This results into duplication of efforts and redundancy.

      We intend to share our approach to build a pipeline enabled to for polygot programming languages and consumption patterns supporting various areas including.

      • A single click to deploy the complete pipeline infrastructure and app pipeline
      • Support multiple cloud deployment (AWS, Azure, etc…)
      • Adoption of open source tools
      • Clustered or non-clustered infrastructure deployments

      We will also emphasize on the implementation experience of the advanced Engineering practices in the area of immutable infrastructure, Chaos Engineering, blue-green/canary deployment.

    • Jen Krieger
      keyboard_arrow_down

      Jen Krieger - Delivering Open Source Projects with Agile & DevOps Thinking

      Jen Krieger
      Jen Krieger
      Chief Agile Architect
      Red Hat
      schedule 2 years ago
      Sold Out!
      45 Mins
      Talk
      Beginner

      Interested in learning how Red Hat is using Agile and DevOps thinking to help deliver popular open source projects such as Docker, Kubernetes and Project Atomic? Red Hat’s Chief Agile Architect, Jen Krieger, will walk you through the good, bad and the ugly of working with a highly motivated team.