DeveloperWeek Global: Enterprise 2020 DeveloperWeek Global: Enterprise 2020

Dev Leadership & Management

Tuesday, November 10, 2020

- PST
KEYNOTE: PagerDuty -- How to Advocate to Not You: Non-technical Considerations for Our Technical Tools
Join on Hopin
Quintessence Anx
Quintessence Anx
PagerDuty, DevOps Advocate


One of the things I struggled with as an SRE was being able really grok what non-engineers/non-devs like my manager, whomever they reported to, and various chains in my employer’s business cared about most when it came time to select tools. Depending on the size of the employer, startup to enterprise, there are increasing numbers of non-engineering folks who have decision making power over the team’s tools. Thus, as devs, ops, etc. we cannot keep our focus on just the technical aspects of different tools and frameworks or we’ll miss the opportunity to appropriately make our case to these other stakeholders. In this session, I’ll be discussing what these other groups need to know to help them make a decision in your best interest.

- PST
VIP Networking Lounge: Fireside chat w/ Featured Speakers
Join on Hopin
Shahir A. Daya
Shahir A. Daya
IBM, Distinguished Engineer and CTO
Shay Mandel
Shay Mandel
Next Insurance, Engineering Manager
Peter Zaitsev
Peter Zaitsev
Percona, CEO

Join DevNetwork Co-founder Jon Pasky in this fireside chat on Engineering Innovation.


- PST
Leveraging Technology to Build and Manage Inclusive Remote Teams
Join on Hopin
Maria Shoaib
Maria Shoaib
Ericsson, Software Engineer

This talk will focus on why inclusive remote teams are better, and how to build them. Starting with “why?”, moving towards “how?” by explaining key methods of inclusivity: design, data analysis, building inclusive teams, leading with empathy, and SDLC with diversity, and sharing resources as inclusion from an overhead cost to a business enabler is a need of tomorrow

- PST
Organization, Architecture, Autonomy and Accountability
Join on Hopin
Kevin Goldsmith
Kevin Goldsmith
Chief Technology Officer

Many consider agile a process to implement within an existing organization. A set of rules to follow that will produce some useful outcomes. This approach can provide improvements in many different structures of organizations. As agile maturity improves, however, the benefits can become limited by the structure and culture of the organization itself.

Agile is more than a framework for organizing tasks for a team. Agile is a culture, a mindset, and a structure for improving the velocity of innovation and providing real business value to customers. To gain the most benefit from Agile it must be considered as part of a more extensive system that incorporates organizational structure, software architecture, and company culture.

This talk considers the interactions between how the work, the software, and the people are organized in high performing agile organizations. Using my own experiences at companies large and small, I will share what I have learned and some best practices I use. These lessons will help you as you improve and scale your Agile teams.

I will discuss:
* How to structure your organization to remove the bottlenecks in coordination and decision-making that can slow velocity to a crawl
* How to take advantage of modern systems architectures to allow teams to move faster
* Using data to provide accountability for autonomous teams without creating more process
* By the end, you will have concrete examples and ideas that you can bring back to your team to help you improve and scale agile within your organization.

Wednesday, November 11, 2020

- PST
5 Skills to Master the New Developer Agenda
Join on Hopin
Annie Mathew
Annie Mathew
Microsoft, Director, Developer Relations

In this pandemic season nations across the world are in various stages of economic response and recovery. As technology plays a vital role in the recovery of nations, the role developers need to play is also undergoing a massive shift. Much like the gap between developers and operations teams brought about Devops, its time now for developers to integrate far more tightly with business leadership to help companies navigate the economic turmoil leveraging tech. I'll talk about 4 skills the new developer needs to master beyond tech alone to realize the potential for transformation - BizDEv teams, understand the business and its problems, dig into pricing and optimization, culture of rapid experimentation and communication. Experiential learning from Asian dev community and customer.

- PST
OPEN TALK: An Automation Journey: Testing a Cloud-Based IoT System
Join on Hopin
Mesut Durukal
Mesut Durukal
Siemens, Test Automation Lead

In this presentation, management of a test automation project experiences are told. System under test is the cloud-based, open IoT operating system.

Digitalization is the hottest topic of businesses where companies invest in transforming their processes by leveraging digital technologies. On this trend topic, applied approaches and techniques are explained to construct ideas about the whole testing lifecycle of cloud-based platform. Test levels, priorities, release scopes and regression suites and the structure of the self-developed automation framework with infrastructural components and tools are investigated.

Like all other journeys, there are ramps and landings on the way. Lessons learnt are continuously utilized and processes are improved by evaluating various strategies and adding feedbacks collected from all parties. Some applications have not resulted positively, and the project has reacted as how an agile organization should do. Challenges are listed and actions against them are summarized with visualizing the benefits by comparing before and after situations. The whole progress from the first stages to the last gives an insight about how the project develops and reaches to maturity.

This is the story of automation journey, which is started with a motto: “We are all in the same boat”. The goal is to make insights of a good test management process and best practices.

