<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Collaboration on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/collaboration/</link><description>Recent content in Collaboration on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Wed, 06 Jan 2021 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/collaboration/atom.xml" rel="self" type="application/rss+xml"/><item><title>Using ChatOps to Improve the R&amp;D Process</title><link>https://www.chenshaowen.com/en/blog/using-chatops-to-improve-the-r-and-d-process.html</link><pubDate>Wed, 06 Jan 2021 00:00:00 +0000</pubDate><atom:modified>Wed, 06 Jan 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/using-chatops-to-improve-the-r-and-d-process.html</guid><description>1. What Is ChatOps GitOps, ChatOps, AIOps, and the like (hereafter NewOps) are emerging operations philosophies that have appeared in recent years. NewOps separates Ops out of its chaotic state into two parts: one facing users, trending toward being more human, auditable, and traceable; the other facing infrastructure, trending toward being more programmatic, automated, and intelligent.</description><dc:creator>WeChat Official Account</dc:creator><category>R&amp;D</category><category>DevOps</category><category>ChatOps</category><category>Operations</category><category>Automation</category><category>Learning</category><category>Collaboration</category><category>Process</category></item><item><title>A Git-Based Frontend and Backend Development Workflow</title><link>https://www.chenshaowen.com/en/blog/based-on-git-development-workflow-of-front-and-back.html</link><pubDate>Sat, 31 Mar 2018 00:00:00 +0000</pubDate><atom:modified>Sat, 31 Mar 2018 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/based-on-git-development-workflow-of-front-and-back.html</guid><description>Recently I took part in a project developed collaboratively by several people, and ran into quite a few problems along the way. For example: a frontend commit overwrote backend code, conflicts were left unresolved and turned into rework, someone committed to branch B, or committed straight to the Master branch.</description><dc:creator>WeChat Official Account</dc:creator><category>Git</category><category>Efficiency</category><category>Collaboration</category><category>CI</category><category>DevOps</category><category>R&amp;D</category></item><item><title>Cross-Departmental Collaboration Course Notes</title><link>https://www.chenshaowen.com/en/blog/cross-departmental-collaborative-curriculum-notes.html</link><pubDate>Fri, 14 Jul 2017 20:55:29 +0000</pubDate><atom:modified>Fri, 14 Jul 2017 20:55:29 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/cross-departmental-collaborative-curriculum-notes.html</guid><description>Collaboration is a journey.
1. Obstacles to Cross-Departmental Collaboration Resistance to collaborating on new business Gray areas in responsibilities Employees&amp;rsquo; ability to collaborate Information asymmetry The management mechanisms for cross-departmental collaboration Misaligned goals and interests Limited resources 2. The Core Philosophy of Collaboration Win-win thinking An open mindset The three aspects at the heart of collaboration</description><dc:creator>WeChat Official Account</dc:creator><category>Management</category><category>Collaboration</category><category>Teams</category><category>R&amp;D</category></item></channel></rss>