Difference between revisions of "Stand-up Meetings"
| Line 1: | Line 1: | ||
== Using Slack for Stand-up == | == Using Slack for Stand-up == | ||
| − | + | In many cases, SCEC software team members are working as the only software developer on a group research project, while SCRUM process is designed to support project on which multiple programmers share 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 communications channels and coordination process that enables seamless knowledge transfer and that leverages the collective knowledge of our group. We will work towards this goal by adding an asynchronous mode to our group communications. Many software groups have adopted [https://slack.com/help Slack] as their tool for asynchronous communication. | |
* Contribute to daily stand-up calls with check-ins to SCEC Software Slack Channel | * Contribute to daily stand-up calls with check-ins to SCEC Software Slack Channel | ||
| Line 7: | Line 7: | ||
** Technical issues | ** Technical issues | ||
** Design discussions | ** Design discussions | ||
| − | ** New | + | ** New technologies (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.) | * 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 === | === How-to Check in via Slack === | ||
Revision as of 18:05, 14 April 2020
Contents
Using Slack for Stand-up
In many cases, SCEC software team members are working as the only software developer on a group research project, while SCRUM process is designed to support project on which multiple programmers share 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 communications channels and coordination process that enables seamless knowledge transfer and that leverages the collective knowledge of our group. We will work towards this goal by adding an asynchronous mode to our group communications. Many software groups have adopted Slack as their tool for asynchronous communication.
- Contribute to 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 technologies (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.
