The Agile Daily Standup - AgileDad

People Pay For The Story.. - How Do We Focus On Outcome - Agile 2023 I love the story of the European tourist who loses everything but her passport and how well it ties into customers and customer relations! 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/

Individuals And Interactions Were Alive And Well at Agile 2023! I was SUPER excited to catch up with so many old friends and meet so many new ones! The conference was a roaring success and one of the highlights was to walk and talk with Jim Highsmith, one of the original authors of the Agile Manifesto. You have to listen to the episode to learn more! 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/

Vanilla Ice Was The PERFECT Agile Coach - Agile 2023 Many have asked if I can speak at their conference, work retreat, or even to their teams... Here is a link to what I offer and how you can book me! AgileDad Speaks Website It is hard to believe that it has been a week since I gave this conference presentation at Agile 2023! This time I decided to give you a little insight into the presentation and what topics surrounding growth mindset were covered. You may even get to hear me rap a little... Stop Collaborate and Listen! 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/

The Journey To Speaking at Agile 2023 - What I Learned and Who I Met I start this episode off with a story about a homeless man who is gifted 15 dollars from a wealthy businessman and what he does with his newfound wealth. I liken this to my journey to share all that I have with others and how my journey to and through the Agile 2023 Conference was nothing less than magical. https://fb.watch/m2se6vDzOX/?mibextid=T3FBdp 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/

Celebrating Episode 850 - Three Questions with Bob Hartman - Agile For All This is a VERY special episode of The Daily Standup Podcast! I have my dear friend Bob Hartman joining me and have I mentioned that he is one of my favorite human beings on the planet? Tune in to live laugh and learn as we share some fun stories and offer an inspiring challenge. https://www.linkedin.com/in/bobhartman/ https://agileforall.com/ 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/

Here are eight critical side effects of this Product Backlog anti-pattern: Encourages Waste: An oversized Product Backlog fosters waste by investing time in items that may never be developed due to the continuous discovery of more valuable tasks. It’s a clear violation of Agile Manifesto principles; particularly, simplicity—the art of maximizing the work not done—is essential. Sunk Cost Fallacy Risk: A large Product Backlog can lead to the sunk cost fallacy. Teams may continue to refine and prioritize items because they’ve already invested time into them rather than because they add significant value. This behavior contradicts the Agile Manifesto’s principle of continuous improvement and adaptation. Leads to Analysis Paralysis: A huge Product Backlog can cause what’s known as analysis paralysis, where the sheer volume of items becomes overwhelming, leading to indecision and delay. The team might spend excessive time evaluating, prioritizing, and re-prioritizing items, which detracts from their capacity to focus on actual product development. This excess of choices often slows down decision-making processes, making it difficult for the team to determine where to start or what to focus on next. Ultimately, this slows down the entire project, diverting energy away from creating value for the customer and towards managing the Product Backlog itself. Damages Stakeholder Engagement: A bloated Product Backlog presents a significant challenge regarding effective communication. The vast number of items can make it difficult for stakeholders to comprehend the plan, the progress, and the order of priority, leading to potential misalignment of expectations. Stakeholders may struggle to find their specific interests within the large list, confusing them and potentially causing a feeling of detachment. Crowding Out Effect: A comprehensive, oversized Product Backlog may inadvertently discourage stakeholders and team members from contributing their ideas and insights. The backlog’s perceived completeness might give the impression that there’s no room or need for additional input, potentially missing valuable ideas and insights. Inhibits Innovation: A huge Product Backlog can unintentionally stifle the creative energy within the Scrum Team. The lengthy list of tasks can create a culture of ‘checking off the boxes’ where the team focuses more on completing the tasks rather than exploring and innovating. The team may feel constrained, perceiving that there’s no room for new ideas, which can limit their creative problem-solving skills and deter them from finding innovative solutions. This mindset contradicts the Scrum value of ‘openness’ and the Agile principle of harnessing change for the customer’s competitive advantage. False Sense of Security: An exhaustive Product Backlog may provide a false sense of security, an illusion of control. It might seem like the Scrum team identified all the necessary work, reducing the perceived need for discovery and learning. This misalignment with the Scrum Guide, which advocates for iterative learning and discovery, can be harmful. Encourages Early Optimization: A bulging Product Backlog can lead to premature optimization, as the team may feel compelled to design systems or workflows that anticipate the completion of future backlog items, resulting in unnecessary complexity, contributing to waste if these tasks later change or get deprioritized. This approach conflicts with the Agile principle of simplicity—the art of maximizing the amount of work not done—and the Scrum value of focus, as it encourages effort toward uncertain future needs rather than the most valuable present ones. 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/⁠

