...
이 단계에서, 전체 팀들은 챗을 사용하고 워크로드는 기존 시스템에서부터 채팅으로 전환한다. At this stage, full teams are using chat and workloads are transitioning from legacy systems to chat. Chat users who have reached this stage tend to find working the old way unimaginable.
이 단계에서 전체 팀은 체팅을 사용하고 작업 부하가 기존 시스템에서 채팅으로 전환되고 있다.
이 단계에 도달한 채팅 사용자는 이전 방식으로 상상할 수 없는 작업을 하는 경향이 있습니다.
Highly technical teams have started to implement “slash commands” that mimic working from a command-line terminal and some bot-based integrations.
For the most part, these integrations play a small role.
But awareness of the possibilities of chat are driving exploration across technical and non-technical teams.
...
Technical teams have begun automating common tasks with advanced bots, while non-technical teams have started to deploy chat-based apps.
Workloads are increasingly being done inside of chat and information is being brought into chat for collaboration via integration.
...
This marks a major transition point as chat has become the place where other apps and data sources are best shared.
In a sense, chat has started to become the browser for an increasing amount of data, tools, and collaboration.
...
Full workloads happen in chatrooms, and process has evolved to be chat-based for both planned and unplanned work.
The amount of task switching between apps at this stage has decreased appreciably because teams at this stage can query information and respond directly inside of chat, as well as manage other tools and process from within their chat tool.
...
At the extreme end of ChatOps, we see teams that have automated large portions of mission critical work.
Advanced custom bots, deep integrations, attempts at AI, and custom engineering have basically turned chat into the operating system for their team.
...
They are expanding the definition of ChatOps and breaking new ground when it comes to real-time collaboration.
They see no limits in how they could combine work, people, and tools to transform the way people on Earth (or eventually, Mars) collaborate.
...