Daily Scrum Patterns: The Sprint Backlog at the Daily Scrum

This blog post is part of a series of blog posts on Daily Scrum patterns.  For some background, you might find it useful to read my previous article on a simple Scrum Patterns framework.  Daily Scrum Patterns fall under the category of “Scrum Technique Patterns”, as introduced in that article.

Today we’ll talk about “Obstacle Resolution Patterns”

Notes:

• All Scrum Patterns are displayed as such: <Scrum Pattern Name>.
• All patterns currently link to the same Daily Scrum Patterns Summary Chart, where you can find out more info about each pattern.

“The Sprint Backlog at the Daily Scrum” Patterns

While it’s a popular and proven practice to <View the Sprint Backlog at the Daily Scrum>, it’s a controversial practice to <Update the Sprint Backlog at the Daily Scrum>, as the updating can detract from the true objectives and focus of the Daily Scrum in some situations.

Also, don’t forget to be creative and <Create Your Own Pattern>, and don’t ever hesitate to use a technique that is not described by a documented pattern.

The Sprint Backlog at the Daily Scrum Patterns:

• <View the Sprint Backlog at the Daily Scrum>
• <Update the Sprint Backlog at the Daily Scrum>

Daily Scrum Patterns: Who Attends the Daily Scrum?

This blog post is part of a series of blog posts on Daily Scrum patterns.  For some background, you might find it useful to read my previous article on a simple Scrum Patterns framework.  Daily Scrum Patterns fall under the category of “Scrum Technique Patterns”, as introduced in that article.

Today we’ll talk about “Obstacle Resolution Patterns”

Notes:

• All Scrum Patterns are displayed as such: <Scrum Pattern Name>.
• All patterns currently link to the same Daily Scrum Patterns Summary Chart, where you can find out more info about each pattern.

Who Attends? Patterns

According to the Scrum Guide, the Development Team must attend. With many teams, and especially Shu level teams, the <Scrum Master Attends>. It’s usually a good practice if the <Product Owner Attends> so that they can help the Development Team if needed, often times at <The After Party>. It’s usually not good if an <Authority Figure Attends> on a regular basis.

Also, don’t forget to be creative and <Create Your Own Pattern>, and don’t ever hesitate to use a technique that is not described by a documented pattern.

Who Attends? Patterns:

• <Development Team Only>
• <Scrum Master Attends>
• <Product Owner Attends>
• Anti-Pattern: <Authority Figure Attends>

Daily Scrum Patterns: Who Participates in the Daily Scrum?

This blog post is part of a series of blog posts on Daily Scrum patterns.  For some background, you might find it useful to read my previous article on a simple Scrum Patterns framework.  Daily Scrum Patterns fall under the category of “Scrum Technique Patterns”, as introduced in that article.

Today we’ll talk about “Obstacle Resolution Patterns”

Notes:

• All Scrum Patterns are displayed as such: <Scrum Pattern Name>.
• All patterns currently link to the same Daily Scrum Patterns Summary Chart, where you can find out more info about each pattern.

Who Participates? Patterns

The Scrum Guide says that “the Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum.” However, some practitioners think it might be ok if the <Product Owner Participates> in the Daily Scrum. Having said that, it is incorrect Scrum if a <Non Scrum Team Member Participates> in the Daily Scrum, so consider using <The After Party> to let non Scrum Team Members communicate with the Scrum Team.

Also, don’t forget to be creative and <Create Your Own Pattern>, and don’t ever hesitate to use a technique that is not described by a documented pattern.

Who Participates? Patterns:

• Controversial Pattern: <Product Owner Participates>
• Anti-Pattern: <Non Scrum Team Member Participates>

Daily Scrum Patterns: Facilitation Patterns

This blog post is part of a series of blog posts on Daily Scrum patterns.  (More coming in future posts over the next weeks).  For some background, you might find it useful to read my previous article on a simple Scrum Patterns framework.  Daily Scrum Patterns fall under the category of “Scrum Technique Patterns”, as introduced in that article.