What Is a REAL Stakeholder? Do you know the difference between a Key Stakeholder, Stakeholder, and an Interested Party? Join V. Lee Henson and learn more about these differences and why they should matter to you! 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/⁠

Everyone agrees that in complex work, clear goals give guidance to what needs attention and what doesn’t (right now). They also see how goals are the glue that binds individuals into a team by giving them a shared purpose. A shared goal gives Scrum teams focus on what is important during a Sprint while allowing flexibility to adjust course and avoid emerging obstacles as needed. Shared goals are the foundation of the Scrum framework. It is what pulls everything together, and gives meaning and purpose to everything that happens in Scrum. In addition to a Sprint Goal, we would also define a daily goal. These teams not only focused each Sprint on one Sprint Goal, but they also identified one daily goal for the entire team, each day! Seems impossible? Maybe… But it’s definitely worth a try. It’s a great way to improve collaboration, focus, and commitment. In general, it’s a perfect booster for team morale. It’s probably not difficult to find reasons why this won’t work for your team, but those reasons might also be symptoms of deeper problems in your team. 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/⁠

Agile project management represents an iterative methodology for planning and guiding project processes. It centers on dividing project work into shorter timeframes, known as sprints or iterations. Agile project management empowers software development teams to work swiftly and collaboratively on projects while remaining adaptable to evolving requirements. It also facilitates rapid response to feedback, enabling adjustments to be made during each sprint and product cycle. An Agile project is finished in manageable pieces, much like Agile software development. Iteration in software development refers to a single cycle of growth. The project team assesses and rates each segment or iteration and should comprise representatives from various stakeholders. Insights gained from these critiques serve as a basis for determining the subsequent steps in the project. 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/⁠

Once upon a time, in a small village nestled among rolling hills, there lived a water bearer. Every day, he would walk to the nearby stream, carrying two large pots tied to a pole that rested upon his shoulders. One pot was perfect, without a flaw, while the other had a deep crack running along its side. As the water bearer made his way from the stream to his master's house, the perfect pot would hold its water securely, delivering a full portion every time. It felt proud of its accomplishment, fulfilling its purpose with perfection. But the cracked pot felt ashamed and burdened by its flaw. No matter how much water the water bearer poured into it, it leaked along the way, leaving a trail of water droplets behind. One day, as they reached the master's house, the cracked pot could no longer bear its imperfection and whispered softly to the water bearer, "I'm sorry for my flaw. I'm ashamed that I can't do my job properly. I'm wasting your efforts and leaving a mess behind." The water bearer smiled warmly and replied, "My dear cracked pot, do not be troubled. Look around you." The pot raised its gaze and noticed a path adorned with vibrant flowers, blooming in a colorful array. The pot was puzzled and asked, "But how is this possible? I have been leaking water along the way." The water bearer gently explained, "You see, I have known about your crack for a long time. Instead of letting it discourage me, I planted flower seeds along your side of the path. Every day, as we walked back, you watered them with the droplets that leaked from you. Without your cracks, these flowers wouldn't have blossomed so beautifully." The cracked pot was filled with awe and wonder. It realized that its flaw had unknowingly brought beauty into the world. It no longer felt ashamed but embraced its uniqueness. From that moment on, it took pride in its imperfection, understanding that it had a purpose and could bring joy to others. As time went on, the cracked pot and the water bearer continued their daily journey. The pot no longer saw itself as broken but as a vessel that nurtured life. It no longer compared itself to the perfect pot, for it had found its own purpose, its own way of making a difference. The village people marveled at the stunning flowers that lined the path, unaware of the pot's role in their creation. The cracked pot learned that it wasn't defined by its flaw, but by the beauty it had unknowingly helped cultivate. And so, the parable of the cracked pot teaches us a profound lesson. It reminds us that even our perceived flaws and weaknesses can have unexpected beauty and bring joy to others. Our imperfections, like the pot's crack, can make us unique and provide opportunities for growth and positive impact. We need only embrace our true selves, for within our flaws lie the seeds of beauty waiting to bloom. 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/⁠