I think that this submission has an interesting content which can make great attention. Rather than theoretical claims, it consists of practical real-life experiences. A full journey will be shared with challenges and proposals against them of course. Successful adaptation of latest technologies and trends is also in the context. In this scope, I talk about API&UI testing automation frameworks, zero downtime release activities such as blue-green deployments. Initiatives like application of artificial intelligence in testing stages will be told as well. Instead of what to do, I go over how to do.

- PST
OPEN TALK: OWASP Top 10 Overview
Join on Hopin
Vanessa Sauter
Vanessa Sauter
Cobalt.io, Senior security strategy

Software is vulnerable. The good news is, software is vulnerable in ways that are known and can be addressed. For the past 15+ years, the security community has been publishing and tracking a list of common security vulnerabilities called the OWASP Top 10.This session provides a brief overview of ten common DevSecOps security vulnerability categories. It's a lot to cover in 25 minutes, so this session focuses on the general concepts.

- PST
OPEN TALK: Perfect Strangers - Successfully Working in a Cross Functional Environment
Join on Hopin
Lauren Nagel
Lauren Nagel
New Relic, Sr. Dir. Product Management
Nic Jansma
Nic Jansma
Akamai, Senior Principal Lead Developer

Successful businesses are built on the shoulders of many different roles and personas. Your personal success certainly depends on your individual contributions, but it also depends on how well you can work across different functions as a team member. Interactions between Developers and Product Management, Developers and Test, or with business focused functions such as Marketing and Sales are key to getting things done in an organization, building a great product, and ultimately your own success! Each role may have different “languages” they speak, priorities and scopes of focus. Navigating these variations is not taught in school, and may initially seem like a huge challenge. Understanding and working well with your counterparts enables everyone’s impact to grow larger than each individual’s contributions, and can help create robust products, close working relationships and increase job satisfaction.

Nic, an Engineering Manager, and Lauren, Product Line Lead, started working together 5 years ago. They have not only built a collaborative engineering/product relationship, but have become good friends as well. They’ll outline the four pillars they think are critical to a great cross-functional relationship: Respect, Empathy, Trust and Communication, and how to cultivate them in your own teams.

You’ll walk away not only with a better understanding of the importance of your colleagues in different roles and how these cross-functional relationships aid in everyone’s success, but also with clear tactics to improve your daily interactions. Nic and Lauren will share their own proven methods for a great cross-functional relationship including; how they support and amplify each others’ needs, effective methods and tools for communicating with each other, and how together they prioritize their work efforts for the most impact.

- PST
OPEN TALK: How Cisco Embraced a DevOps Culture Within Its Network Engineering Team
Join on Hopin
Stuart Clark
Stuart Clark
Cisco Systems, Network Automation Developer Evangelist

BUSINESS PROBLEM & CHALLENGE
Network automation was not well practiced or well understood inside our network engineering team, but was sorely needed. We needed to decrease effort and mistakes on daily management tasks by minimizing the direct human interaction with network devices. High on our priority list of goals, was improving network security by recognizing and fixing security vulnerabilities and increasing the network performance.

HOW WE OVERCAME THE CHALLENGE
We started by simplifying daily workflows, baselining our configurations and removing snowflakes. While this can be very labour-intensive at the outset when you’re working on a global scale in a highly critical customer environment, the long-term benefits far outweighed the labour.
Next, we created an inventory file which listed all network devices by type, model, location and IP address - this enabled us to retrieve info about devices and using network programming and automation, allowing us to deploy to all devices, or even a subset of devices (eg. only those in a specific area), depending on what was needed. The benefit to this is we avoided manual configuration and logging into hundreds of different devices to add configuration to each one.
Overcoming these two big challenges set us up for success and enabled us to deploy at a global scale. We lived by the mantra:

“If it’s not repeatable, it’s not automatable. And if it’s not automatable, it’s not scalable.”

LEARNINGS AND MEASURABLE OUTCOMES
So what did we learn? For starters, it can be hard to automate a use case or test in the same way you would if doing it manually. Testing that requires physical movement, for example losing service provider links or hardware failure is also a challenge, as automating something like that is very tricky. We also learned that code reviews are extremely important. Shared code ownership means the entire team can make changes anywhere, at any time.

And what we’re the measurable outcomes?

Faster deployment times - we were able to efficiently push changes to over 300 network devices and audit the configuration of our global network, taking the time to execute from days down to hours.
Removed the fear of large and complex network changes - the accuracy and efficiency with which we were able to deploy at scale, gave business and the leadership more confidence in subsequent large scale network changes and deployments.
Faster feedback on network changes - it allowed us to get reviews on network configuration changes with version control and peer review, treating infrastructure as code (IaC).
Helped with adhering to PSIRT/CSIRT challenging timeframes and security vulnerabilities.


Techniques used:
We started by simplifying daily workflows, baselining our configurations and removing snowflakes. Next, we created an inventory file which listed all network devices by type, model, location and IP address.

Metrics used:
Speed of deployment; speed of feedback on network changes; speed of adherence to PSIRT/CSIRT timeframes; confidence and buy-in from senior leadership on subsequent deployments!