Notes:

• All Scrum Patterns are displayed as such: <Scrum Pattern Name>.
• All patterns currently link to the same Daily Scrum Patterns Summary Chart, where you can find out more info about each pattern.

Facilitation Patterns

Most teams hold the Daily Scrum as a <Standup Meeting>, but this is not required in Scrum, and some teams that are distributed feel like it’s ok to hold a <Sit Down Meeting> so long as they are faithfully executing the objectives of the Daily Scrum.

Teams just starting with Scrum might benefit from a <Close Facilitator>, so long as that doesn’t turn into a <Controlling Facilitator>. A bad practice is facilitating a Daily Scrum such that it <Turns into a Waterfall Status Meeting>.

Also, don’t forget to be creative and <Create Your Own Pattern>, and don’t ever hesitate to use a technique that is not described by a documented pattern.

Facilitation Patterns:

• <Standup Meeting>
• <Sit Down Meeting>
• <Close facilitator>
• Anti-Pattern: <Controlling Facilitator>
• Anti-Pattern: <Turns into a Waterfall Status Meeting>
• <Create Your Own Pattern>

Daily Scrum Patterns: Obstacle Resolution Patterns

This blog post is part of a series of blog posts on Daily Scrum patterns.  For some background, you might find it useful to read my previous article on a simple Scrum Patterns framework.  Daily Scrum Patterns fall under the category of “Scrum Technique Patterns”, as introduced in that article.

Today we’ll talk about “Obstacle Resolution Patterns”

Notes:

• All Scrum Patterns are displayed as such: <Scrum Pattern Name>.
• All patterns currently link to the same Daily Scrum Patterns Summary Chart, where you can find out more info about each pattern.

Obstacle Resolution

Many teams <Defer Obstacle Resolution> until after the Daily Scrum, but some teams <Allow Obstacle Resolution> if they can still avoid busting the 15 minute time-box. Having said that, it’s generally considered a bad practice if your team decides to <Save All Obstacles For the Daily Scrum>.

Some teams use <The After Party> to handle obstacle resolution and other conversations inappropriate for the Daily Scrum, and that’s probably fine unless <The After Party Defeats the Purpose of the Daily Scrum>.

Also, don’t forget to be creative and <Create Your Own Pattern>, and don’t ever hesitate to use a technique that is not described by a documented pattern.

Obstacle Resolution Patterns:

• <Defer Obstacle Resolution>
• <Allow Obstacle Resolution>
• Anti-Pattern: <Save All Obstacles For the Daily Scrum>
• <The After Party>
• Anti-Pattern: <The After Party Defeats the Purpose of the Daily Scrum>
• <Create Your Own Pattern>

What Daily Scrum Patterns do you like to use?  Sound off in the comments.

Daily Scrum Patterns: Talk Order

This blog post is part of a series of blog posts on Daily Scrum patterns.  (More coming in future posts over the next weeks).  For some background, you might find it useful to read my previous article on a simple Scrum Patterns framework.  Daily Scrum Patterns fall under the category of “Scrum Technique Patterns”, as introduced in that article.

Notes:

• All Scrum Patterns are displayed as such: <Scrum Pattern Name>.
• All patterns currently link to the same Daily Scrum Patterns Summary Chart, where you can find out more info about each pattern.
  

Talk Order

Most teams start out with a <Round Robin> approach. Teams that are distributed or are highly self organizing might use the <Talking Stick> approach. Some teams become better at getting work done if they <Walk The Items> instead, but use caution as that approach can lead to a Daily Scrum that <Turns Into Waterfall Status Meeting>.

Also, don’t forget to be creative and <Create Your Own Pattern>, and don’t ever hesitate to use a technique that is not described by a documented pattern.

Talk Order Patterns:

• <Round Robin>
• <Talking Stick>
• Controversial Pattern: <Walk the Items>
• <Create Your Own Pattern>