The Agile Daily Standup - AgileDad

AgileDad ~ V. Lee Henson

Rise and shine, Agile enthusiasts! Kickstart your day with 'The Agile Daily Standup' podcast. In a crisp 15 minutes or less, AgileDad brings you a refreshing burst of Agile insights, blended seamlessly with humor and authenticity. Celebrated around the world for our distinct human-centered and psychology-driven approach, we're on a mission to ignite your path to business agility. Immerse yourself in curated articles, invaluable tips, captivating stories, and conversations with the best in the business. Set your aspirations high and let's redefine agility, one episode at a time with AgileDad!

  1. 2D AGO

    Team Dynamics - The Soloist - Mike Cohn

    Team Dynamics - The Soloist - Mike Cohn It’s always great when a high performer joins a team. A true star can elevate everyone through their attitude, ability, and commitment.Think of them like a brilliant musician in a band—a lead guitarist or vocalist who’s not just talented, but who listens, collaborates, and knows how to bring out the best in everyone else. They don’t just shine—they make the whole group sound better.But sometimes, the high-performing teammate turns out to be more comfortable as a soloist.Soloists want to stand out—but often at the expense of the ensemble. They can sometimes play over others, ignore the rhythm of the group, and expect the spotlight on every track. They might be technically excellent, but they’re out of sync.These kinds of high performers sometimes overvalue their individual contribution and subtly (or not-so-subtly) expect special treatment: the final say in decisions, the best projects, or freedom from feedback and constraints. When they take risks and things go wrong, they assume their talent will shield them—leaving the rest of the team to clean up after the show.The difference between a true bandmate and a soloist isn’t skill—it’s orientation. One makes the team tighter. The other plays their own set.That’s where the Scrum Master comes in.A good Scrum Master notices when someone’s out of sync and steps in early—before the rhythm breaks.Rather than act on their own opinion, the Scrum Master should have the private conversations necessary to confirm that the rest of the team also feels the soloist is throwing off their rhythm.If the feeling is widespread, then the Scrum Master should have a private conversation with the soloist about any behavior that is detrimental to the team. If, for example, a diva is ignoring what the team selected during sprint planning and instead chooses to work on pet projects, the diva needs to understand that’s not acceptable.If a private conversation doesn’t help, the Scrum Master can escalate the problem to the solist’s functional manager. Consider including the soloist in that conversation so that there’s no miscommunication and everyone is on the same page.Don’t let one person throw off the rhythm of the whole team. To succeed with agile, we don’t need virtuosos; we need great bands. How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/

    4 min
  2. OCT 8

    How to Engage Busy Stakeholders - Mike Cohn

    How to Engage Busy Stakeholders - Mike Cohn We often find ourselves reliant on others outside the team.For example, an agile team may get stuck waiting for feedback on the latest features or input on what to build next because a key stakeholder has never shown up for a sprint review. Without that stakeholder’s feedback, the team is impeded: unable to determine if what they’ve created is what’s needed.The team nags, pleads, and cajoles. But still they’re left waiting because stakeholders are often busy, and they just can’t (or won’t) find the time.You’ve tried moving the sprint review meeting to more convenient times. You’ve sent agendas that make it clear the stakeholder’s most desired feature is the one being discussed in the review.But time and time again, something comes up at the last minute and the stakeholder is a no show.In these instances, it’s time to take the meeting to them.  When a stakeholder won’t (or can’t) show up for the team, it’s time for a different approach:  Schedule time on the stakeholder’s calendar for a meeting a few days before sprint planning.Use that block of time to work together on what the team needs.Schedule a Non-Meeting Meeting Tip within the Tip: Want more help with team dynamics and stakeholder management? Try my free Scrum Team Reset training. It’s three videos from me that will help you find new ways to take your team from good to great. When I schedule the meeting, I’ll sometimes be very clear what the meeting is about: “I want to go over such-and-such with you before the review.” Other times, I’ll be more vague: “I need to chat about the project.”Use whatever language you need to secure time on the person’s calendar. Why? Because we are all more willing to cancel appointments with ourselves than we are to cancel an appointment with someone else. By putting time on their calendar that they’re reluctant to cancel, you’ve secured enough time for them to actually do the work. Get the To-Do to DoneDuring the meeting, explain to them the work you need them to do (look at the feature and give feedback or clarify how the feature should work.) Then, use the time to step through the implementation (or plan) with them.This results in two things: the team gets the information it needs. The stakeholder finds that the thing they’ve been putting off really wasn’t so bad once they focused on getting it done. Why This WorksWhen stakeholders show an inability to get work or answers to you at appropriate times, it’s time to intervene. Maybe they’re worried their time will be wasted in a review where their feature is one of many being discussed.Maybe “review the xyz feature” has been on their to-do list and keeps getting bumped down. Or maybe they haven’t actually scheduled a specific time to work on it.No matter the reason, the work the team needs done is not happening. And your best chance of helping the stakeholder do that work is to schedule time with the stakeholder directly. And then use that time to make it happen.Should stakeholders be able to do this on their own?Sure.But we all struggle at times. My experience is that after doing this a handful of times with a stakeholder, most stakeholders will form a new habit and be able to continue without you.In other cases, you and the stakeholder will discover it actually is more efficient when done together, and you’ll keep a recurring meeting on their calendar that isn’t the review. That’s perfectly fine, too.Stakeholders are often busy. And that can cause them to take longer to respond than a fast-moving agile team might like. Finding creative solutions that keep the team moving (even if it’s not something Scrum prescribes) is the best way to help advance a team from good to great, How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/

    7 min
4.9
out of 5
29 Ratings

About

Rise and shine, Agile enthusiasts! Kickstart your day with 'The Agile Daily Standup' podcast. In a crisp 15 minutes or less, AgileDad brings you a refreshing burst of Agile insights, blended seamlessly with humor and authenticity. Celebrated around the world for our distinct human-centered and psychology-driven approach, we're on a mission to ignite your path to business agility. Immerse yourself in curated articles, invaluable tips, captivating stories, and conversations with the best in the business. Set your aspirations high and let's redefine agility, one episode at a time with AgileDad!

You Might Also Like