DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
Securing Your Software Supply Chain with JFrog and Azure
Register Today

Trending

  • IDE Changing as Fast as Cloud Native
  • Future of Software Development: Generative AI Augmenting Roles and Unlocking Co-Innovation
  • Stack in Data Structures
  • Opportunities for Growth: Continuous Delivery and Continuous Deployment for Testers

Trending

  • IDE Changing as Fast as Cloud Native
  • Future of Software Development: Generative AI Augmenting Roles and Unlocking Co-Innovation
  • Stack in Data Structures
  • Opportunities for Growth: Continuous Delivery and Continuous Deployment for Testers
  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. Managers: For Effective Stand Up Meetings, Do Your Homework

Managers: For Effective Stand Up Meetings, Do Your Homework

Before stepping foot into the stand-up, managers need to understand the early warning signs of risks to the sprint.

Sasha Rezvina user avatar by
Sasha Rezvina
·
Jun. 21, 19 · Opinion
Like (5)
Save
Tweet
Share
11.73K Views

Join the DZone community and get the full member experience.

Join For Free

Meeting

Stand up meetings don't have to be the worst. It just takes a little management preparation.
“The daily stand up meeting is not another meeting to waste people's time. It will replace many other meetings, giving a net savings several times its own length.” --  XP Rules

One of three things happens at every standup:

  1. Issues are omitted.

  2. Issues are delayed.

  3. Issues are glossed over.

It may be because a developer doesn’t want to look bad in front of their peers. Or, perhaps, they’d just rather have the satisfaction of working through the challenge on their own. Regardless, all developers are subject to biases that can sway their decision on whether and when they share critical problems.

One person in the room, however, is usually too far from the codebase to recognize all the issues that are at-risk of derailing the sprint. And that person -- whether it’s a manager, a team lead, or a scrum master -- is usually the one responsible for making sure the team stays on track.

This creates an undesirable dynamic. Those who are closest to the problems don’t have the time to step back and see the forest for the trees. The manager, who is responsible for keeping the sprint on track, doesn’t have the visibility to uncover roadblocks and bottlenecks.

Developers end up inadvertently serving as gatekeepers to critical issues.

To change this dynamic, the manager needs to do a bit of research. Before stepping foot into the stand-up, they need to understand the early warning signs of risks to the sprint.

Identify the signals through the noise

The first thing the manager should look at is: How fast is the team moving? Is this pace faster or slower than normal?

Currently, most managers track some version of planned vs. completed work. They might look at story points or tickets closed. While these are useful for assessing planning effectiveness, they’re not diagnostic. You can’t tell whether the issue is with capacity or efficiency.

A more accurate reflection of pace is an activity metric, such as a pushes or commit count. When activity is lower than normal, the manager knows that there are obstacles holding back the engineers from coding.

If this activity count is low, the manager will want to further investigate where developers might be stuck. They should look out for three red flags:

  • Long-running pull requests: Are there pull requests that have been open for more than three business days? If so, who can help get it out the door, or break it up into smaller chunks?

  • High review cycles: Is there a pull request that has been passed back and forth between the reviewer and the author several times?

  • Large pull requests: Are contributors opening pull requests in small, easy-to-review units? If not, those pull requests are harder to review and at greater risk of causing an issue when they are merged.

If pace is slow, yet no pull request is growing unwieldy, you’ll want to pull a list of engineering activities. Check tickets, commits, merges, and reviews to ensure that the team’s work aligns with what was planned and expected.

You can surface this information by setting up a Git history statistics tool, like GitStats, and then pull the data before each standup. Or, you can use an Engineering Intelligence platform like Velocity to see all of these risks in one place.

 Regardless of how you pull the data, spending 15 minutes to catch up on all the important work in progress ensures that no time is wasted catching up during actual standup. 

Shift the conversation toward action

With more shared context, the conversation shifts from talking about problems to talking about solutions. Here are two scenarios played out side by side:

Discuss solutions

The opportunity to offer support is much greater when you start the conversation with actual data. It takes the onus off of each developer to ask for help and transforms the meeting into a constructive way to keep the team on pace.

Stand-up is not roll-call

The value in disrupting developers for face-time is to identify and plan for addressing bottlenecks -- not for proving that they’re working.

Once time is re-allocated toward identifying risks and ensuring the team is on track to hit this sprint’s goals, you’ll find that finally, the stand-up is providing more value than a meeting that is several times its length.

All that’s required is a bit of preparation.

Further reading

Helping Overcome Impediments Between Managers and Agile Teams

You're Doing It Wrong: Daily Stand-Ups

Git scrum agile

Published at DZone with permission of Sasha Rezvina. See the original article here.

Opinions expressed by DZone contributors are their own.

Trending

  • IDE Changing as Fast as Cloud Native
  • Future of Software Development: Generative AI Augmenting Roles and Unlocking Co-Innovation
  • Stack in Data Structures
  • Opportunities for Growth: Continuous Delivery and Continuous Deployment for Testers

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com

Let's be friends: