The document discusses how ChatOps can be used as an agent of change by connecting people, tools, processes, and automation. It notes that implementing DevOps in a Microsoft environment can cause friction due to dependencies, lack of context, different time zones, and organizational structure. Finally, it lists over 30 common tools used in enterprise environments.

1. @scottnasello | @Monitorama
ChatOps as Change Agent?
1

2. @scottnasello | @Monitorama2
“DevOps in a Microsoft shop is like a 5 hour road trip
to an amusement park on the hottest day of the year”

3. @scottnasello | @Monitorama3
ChatOps: A collaboration workflow that connects
people, tools, process, and automation

4. @scottnasello | @Monitorama
NOBODY PUTS IN THE CORNER

5. @scottnasello | @Monitorama5
Welcome aboard!

6. @scottnasello | @Monitorama6
… New hire day 1
… Autobuild Coffee Scripts
… CI pipeline

7. @scottnasello | @Monitorama
Friction (n): conflict or animosity caused by a
clash of wills, temperaments, or opinions.

8. @scottnasello | @Monitorama
Friction (n): conflict or animosity caused by a
clash of wills, temperaments, or opinions.

9. @scottnasello | @Monitorama9
friction
… dependencies
… context
… time zone
… org structure

10. @scottnasello | @Monitorama10
1 2 3 4 5
Active Directory, Artifactory, Azure, CHEF, Cisco, Citrix,
Commvault, EMC, GitLab, Grafana, InfluxDB, Isilon, Jenkins,
Lansweeper, O365, NetScaler, Packer, Palo Alto, Pester,
PoshOrigin, SAP, SCCM, Sensu, SharePoint, Symantec, Teradata,
Terraform, TFS, VMware, VPN, Windows