Collaboration: The Next Development Opportunity
June 15, 2017

Stephen Hamrick
SAP

Today's worker faces a common collaboration conundrum: as new tools proliferate that bring teams together, individual employees are flooded with irrelevant information. In the development community, creating additional efficiency through improved collaboration has been prevalent for some time – through relatively new approaches such as agile and SCRUM, but historically through open source projects and developer forums. But despite the head start on the rest of the corporate world when it comes to collaboration, many organizations function today as they did 15-20 years ago.

Since time is money in the tech world, outdated collaboration is a huge missed opportunity. How can developers improve their approach to collaboration? Here are key ways for developers to improve interaction for greater speed and efficiency – not only in their own organizations, but in the solutions they roll out across their organizations.

Step One: Examine how other lines of business collaborate

No team should operate in a bubble – but especially the teams that are tasked with making companywide decisions regarding relevant technology. Often, collaboration solutions can get rolled out on features, rather than cultural fit. As developers fall in love with the tools they personally use, this can falsely predict the comfort that other lines of business will experience when using the tools themselves.

Ultimately, different groups of people share information differently, for a variety of business purposes. It is essential to have visibility into different levels of the organization to create a unified understanding of how people work. The culture should dictate the tools, rather than tools helping change the collaboration culture.

Step Two: Pick your tools beyond bots and chat

The array of collaboration tools is more comprehensive than many developers realize, and various tools serve a diverse degree of needs. For example, many organizations are too large or complex to rely solely on chat applications, while Wikis can be hard to search and find relevant information. Unified communications is a critical way to add audio and video to voice, but document sharing capabilities are constricted to specific interactions, rather than cataloged and organized in an online space.

The best solution is presumably something that utilizes the best of each tool, rather than calling a tool a strategy. Think about a mix of tools that best suit your team's needs, combining chat with Wikis, shared landing pages and centralized spots to house relevant content.

Step Three: Scale your tools wisely

Regardless of the mix of tools, a key consideration is to scale and integrate tools consistently. Many popular chat apps have limits on the number of accessible users, necessitating additional workspaces and areas for mass access to thousands or tens of thousands of people.

Additionally, the mix of tools must serve as a unified, organized mix of capabilities. Some collaboration providers look to integrate and sell multiple tools together, others do not. Examine a technology partner that can provide a holistic look at multiple capabilities, and build collaboration tools around business needs.

At the end of the day, collaboration is about value and efficiency. Developers must understand that it's more of a business issue than a technological issue, and work to improve their own practices and solutions that most efficiently bring people together. As some of the "early adopters" of many collaboration frameworks, this presents a clear opportunity for the developer community to change business culture for the better. When done right, collaboration can be a key business accomplishment – it's time for the community to recognize its importance and act accordingly.

Stephen Hamrick is VP Product Management, Collaboration Software, at SAP

The Latest

August 15, 2018

Microservices are a hot topic in IT circles these days. The idea of a modular approach to system building – where you have numerous, smaller software services that talk to each other instead of monolithic components – has many benefits ...

August 13, 2018

Agile is expanding within the enterprise. Agile adoption is growing within organizations, both more broadly and deeply, according to the 12th annual State of Agile report from CollabNet VersionOne. A higher percentage of respondents this year report that "all or almost all" of their teams are agile, and that agile principles and practices are being adopted at higher levels in the organization ...

August 09, 2018

For the past 13 years, the Ponemon Institute has examined the cost associated with data breaches of less than 100,000 records, finding that the costs have steadily risen over the course of the study. The average cost of a data breach was $3.86 million in the 2018 study, compared to $3.50 million in 2014 – representing nearly 10 percent net increase over the past 5 years of the study ...

August 08, 2018

Hidden costs in data breaches – such as lost business, negative impact on reputation and employee time spent on recovery – are difficult and expensive to manage, according to the 2018 Cost of a Data Breach Study, sponsored by IBM Security and conducted by Ponemon Institute. The study found that the average cost of a data breach globally is $3.86 million ...

August 06, 2018

The previous chapter in this WhiteHat Security series discussed dependencies as the second step of the Twelve-Factor App. This next chapter examines the security component of step three of the Twelve-Factor methodology — storing configurations within the environment.

August 02, 2018

Results from new Forrester Consulting research reveal the 20 most important Agile and DevOps quality metrics that separate DevOps/Agile experts from their less advanced peers ...

July 31, 2018

Even organizations that understand the importance of cybersecurity in theory often stumble when it comes to marrying security initiatives with their development and operations processes. Most businesses agree that everyone should be responsible for security, but this principle is not being upheld on a day-to-day basis in many organizations. That’s bad news for everyone. Here are some best practices for implementing SecOps ...

July 30, 2018

While the technologies, processes, and cultural shifts of DevOps have improved the ability of software teams to deliver reliable work rapidly and effectively, security has not been a focal point in the transformation of cloud IT infrastructure. SecOps is a methodology that seeks to address this by operationalizing and hardening security throughout the software lifecycle ...

July 26, 2018

Organizations are shifting away from traditional, monolithic architectures, with three-quarters of survey respondents delivering at least some of their applications and more than one-third delivering most of their applications as microservices, according to the State of DevOps Observability Report from Scalyr ...

July 24, 2018

What top considerations must companies make to ensure – or at least help improve – Agile at scale? The following are key techniques and practices to help accelerate Agile delivery rollouts and scale Agile and DevOps in the Enterprise ...

Share this