Java IoT Authors: Yeshim Deniz, Liz McMillan, Zakia Bouachraoui, Elizabeth White, William Schmarzo

Related Topics: @DevOpsSummit, Java IoT, Microservices Expo

@DevOpsSummit: Blog Post

Team Cohesion in DevOps Collaboration By @Datical | @DevOpsSummit [#DevOps]

DevOps culture aim to address change at the organizational level, which of course is the ultimate goal

Team Cohesion Is the Beginning of DevOps Collaboration

I read an interesting article this morning discussing some tips for effecting cultural change at the team level, written by Bertrand Besnard on DevOps.com (see article here).  It was interesting because most of the articles I read on DevOps culture aim to address change at the organizational level, which of course is the ultimate goal.  But Bertrand's take on culture has a more homegrown feel to it, more of a bottom's up approach towards transforming culture, that, as I think about it, should also be included in the general discussion.

Essentially, Bertrand's implied logic is that by first creating a culture of trust and collaboration at the team level the team can then champion cultural transformation on a broader scale.  This triggered my memory about some studies I've seen on the adoption of DevOps, where some of the questions asked how the movement started within the organization.  If I remember correctly, there was a good split between implementations initiated by management (top down) and those that started as a homegrown movement from one team or other internal champion (bottom up).  The difference came in the speed of transformation, wherein the additional resources and organizational commitment demonstrated through a management-led implementation effected change and led to results sooner.  But both approaches netted similar results in terms of benefits to the organization and the business.

To that end, here are four suggestions for improving intra-team culture and building better cohesion:

Create cohesion
Bertrand provides a lot of tips around getting the team together more often, whether that's going out for a beer to welcome a new team member, a monthly happy hour, or participating in an amateur sports league together.  Those are all well and good, and will contribute towards team cohesion, but in my experience these efforts are a long term strategy at best.  Think about it - these people already spend 8-10 hours a day together - do they really need to spend even more time together to build cohesion?  Also, people are generally less willing to engage in these types of after-work activities when they have families who are competing for their personal time at home.

So what would my suggestion be?  After many years as an Army officer and having built, coached, and trained many teams, my answer is shared misery.  I've never seen anything more successful at building team cohesion than dropping the team off in the middle of nowhere and telling them to work together to figure out how to get back home.  We ran exercises like this about once a quarter, wherein it seemed the planners of each successive event were constantly trying to outdo the last one, incrementally increasing the punishment we endured.  My brigade commander actually patterned the events he hosted after a technique that Genghis Khan supposedly liked to employ to indoctrinate new leaders, which he affectionately labeled the "Mungadai."  The story goes that ol' Genghis would drop a new leader off in the woods with only a rice ball (apparently with fishy bits inside) and the clothes on his back and tell him if he wanted to lead in Genghis' army he had to find his way back, knowing that the most direct route would take at least several days.

Shared misery works.  I'm not sure exactly why.  But as I thought about it during all of those excruciating training exercises, I came up with two reasons.  First, shared misery strips individuals of everything they thought to be important in their lives before the misery started, and provides extreme focus on the act of surviving - when others are in the same situation, people tend to naturally cooperate with each other to ensure the survival of all.  Second, it builds trust between team members, as in trying to escape the misery together they necessarily have to rely on each other, whether that's simply trying to get a fire started in the drizzling rain or traversing a chasm together.

Shared misery at this level is probably not going to pass muster with your typical IT team, but there are ways you can share some misery together.  Organize a team camping trip over a couple of days, or go and play paintball together.  At Datical we put together a team that trained and executed the Tough Mudder event together - one of those crazy obstacle course races.  It was only a few hours of misery, but the misery was pretty extreme - good team-building event.

Create incentive
Incentives are about encouraging the "right" behaviors.  Find a way to reward individuals and the team for the behaviors you want to see, and figure out ways to, not punish, but provide some kind of negative reinforcement for those behaviors you don't want to encourage.  Bertrand recommends making people, with their informed consent of course, contribute a trivial amount of change to a jar when one makes a mistake - say, breaking a build or not naming a file correctly.  Then, periodically, you use the money in the jar to go do something fun.  In the Army we weren't this creative - we just did a lot of pushups.  We called it "beating your face," as in, "Well, that was a knuckleheaded thing to say - beat your face."

Develop people
This is one I really believe in.  People have a way of responding when their leaders take a personal interest in them, and tend to show gushing appreciation for leaders who sincerely make an effort to improve them - whether that's helping an individual get better with a technical skill, or periodic counseling on career trajectory, etc.  There are basically two ways to develop people - informally and formally.  The formal approach is all business, and usually organizational policy - it typically takes shape via a monthly or quarterly counseling wherein you initially collaborate to establish some personal goals for the period, and then periodically come back to assess progress towards those goals and provide constructive feedback on how to improve.  The informal approach isn't documented or tracked, and relies heavily on commitment from the leader to interact with team members every day, creating teaching moments for the individual and team whenever possible.  It's basically what a good coach does with her players each practice.  I like the informal approach much better, as I've always gotten better results with it, even though it requires much more time to do well.

Demonstrate values
This means practicing what you preach.  A leader has to understand that team members are constantly watching him or her, to see if actions live up to words.  When there is alignment between a leader's stated values and his or her actual actions, the team will fall in line.  When there is no alignment, resentment grows in the team as team members begin testing the limits of what they can get away with.  It only seems natural to them in this scenario, because in their eyes the leader is getting away with it.  This also leads to CYA behavior and internal politics, which over time becomes a cancer within the team and organization.  So, practice what you preach.

More Stories By Rex Morrow

Rex is the Marketing Director at Datical, a venture-backed software company whose solution, Datical DB, manages and simplifies database schema change management in support of high velocity application releases. Prior to Datical, Rex co-founded Texas Venture Labs, a startup accelerator at the University of Texas, and received his MBA from the McCombs School of Business. Before graduate school, Rex served as a Captain in the U.S. Army, and was awarded two bronze stars during combat deployments in Iraq.

IoT & Smart Cities Stories
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
Whenever a new technology hits the high points of hype, everyone starts talking about it like it will solve all their business problems. Blockchain is one of those technologies. According to Gartner's latest report on the hype cycle of emerging technologies, blockchain has just passed the peak of their hype cycle curve. If you read the news articles about it, one would think it has taken over the technology world. No disruptive technology is without its challenges and potential impediments t...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...