Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion src/handbook/company/communication.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ Our recommended Slack (light) theme is:
You will not automatically join every Slack channel when you start. Below are some helpful channels you may want to join depending on your interests and work.

- `#announcements` for company-wide announcements.
- `#feature-demos` for product updates. Everyone should stay aware of product changes, no matter their role.
- [`#feature-demos`](https://flowfuse.slack.com/archives/C04GW82DJFK) for product demos of sprint and release deliveries, showcased to a wide audience (marketing, sales, product strategy, leadership). Everyone should stay aware of product changes, no matter their role.
- `#ops-metrics` for sales and engagement metrics.
- `#virtual-coffee` to join the coffee call rotation.
- `#gh-handbook` to follow updates to the handbook.
Expand All @@ -120,6 +120,10 @@ We recommend organizing these channels into [custom Slack sections](https://slac

We also have channels for specific groups, such as `#people-managers` for managers and `#us-hr` for HR topics specific to US team members.

##### Project channels

Project channels are created for continuous work discussion within a product lane with a clear scope. Use them for day-to-day coordination, intermediate demos, design feedback, and scope discussions among the directly involved stakeholders. When a feature is ready to be delivered, the final demo should be posted to [`#feature-demos`](https://flowfuse.slack.com/archives/C04GW82DJFK) instead. This keeps `#feature-demos` focused on what is ready for a wider audience, and `#proj-` channels focused on what is still in progress.

When you create a new channel, add a clear description. This helps everyone browse channels and decide which ones are relevant to their work.

### GitHub
Expand Down
2 changes: 1 addition & 1 deletion src/handbook/development/project-management.md
Original file line number Diff line number Diff line change
Expand Up @@ -321,7 +321,7 @@ Demos should consist of:
- A short (< 5 minute where possible) screen capture walk through of the feature with commentary.
- It should cover the feature from a users perspective - what value do they get from it.
- The video should be uploaded to, or linked to, in the relevant issue.
- A link should be posted to the `#feature-demos` channel in slack. This will allow the whole team to be notified of the demo without having to subscribe to every issue comment.
- To be posted to the [`#feature-demos`](https://flowfuse.slack.com/archives/C04GW82DJFK) channel in Slack for work that is ready to be delivered. Intermediate demos for fine-tuning current sprint scope should be shared in the relevant `#proj-` channel instead (see [Communication](/handbook/company/communication/#project-channels)).

For some features, it may be necessary to create multiple demos of different aspects.

Expand Down