Stand-up Meetings - Revision history

Maechlin: /* Using Slack for Stand-up Meetings */

2020-07-03T06:54:04Z

Using Slack for Stand-up Meetings

Maechlin: /* Stand-up Questions */

2020-04-16T01:39:18Z

Stand-up Questions

Maechlin at 01:37, 16 April 2020

2020-04-16T01:37:12Z

Maechlin: /* Stand-up Questions */

2020-04-15T17:42:56Z

Stand-up Questions

Maechlin: /* Using Zoom for Stand-up Meetings */

2020-04-15T17:39:58Z

Using Zoom for Stand-up Meetings

Maechlin at 17:38, 15 April 2020

2020-04-15T17:38:44Z

Maechlin: /* Stand-up Examples */

2020-04-15T16:38:16Z

Stand-up Examples

Maechlin at 16:23, 15 April 2020

2020-04-15T16:23:25Z

Wsavran: /* How-to Check in via Slack */

2020-04-14T18:24:24Z

How-to Check in via Slack

Wsavran: /* How-to Check in via Slack */

2020-04-14T18:24:08Z

How-to Check in via Slack

@@ Line 21: / Line 21: @@
 ** 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.)
+* 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 ===

@@ Line 1: / Line 1: @@
 == Stand-up Questions ==
-Based on Stand-up best practices, we will use 3 standup questions. These questions now focus on identifying things that we have, or plan, to “complete".
+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?
@@ Line 6: / Line 6: @@
 #What is getting in your way
-The intent of these questions is to emphasize completions of tasks, rather than effort spent. While it is common to hear “yesterday I worked on X… today I will continue working on X… everything’s fine”;  it may be better to say “I pass”.
+The intent of these questions is to emphasize completions of tasks, rather than effort spent.
 == Using Zoom for Stand-up Meetings ==

← Older revision		Revision as of 01:37, 16 April 2020
Line 6:		Line 6:
	#What is getting in your way		#What is getting in your way

−	~~<b>Common Pitfalls</b>~~
	The intent of these questions is to emphasize completions of tasks, rather than effort spent. While it is common to hear “yesterday I worked on X… today I will continue working on X… everything’s fine”; it may be better to say “I pass”.		The intent of these questions is to emphasize completions of tasks, rather than effort spent. While it is common to hear “yesterday I worked on X… today I will continue working on X… everything’s fine”; it may be better to say “I pass”.

@@ Line 1: / Line 1: @@
 == Stand-up Questions ==
+Based on Stand-up best practices, we will use 3 standup questions. These questions now focus on identifying things that we have, or plan, to “complete".
-−
 == Using Zoom for Stand-up Meetings ==

← Older revision		Revision as of 17:39, 15 April 2020
Line 5:		Line 5:
	== Using Zoom for Stand-up Meetings ==		== 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 ==		== Using Slack for Stand-up Meetings ==

← Older revision		Revision as of 17:38, 15 April 2020
Line 1:		Line 1:
		+	== Stand-up Questions ==
		+
		+
		+
		+	== Using Zoom for Stand-up Meetings ==
		+
		+
	== Using Slack for Stand-up Meetings ==		== Using Slack for Stand-up Meetings ==

@@ Line 39: / Line 39: @@
 *[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]
 == Related Entries ==

@@ Line 1: / Line 1: @@
 == 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 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.
+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

@@ Line 12: / Line 12: @@
 === How-to Check in via Slack ===
 * 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)
-* Our SCEC software group has the workspace URI scecsoftware.slack.com All of us are members of the room.
+* 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 [https://slack.com/help/articles/201355156-Guide-to-desktop-notifications adjust notification] settings to see all messages from this channel.