Difference between revisions of "Stand-up Meetings"
From SCECpedia
Jump to navigationJump to search| (15 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == | + | == Stand-up Questions == |
| + | We will use 3 standup questions to focus on identifying things that we have, or plan, to “complete". | ||
| + | |||
| + | #What have you completed since the last meeting? | ||
| + | #What do you plan to complete by the next meeting? | ||
| + | #What is getting in your way | ||
| + | |||
| + | The intent of these questions is to emphasize completions of tasks, rather than effort spent. | ||
| − | 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. | + | == Using Zoom for Stand-up Meetings == |
| + | |||
| + | The SCEC IT Calendar has an entry with a link to a zoom meeting that is the standard connection for our Zoom stand-up calls. | ||
| + | |||
| + | == Using Slack for Stand-up Meetings == | ||
| + | |||
| + | In many cases, SCEC software team members are working as the only software developer on a group research project, while the 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 8: | Line 21: | ||
** Design discussions | ** Design discussions | ||
** New technologies (e.g., CI / plotly / etc) | ** 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 | + | * Use Slack for other various work and non-work related asnyc communications (eg., sharing news, interesting tid-bits, etc.) |
=== How-to Check in via Slack === | === 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) | + | * Every morning when you start working open the [https://slack.com/downloads Slack desktop application] (there is a web client, but I have the best experience with the desktop app) |
| − | * | + | * Workspace URI: scecsoftware.slack.com |
| − | * In the #stand-up channel, write a short blurb about the day | + | * In the #stand-up channel, write a short blurb about the day. Everyone in the daily stand-up calls has access to this room. |
* 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. | ||
| + | |||
| + | === Slack Channels === | ||
| + | * In the app you'll see a "Channels" drop-down in the left panel. | ||
| + | * Click the '+' icon to manage the channels in the room. | ||
| + | * Right now we have individual project channels (eg., #broadband, #cybershake, #cxm, etc) and #stand-up and others | ||
| + | * It should be straight-forward which content goes in which channels | ||
| + | ** Use the #stand-up channel for daily sync-up communications | ||
| + | ** Use the project channels for project communications | ||
| + | ** Use general for general but work-related discussions | ||
| + | ** Use random for other non-work stuff | ||
| + | * Feel free to make your own channels. View this as our living chat room and we can evolve it as we see fit :) | ||
| + | |||
| + | === Slack Apps === | ||
| + | Slack can integrate Apps into the message system which enables it to become a primary means of communication | ||
| + | * [https://scecsoftware.slack.com/apps/A5GE9BMQC-zoom?utm_source=in-prod&utm_medium=inprod-btn_app_install-index-click Zoom app] | ||
| + | * [https://scecsoftware.slack.com/apps/AFV5ECLBZ-outlook-calendar?utm_source=in-prod&utm_medium=inprod-btn_app_install-index-click Outlook Calendar app] | ||
| + | * [https://scecsoftware.slack.com/apps/A8GBNUWU8-github?utm_source=in-prod&utm_medium=inprod-btn_app_install-index-click Github App] | ||
== Stand-up Examples == | == Stand-up Examples == | ||
| Line 22: | Line 52: | ||
*[https://www.youtube.com/watch?v=i7_RPceEIYE Standup is Not A Status Meeting] | *[https://www.youtube.com/watch?v=i7_RPceEIYE Standup is Not A Status Meeting] | ||
*[https://www.youtube.com/watch?v=H02BlTXpcto Different way to do Stand-up Meetings] | *[https://www.youtube.com/watch?v=H02BlTXpcto Different way to do Stand-up Meetings] | ||
| + | *[https://www.agilealliance.org/glossary/three-qs Standup Questions] | ||
== Related Entries == | == Related Entries == | ||
Latest revision as of 06:54, 3 July 2020
Contents
Stand-up Questions
We will use 3 standup questions to focus on identifying things that we have, or plan, to “complete".
- What have you completed since the last meeting?
- What do you plan to complete by the next meeting?
- What is getting in your way
The intent of these questions is to emphasize completions of tasks, rather than effort spent.
Using Zoom for Stand-up Meetings
The SCEC IT Calendar has an entry with a link to a zoom meeting that is the standard connection for our Zoom stand-up calls.
Using Slack for Stand-up Meetings
In many cases, SCEC software team members are working as the only software developer on a group research project, while the 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, 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)
- Workspace URI: scecsoftware.slack.com
- In the #stand-up channel, write a short blurb about the day. Everyone in the daily stand-up calls has access to this room.
- 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.
Slack Channels
- In the app you'll see a "Channels" drop-down in the left panel.
- Click the '+' icon to manage the channels in the room.
- Right now we have individual project channels (eg., #broadband, #cybershake, #cxm, etc) and #stand-up and others
- It should be straight-forward which content goes in which channels
- Use the #stand-up channel for daily sync-up communications
- Use the project channels for project communications
- Use general for general but work-related discussions
- Use random for other non-work stuff
- Feel free to make your own channels. View this as our living chat room and we can evolve it as we see fit :)
Slack Apps
Slack can integrate Apps into the message system which enables it to become a primary means of communication
Stand-up Examples
- Short Example
- Standup is Not A Status Meeting
- Different way to do Stand-up Meetings
- Standup Questions
