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 17, 2017

Mobile SDKs (software developments kits); love them or hate them, they're here to stay. They provide our apps with all sorts of functionality that would be incredibly time consuming to build, and they give us another means to monetize our apps. While it would be difficult to argue that SDKs aren’t useful, it’s also hard for developers to get a good idea of the amount of resources used by each SDK once the app is in production ...

August 15, 2017

A common belief within DevOps circles is that automation not only enables greater frequency of delivery and deployment, but improves its overall success rate. Whenever manual intervention is required, the chances of errors creeping in increases. Human error is a significant factor in many an outage, after all ...

August 14, 2017

DevOps and NetOps are both far more generous in their opinion of the other with respect to prioritization of efforts than traditional archetypes purport them to be, and they have a lot in common – even though they may disagree on details – according to a new survey by F5 ...

August 10, 2017

Only 12 percent of organizations can claim that their whole organization is on the path to business agility even though more than two thirds of survey participants agreed that agile organizations are better able to quickly respond to dynamic business conditions, according to a new survey from CA Technologies ...

August 09, 2017

Alongside its clear benefits, DevOps brings unique challenges when developing and operating a mobile environment. Mobile app developers and development teams face a unique set of requirements relating to collaboration, testing, and release. Technology fragmentation, disparate back-end systems, updates that require user action, and poor instrumentation can impede the DevOps process and become critical roadblocks to agile mobile development, ultimately impacting app retention and the bottom line ...

August 07, 2017

A crashing app might be a deal breaker, no matter how heavy the load that an alternative website entry point can handle would be. It is all about quickly verifying compliance against key functional and non-functional requirements in order to meet aggressive release schedules as part of the Go-to-market strategy. This means positioning unit testing, UI testing, API testing, and, of course, performance and load testing — as pillars of SDLC ...

August 03, 2017

Most software developers make themselves easy targets for hackers, even when they are behind a corporate firewall, according to a new survey from Netsparker Ltd. ...

August 01, 2017

Your top priority is to improve application development agility, but you may run into roadblocks put up by a security team that (mistakenly) believes speed is the enemy of effective cybersecurity. A new survey finds a majority of enterprises are working to overcome those roadblocks by integrating security into their existing DevOps methodology ...

July 31, 2017

Agile development compresses software testing cycles, jeopardizing risk coverage and opening the door for software failures. Here's what you can do ...

July 27, 2017

While 75 percent of organizations highlight continuous testing as critical or important, only a minority of survey respondents have made exceptional progress acquiring the necessary knowledge and key enablers to drive digital transformation, according to a global study by CA Technologies ...

Share this