Difference between revisions of "Stand-up Meetings"
| Line 1: | Line 1: | ||
| − | == | + | == Using Slack for Stand-up == |
Our software team is unique in that each member is working on their own individual projects instead of a shared development responsibility. This challenges some of the ideas around the Scrum process, and as a result we might need to adapt this process to better fit our needs as a group. Specifically, we should focus on developing a medium where we can have seamless knowledge transfer and can leverage the collective knowledge of our group. I think we can work towards this goal by shifting to an asynchronous mode as our primary means of communication. Many software groups have adopted [https://slack.com/help Slack] as their tool for asynchronous communication. | Our software team is unique in that each member is working on their own individual projects instead of a shared development responsibility. This challenges some of the ideas around the Scrum process, and as a result we might need to adapt this process to better fit our needs as a group. Specifically, we should focus on developing a medium where we can have seamless knowledge transfer and can leverage the collective knowledge of our group. I think we can work towards this goal by shifting to an asynchronous mode as our primary means of communication. Many software groups have adopted [https://slack.com/help Slack] as their tool for asynchronous communication. | ||
| Line 16: | Line 16: | ||
* You can [https://slack.com/help/articles/201355156-Guide-to-desktop-notifications adjust notification] settings to see all messages from this channel. | * You can [https://slack.com/help/articles/201355156-Guide-to-desktop-notifications adjust notification] settings to see all messages from this channel. | ||
| − | This will take some effort to train us into the habit of using the platform, but I believe that it will help open a low-friction medium for communication in our software group. | + | This will take some effort to train us into the habit of using the platform, but I believe that it will help open a low-friction medium for communication in our software group. |
| − | |||
== Stand-up Examples == | == Stand-up Examples == | ||
Revision as of 17:58, 14 April 2020
Contents
Using Slack for Stand-up
Our software team is unique in that each member is working on their own individual projects instead of a shared development responsibility. This challenges some of the ideas around the Scrum process, and as a result we might need to adapt this process to better fit our needs as a group. Specifically, we should focus on developing a medium where we can have seamless knowledge transfer and can leverage the collective knowledge of our group. I think we can work towards this goal by shifting to an asynchronous mode as our primary means of communication. Many software groups have adopted Slack as their tool for asynchronous communication.
- Replace daily stand-up calls with check-ins to SCEC Software Slack Channel
- Have 1 hr max weekly software round-table meeting for technical discussions / knowledge transfer
- Technical issues
- Design discussions
- New techologies (e.g., CI / plotly / etc)
- Use Slack for other various work and non-work related asnyc communications (eg., sharing news, interesting tid-bits (Phil's drone vids), etc.)
How-to Check in via Slack
- Every morning when you start working open the slack desktop application (there is a web client, but I have the best experience with the desktop app)
- In the #stand-up channel, write a short blurb about the day
- You can adjust notification settings to see all messages from this channel.
This will take some effort to train us into the habit of using the platform, but I believe that it will help open a low-friction medium for communication in our software group.
