• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
Codemotion Magazine

Codemotion Magazine

We code the future. Together

  • Discover
    • Live
    • Tech Communities
    • Hackathons
    • Coding Challenges
    • For Kids
  • Watch
    • Talks
    • Playlists
    • Edu Paths
  • Magazine
    • Backend
    • Frontend
    • AI/ML
    • DevOps
    • Dev Life
    • Soft Skills
    • Infographics
  • Talent
    • Discover Talent
    • Jobs
  • Partners
  • For Companies
Home » DevOps » How To Build Teams and Practices to Deliver Value
DevOps

How To Build Teams and Practices to Deliver Value

In this article we take a look at how teams can deliver value through innovations in both people and processes.

September 2, 2020 by Cate Lawrence

Table Of Contents
  • Change your work practices to deliver value with small, incremental changes
  • Do fewer things at once to avoid context switching
  • Company culture is a critical component to deliver value
  • Hiring and retaining great people 
  • Join us for Panel 3 – The secret sauce for delivering value

People working in tech are always trying to maximise their ability to deliver value. We’ve created philosophies such as scrum, agile and later DevOps.

We’ve created a plethora of work practices that are designed to increase efficiency, reduce waste and improve customer and client practices. Importantly, we’re not only interested in better processes that lead to better products, but also in improving the overall world and way of work.

Let’s take a look at some of the central principles and how they play out across teams and departments in real-life scenarios: 

Change your work practices to deliver value with small, incremental changes

In terms of software, we have realised over the years, that the smaller the better, the more the focus it is, the faster it builds, and the faster it drops.

is a Principal Technologist at Amazon Web Services, he suggests that there are key components critical to successfully delivering those small incremental changes: 

  • Automated continuous delivery: You need to have automated Continuous Delivery pipelines. Because doing those changes by hand, it’s gonna take a while.
  • Tagging, which allows you to tag the versions you need
  • Flagging, A/B features where you can say turn this feature on turn this feature off.
  • Canary testing, A/B testing, where you can say:

“I’m going to release this new feature to one person of my traffic coming at Tuesday, 11am. That is coming from a certain user agent, but maybe a mobile device or a browser. That’s where you start testing it. And then you expand from there based upon your health metrics on how that’s working out.”

Do fewer things at once to avoid context switching

Jake Levine, a staff software engineer at Meetup believes that which might appear lazy by some managers, is actually about increasing efficiency overall.

He offers multitasking as an example: “Our non-lazy engineer is always working on tonnes of different things. They’re taking on tonnes of different projects all at once.” 

However every time we task switch, we have to refocus our attention to the tasks at hand which requires additional effort “we suddenly have to remember all of the contexts that’s related to our new activity, where we left off, what the remaining open items are, etc.”

Conversely, if we focus all of our attention on one task at a time, we are likely to have greater concentration and be able to complete the task faster and at a higher quality. 

Company culture is a critical component to deliver value

Thiago de Faria is Head of Solutions Engineering, at LINKIT. He contends, “Culture is the biggest problem in every field in every area. technical things and computer are easy. People are hard. And usually, people are hard because they are a reflection of how culture happens inside the company.”

He gives the example of being an on-call worker:

“This is something that I passionately defend. Because I think people only write good production code, when they feel the pain to be on-call for receiving a pager duty notification, then you start to do proper testing, proper integration for things because you don’t want that thing to go into production. If it’s gonna harm, you’re weakened.”

Without the first-hand experience of the pain of pager duty, developers are less likely to commit to proper testing and documentation that reduces the painpoint the next time around. However with a pager call, when the dev doesn’t know what to do, if they have a CI/CD pipeline, “They’re just going to roll back to the latest version and open a ticket for you to fix that thing. 

Hiring and retaining great people 

While we are intent on trying to increase efficiency by methods such as automation of processes that would otherwise be long and arduous, the people we employ are also a critical part of the equation.

Companies need to employ great people, provide opportunities for interesting work, useful feedback, and career progression. Without nurturing people and building great teams, people leave companies for somewhere better – and skilled people with experience are often in short supply in tech. 

 According to Freelance front-end developer Yaprak Ayazoglu, this includes providing support and resources for parents in tech. She suggests that companies need to be aware of the challenges facing parents at work – especially mothers – and that training would be a good option to help employers and employers gain empathy. 

