Communication

.github/workflows/linting.yml

@@ -0,0 +1,18 @@
+name: Linting
+
+on:
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  linting:
+    name: "Markdown linting"
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out the code
+        uses: "actions/checkout@v2"
+      - name: Lint code
+        uses: docker://avtodev/markdown-lint:v1
+        with:
+          args: "**/*.md"

.markdownlintrc

@@ -0,0 +1,3 @@
+{
+  "MD013": false
+}

communication/asynchronous-messaging.md

@@ -0,0 +1,8 @@
+# 💬 Asynchronous Messaging
+
+## 4 components of a great asynchronous message
+
+1. Include enough information to cover all follow-up questions.
+1. Include a deadline for when you need an answer.
+1. Add any links, images, and as much supporting materials as is possible.
+1. Include a concrete need or outcome.

meetings/retrospectives.md

@@ -0,0 +1,13 @@
+# 🤔 Retrospectives
+
+## Purpose
+
+To reflect on the past and make improvements on the future. Identify what went well, what didn't go well, and what we can change.
+
+## Steps
+
+1. Review action items from past retros.
+1. Spend 5 minutes adding thoughts.
+1. Group like items together.
+1. Vote on what we feel is the most important to talk about.
+1. Discuss items in order of votes. Add new action items as needed.

process/cycle-goals.md

@@ -0,0 +1,15 @@
+# 🎯 Cycle goals
+
+## Purpose
+
+The cycle goal communicates to the team what we are trying to accomplish at the end of a cycle.
+
+It shouldn't be just "implement this solution in this time frame" but something we can say is true after we are finished. More often than not, it should be user focused.
+
+The problem statement, appetite, and goal of a pitch are what the team will use to shape a solution. These 3 items needed to be set before the team can shape an effective solution.
+
+## Example goals
+
+* Allow users to easily add documents they commonly use on projects from a project or in a project template.
+* Users are able to restrict access of documents to the uploader, admin, and manager for existing documents.
+* Out internal teams will be able to resume building on Slab and will be able to contribute to mobile, web, and token packages.

process/singer-process.md

@@ -0,0 +1,26 @@
+# 🎶 The Singer Process
+
+## Framing
+
+Who: Product Trio
+What: What do we want to accomplish and why? What is the context, outcome, and constraints?
+
+## Pitch shaping
+
+Who: Product Trio
+What What should we build to satisfy the frame?
+
+## Technical shaping
+
+Who: Engineers
+What: How do we best build the solution?
+
+## Team alignment
+
+Who: Entire team
+What: Are we doing the right thing? Do we understand what we are doing? Are we missing anything?
+
+## Scoping
+
+Who: Entire team
+What: What is our plan to to build the solution and accomplish our goal?