All developers are affected by challenges throughout their career lifecycle, and emotional intelligence will help them progress.

Yaprak notes that fear of employment rejection facing many pregnant women, especially in tech: “I’m already judged unconsciously because of my gender. But after being pregnant, will I be treated like an idiot?”

Join us for Panel 3 – The secret sauce for delivering value

If you liked this article and are interested in further improving your work practices put on your agenda our next online event, in October! You’re going to love not only because it’s free but for the level of expertise and insights that you will be able to gather.

During the dedicated Panel, we’ll be exploring what truly is value and discuss how we can measure it in an unbiased way.

We’ll unpack this tiny word, and we’ll see its different aspects. We’ll hear about the challenges our experienced panellist faced to maximise the produced value, from shaping the development and alignment processes to coaching their teams, choosing the right tools and technologies, and obviously getting the metrics right!

Master of Ceremony:
  • Piergiorgio Niero – Head of Engineering at SuperAwesome
Panellists:
  • Frank Amankwah – Head of Digital Engineering at Emirates Group
  • Renan Gutman – Executive VP Product at Kaltura
  • Chris Brooke – VP Engineering at Spirable

“I’m going to release this new feature to one person of my traffic coming at Tuesday, 11am. That is coming from a certain user agent, but maybe a mobile device or a browser. That’s where you start testing it. And then you expand from there based upon your health metrics on how that’s working out.”

If you want to know more about how modern technologies and tools can support you for – and during – the organisation of a virtual event, don’t miss this article showcasing the best tools we used to host our online conferences since the COVID-19 outbreak.

facebooktwitterlinkedinreddit
Share on:facebooktwitterlinkedinreddit

Tagged as:Teamwork

How Can You Become A Chief Technology Officer?
Previous Post
Digital Nomads: Finding Freedom By Writing Code While Travelling
Next Post

Related articles

  • Being A Tech Lead: How Much Tech, How Much Lead?
  • How To Avoid A CTO Meltdown (Warning Signs)
  • Codemotion Takes a Look at the Future of Work
  • How do we make tech less male, pale and stale?
  • Because we’re worth it: tech’s top women
  • DevOps Trends to Follow in 2023
  • Automotive Software Development: Can Agile and ASPICE Coexist?
  • What Is DevSecOps and Why Is It So Important?
  • Automating Security Testing with SCA, SAST and DAST
  • Challenges for DevOps in the Banking Sector

Primary Sidebar

Codemotion Talent · Remote Jobs

Flutter Developer

3Bee
Full remote · Android · Flutter · Dart

Python Back-end Developer

h-trips.com
Full remote · Django · Pandas · PostgreSQL · Python

AWS Cloud Architect

Kirey Group
Full remote · Amazon-Web-Services · Ansible · Hibernate · Kubernetes · Linux

AWS SysOps Administrator

S2E | Solutions2Enterprises
Full remote · Amazon-Web-Services · Terraform · Linux · Windows · SQL · Docker · Kubernetes

Latest Articles

laravel best practices. The most popular PHP framework turns 12

Laravel: Celebrating 12 Years of Powering PHP Development

Languages and frameworks

Intelligent document processing with serverless cloud and machine learning.

Intelligent Document Processing With Serverless Cloud and Machine Learning

Cloud

kubernetes, probe failed error

K8s Readiness Probe Failed Error

Cloud

AI books you have to read.

10 Books on Artificial Intelligence for Developers

AI/ML

Footer

  • Magazine
  • Events
  • Community
  • Learning
  • Kids
  • How to use our platform
  • Contact us
  • Become a Contributor
  • About Codemotion Magazine
  • How to run a meetup
  • Tools for virtual conferences

Follow us

  • Facebook
  • Twitter
  • LinkedIn
  • Instagram
  • YouTube
  • RSS

© Copyright Codemotion srl Via Marsala, 29/H, 00185 Roma P.IVA 12392791005 | Privacy policy | Terms and conditions

Follow us

  • Facebook
  • Twitter
  • LinkedIn
  • Instagram
  • RSS