The Agile Daily Standup - AgileDad

Why Soft Skills Outlast Technical Skills on Product Teams - Mike CohnAnyone who has worked in product development for more than a few years has seen the same pattern repeat itself.The technical skills that once felt essential gradually—or sometimes suddenly—become obsolete. Tools change. Frameworks fall out of favor. Architectures that once seemed modern start to look dated.This isn’t new, but it is accelerating.The half-life of technical skills keeps shrinking, especially in technology. In the 1980s, it took ten years for half of what you knew to become outdated. Today, it is four years, and will soon fall below two years according to a Stanford professor. This raises an important question for leaders:Where does investment in people have the greatest long-term impact?Technical skills are necessary, of course. But they are rarely durable.Soft skills behave very differently.When someone learns how to collaborate well, make good decisions, facilitate discussions, or lead others, those skills don’t decay at the same rate. Instead, they tend to compound. They become part of how that person works.Learning how to learn is a good example. Once someone develops that capability, it stays with them. The same is true for decision-making, leadership, and collaboration. These are skills that can continue to improve over time—but they don’t become irrelevant.I once saw just how important this was during a demo to a group of nurses.A programmer demonstrated new functionality and showed text on the screen that suggested giving Saltine crackers to a newborn—clearly clinically inappropriate.He tried to explain that it was just placeholder text. The real point, he said, was the workflow, not the words.But to the nurses, the words mattered a great deal.Their professional identity is grounded in “do no harm.” What they saw on the screen violated that principle. They were ready to escalate the issue and cancel the project.What saved the project wasn’t a technical fix.It was the project manager’s soft skills.He calmed the situation, acknowledged the nurses’ concerns, explained what had happened, and persuaded them to come back a week later for a revised demo.The failure wasn’t technical—it was a failure of empathy.Product development is full of uncertainty. We work with evolving requirements, incomplete information, and users whose trust we must earn and keep.Soft skills reduce risk in these environments.Empathy helps teams understand users. Clear communication builds trust. Collaboration prevents small misunderstandings from becoming major setbacks.And when these skills improve, the benefit isn’t limited to one person.If someone learns a new technical skill, that benefit often stays with them. But when someone learns to collaborate better, the entire team benefits. Everyone gets better.This is one reason leaders often underestimate the return on investing in soft skills.The payoff isn’t always immediate or easy to measure. It tends to show up most clearly under pressure—when teams need to have hard conversations, discuss options honestly, and make good decisions quickly.That’s also when the absence of soft skills is most costly.Some leaders think these skills can wait until things slow down. In reality, pressure is when they matter most.Teams with strong soft skills can disagree productively, make tradeoffs together, and move forward with confidence—because trust was built earlier.Everyone on a product development team benefits from strong soft skills, but some roles depend on them especially heavily.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 Scope Churn? Businesses naturally want predictability from their software organizations. Promises have been made to customers, and there are business objectives to deliver as well. Often, those things have little to no wiggle room. The head of Marketing says “This must be completed on time, because we have a trade show on March 1st, and we have committed to present there.” The head of Product says “The only way we could save this angry customer was to promise that this would be completed on September 30th. If we don’t deliver, they will walk.”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 Failed Us After 18 Months - Here we go...On month eighteen, our average lead time crossed 27 days. Production defects doubled. A supposedly minor release missed its window by three weeks.Nothing had “broken.” Velocity charts still looked healthy. Every ceremony was running on time. But releases slowed, confidence eroded, and engineers stopped believing what the board said.This hurt because customers felt it immediately. Bugs lived longer, features arrived stale, and every delay came with an explanation no one trusted anymore.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/

Ernest Shackleton and Leadership When Everything Falls ApartIn 1914, Ernest Shackleton set out on what was supposed to be one of the greatest expeditions in history: the first land crossing of Antarctica. His ship, the Endurance, carried 27 men into one of the most unforgiving environments on Earth.What happened next is the part that matters.The ship never reached Antarctica.Instead, it became trapped in pack ice for months—until the pressure finally crushed the ship. The Endurance sank, leaving Shackleton and his crew stranded on drifting ice floes, more than 1,000 miles from safety, with no communication, no rescue plan, and brutal Antarctic winter closing in.From that moment on, the mission was no longer exploration.The mission became survival.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/

5 Daily Habits To Keep Your Team Motivated and InspiredManaging a team is never easy, and one of the biggest challenges is keeping everyone motivated. Motivation doesn’t come from long meetings or fancy speeches. It comes from small, everyday habits that keep energy, focus, and inspiration alive.Things like starting the day with open communication, recognizing effort right away, or giving quick feedback may seem small, but when done daily, they make a big difference. Over time, these habits build a culture where your team feels inspired to give their best.In this episiode, we’ll explore five simple daily habits that can help you keep your team motivated and inspired — not through one-time efforts, but through steady consistency.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/

Using AI to Go From User Insight to Better Backlogs - Mike CohnAI is rapidly changing how product teams work—but the biggest opportunity isn’t replacing product thinking. It’s reducing the friction between understanding users and turning those insights into high-quality backlog items.To make the ideas concrete, I use a consistent example throughout: a team building software for valet-attended parking garages, initially selling to independent operations like boutique hotels. Each step builds on the previous one, showing how AI outputs can feed naturally into your existing agile practices.With a straightforward prompt, AI can help you build a detailed persona—including hopes, concerns, emotional triggers, and decision criteria. In my example, the persona that emerged was a garage owner/operator with high staff turnover, contract-renewal anxiety, and a strong desire for predictable labor costs. Several of these insights are things I might have missed or deprioritized on my own.Understanding a persona’s aspirations—not just their functional needs—turns out to be especially valuable. Once a persona exists, you can ask AI to role-play that person and let you interview them. This is not a replacement for real user interviews, but it’s a great way to explore assumptions, test questions, and uncover gaps in your thinking.AI is also excellent at preparing interview guides for real users who match a persona. With the right prompt, it can generate a structured guide that covers: Opening context (confidentiality, purpose, time commitment)Current workflows and pain pointsDesired future state and success criteriaConstraints (including regulatory or operational)Thoughtful wrap-up questionsLooking at the results, I was struck by how much better prepared I could have been for many interviews over the years if I’d had this kind of support. Once you’re ready to move into backlog work, AI can help generate user stories and job stories that follow well-established agile guidance.By being explicit in the prompt—format, INVEST criteria, and output rules—you can get clean, ready-to-use stories that are easy to import into a backlog tool. AI can also correctly choose between user stories and job stories depending on whether the situation or the role is more important.In the valet parking example, this resulted in stories about vehicle handoff tracking, damage-claim protection, wait-time monitoring, staff accountability, and remote visibility into operations. I prefer to add acceptance criteria as a separate step, and AI handles this easily. You can ask for: A simple bullet list (great for user reviews), orGherkin (given-when-then) format for more formal specificationYou can even convert between formats later. Either way, this step quickly raises clarity and testability. AI isn’t just for generating content—it’s also useful for critique.With a structured prompt, AI can evaluate user and job stories against the INVEST criteria, identify only what’s missing, explain why, and suggest a focused improvement. This works whether the stories were written by AI or by you.Over time, you can even build a library of good and bad examples to further improve the quality of feedback you get. AI won’t replace talking to users, making judgment calls, or exercising product sense. What it can do is help teams move faster from vague ideas to concrete artifacts, surface blind spots, and raise the baseline quality of their work—especially when time or experience is limited.Used well, AI becomes a tireless collaborator: one that remembers persona details, never gets impatient with rewrites, and can move effortlessly from big-picture thinking to precise backlog items.The key mindset shift is this: don’t ask whether AI can replace parts of product discovery or backlog refinement. Ask how it can help you arrive better prepared for the conversations that still matter most.

Story Point Estimations are failing your Team! - Here We Go Again...Story Pointing wasn’t a completely novel idea. It evolved out of the Delphi method — a research technique that helped drive consensus and forecasting built on collective wisdom. In 1950s, RAND Corporation began using it as a way to forecast the effect of technology on warfare.So, it wasn’t just an idea dreamed up by someone in the Agile community randomly — no. It’s actually based on a scientific approach. Something that’s been applied and true in other disciplines for many, many years.And, when Scrum needed a prescriptive technique to help the Teams estimate and measure the amount of work the Team could consistently deliver Sprint after Sprint, this became a recommended approach.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 Makes a Great Scrum Master?When people ask me, “What does it take to be a great Scrum Master?” my first response is always — In what kind of organization?It’s not a dodge. It’s the most honest answer I can give.We talk about Scrum Masters as if the role is universal — a fixed job description that applies equally everywhere. But the reality?The Scrum Master navigating a twenty — person startup looks completely different from one guiding a 200-person enterprise team.And both are doing the job right.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 7 Two-Minute Habits That Make People Actually Want to Follow You1) Active Listen BurstHere’s the move: give someone 60 seconds of your full attention, then paraphrase what they said and ask one clarifying question. The moment someone starts speaking, resist the urge to formulate your response. Instead, just listen. Then say: “So what I’m hearing is ____. Did I miss anything?” This works because people trust leaders who make them feel truly seen — and it clears up confusion before solutions start flying around the room. Just watch out for one thing: don’t hijack the moment with your own story. Paraphrase first, then ask your question.2) Values CompassBefore or after making a key decision, take a moment to name the value guiding your choice. It’s simple: “I’m choosing X because it best serves [fairness / ownership / customer care].” This habit works because when values are explicit, your team immediately understands the trade-offs you’re making. They might not always agree with the decision, but they’ll understand the why behind it. Pro tip: keep your organization’s core values in your notes and use the same vocabulary consistently so your team recognizes the pattern.3) Openness NudgeIn the final two minutes of every meeting, create space for dissent and missing perspectives. Simply ask: “What haven’t I heard yet — especially if you disagree with me?” This is how you build psychological safety — it doesn’t happen by accident. You have to actively pull the truth out of the room. If everyone stays quiet, try a 30-second silent vote: “Type your concerns in the chat now.” This removes the social pressure and gives people a safer way to speak up. The uncomfortable truths you uncover here will save you from bigger problems later.4) No-Blame LanguageDuring reviews or post-mortems, shift the conversation from “who’s at fault” to “what system failed.” Ask: “What part of the system or process produced this outcome?” This reframing is powerful because shame kills learning, while systems thinking scales it. When people aren’t afraid of being blamed, they’ll be honest about what actually happened — and that’s where real improvement begins. Make sure to close the loop by assigning one owner and setting a deadline for fixing the system issue you’ve identified.5) Compass Check (Fair? Clear? Kind?)Before you hit send on any tough message, run it through three quick filters: Is it fair? Is it clear? Is it kind? If you can’t say yes to all three, go back and fix one line. This is emotional quality control that takes less than a minute but saves hours of cleanup later. It reduces drama, increases alignment, and helps you communicate difficult things in ways that maintain trust. The discipline of pausing before sending is what separates reactive leaders from respected ones.6) One-Line IntentAt the start of every meeting, state your goal in one clear sentence: “Goal: decide/align on ____.” That’s it. This simple habit works because people relax when they know what “done” looks like. It eliminates the wandering discussions where everyone leaves confused about what actually happened. Put this goal at the top of your agenda and read it out loud in the first 30 seconds. It sets the tone and gives everyone permission to redirect the conversation if things go off track.7) Decision Note (What/Who/When)Right after any decision, log it in one sentence: “Decision: ____. Owner: ____. By: ____.” This creates transparency and accountability while saving everyone from those frustrating moments three weeks later when no one remembers what was actually decided. Future-you won’t have to dig through five different chat threads trying to reconstruct the conversation. \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/

Why Most Agile Teams Build Features Instead of Value and How To Flip the ScriptFor a long time, I believed that the number of features we shipped was a sign of a healthy product team. New capabilities meant progress. More releases meant momentum. A packed roadmap meant ambition. And during sprint reviews, when we showcased everything we had delivered, I felt proud as if quantity itself was proof of impact.But something always nagged me. After each launch, I would look at the data or talk to users and feel this uncomfortable tension between what we had built and what had actually changed. The features were there, polished, documented, deployed but the world around them stayed strangely still. The metric didn’t move. The user behavior didn’t shift. We were launching features into the void, and the void was yawning back.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/

Start The Year With a Clean Backlog - Mike CohnThink outside the box.Do you hate that phrase as much as I do?It’s become another overused business cliché, and it bothers me for another reason: Creativity often comes from thinking inside the box.This is especially true in agile story-writing workshops. The difference between a successful story-writing workshop and one that fails to deliver often comes down to a single factor:Whether or not the product owner defines a clear, significant objective: a “box” within which the team can think.Workshops without boundaries often roam across the entire product. Teams may generate a long list of user stories but those stories lack cohesion or purpose. They’re hard to prioritize, and even harder to act on. The most productive workshops start with a simple framing statement from the product owner, like: “We’re here to think about this specific subset of the product.”That’s it. One well-chosen boundary and suddenly the team is aligned, focused, and generating better, more valuable ideas.Early in the product’s life, that boundary might be about identifying what’s needed to deliver an MVP.Later on, it might center around a Minimum Marketable Feature (MMF), something small enough to ship but valuable enough to matter. When workshops are focused around a meaningful objective, you don’t need to hold them every sprint. I typically run them about once a quarter because one well-run session generates a steady flow of high-value stories.As this year closes and a new one begins, it’s a great time to schedule a story-writing session. You might even want to bring our trainers in for a Story-Writing Workshop, where we’ll work with you to: Set powerful, objective-based boundariesWrite stories that are right-sized and ready to buildBuild a focused backlog that everyone can align around Discover how to kick off the new year with a backlog that’s ready to go.Whether you hold your own story-writing workshop or bring us in to help, remember that thinking inside the box is a powerful way to take teams 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/

The OKR Illusion, Why Structure Without Direction Is Just NoiseOKRs (Objectives and Key Results) have gained significant traction over the past decade, especially after being widely adopted and championed by companies like Google. Originally developed at Intel, OKRs are a simple yet powerful framework for setting and tracking goals. At their core, OKRs are about defining what you want to achieve (Objectives) and how you’ll measure progress (Key Results). While the concept is simple, the impact lies in how OKRs align teams, create focus, and connect everyday work to meaningful, measurable outcomes.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 Dr Martin Luther King JrUnderstanding Civil Rights Day and what we can do today to make a difference. 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 1500 - Special Edition With Bob HartmanJoin us for this once in a lifetime ONE HOUR edition of The Agile Daily Standup Podcast as we celebrate episode 1500 together! 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 in 2026 Looks Nothing Like ScrumThat delay cost us 42,000 failed checkout attempts and a week of executive explanations. Nothing was broken in the code. The failure was procedural. The fix was ready. The sprint boundary said no.That was the moment we stopped pretending Scrum was helping us ship.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/

AI Doesn’t Eliminate Agile Teams — It Increases the Need for Great Ones - Mike CohnEveryone today seems eager to talk about how AI is accelerating software development. Teams are shipping faster. Individuals are more productive. Entire backlogs can be written in minutes. Estimates are a click away. Code that once took days now materializes in minutes. With all this newfound speed, it’s understandable that teams and leaders start asking whether they still need the same kinds of collaboration—or even the same kinds of teams.Yet hidden underneath all that enthusiasm is a risk that hasn’t received enough attention. In fact, I would argue it is the risk that agile leaders should be paying the closest attention to.https://www.mountaingoatsoftware.com/blog/ai-doesnt-eliminate-agile-teams-it-increases-the-need-for-great-onesHow 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/

Scrum Is NOT Dead... It’s Obsolete?(Did someone actually Go here?) AAAAAAAhhhhhhhh!Stand-ups are still happening. Sprint planning still blocks calendars every few weeks. Retrospectives still end with “we should communicate better.” Jira boards are still very busy.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/

I made a VERY controversial Podcast Episode on January 1st and I think people may have completely missed it! There will be 3 CRAZY-BIG changes happening on the Agile Landscape in 2026:🚀 Prediction One: The Shift from Product Ownership to Product ManagementBroader Lifecycle Focus: Product managers will oversee the entire product lifecycle, from ideation to release.AI Integration: AI tools will streamline tasks, allowing product managers to focus on delivering value and happy customers.Expanded Roles: Expect more product manager roles and fewer traditional product owner positions.🛠️ Prediction Two: The Evolution of the Scrum Master into the Agile Project ManagerHolistic View: Agile Project Managers will support product managers and ensure teams focus on building the right product efficiently.Organizational Change Management: This will become a critical responsibility, guiding change within organizations.Certifications: Scrum Master certifications will still hold value but will need to adapt to this evolving role.💻 Prediction Three: Developers Will Spend Less Time Coding and More Time on Quality and IntegrationAI-Generated Code: AI tools like ChatGPT will generate code faster, requiring developers to focus on integration and quality assurance.New Roles: Developers will become integrators and quality managers, ensuring seamless code assembly and high-quality releases.🤖 Bonus Prediction: 2026 Will Be the Year AI Explodes in AgileAI Revolution: AI will revolutionize how we work, and those who leverage it will have a significant advantage.New Courses: We’re launching AI courses for Agile Project Managers, Product Managers, and Leaders to help you thrive in an AI-augmented environment.I’m genuinely excited about what 2026 holds for the agile community. These shifts, combined with the transformative power of AI, will redefine how we deliver value. If you’re curious to learn more, join my AI classes or attend agile leadership summits where we dive deep into these topics.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/

Growth Is Not Becoming Someone Else, It's About Becoming More Fully Who You Actually AreLena was the kind of person who could organize a project, a pantry, or a party with military precision—but she could not organize her courage.At work, she was reliable, steady, always the one staying late to fix last‑minute mistakes. Her boss trusted her, her teammates liked her, and her performance reviews were consistently stamped with the same phrase: “Solid team player.” It was meant as a compliment, but every time she saw it, a small, restless ache formed behind her ribs.Because tucked between her color‑coded spreadsheets and carefully labeled folders was a sketchbook she never showed anyone.Lena drew in the margins of meeting notes. She sketched on napkins at lunch. She had ideas for children’s books, a mental library of characters and worlds that lived only in her head and in the worn pages of that sketchbook. For years, she told herself a quiet story: One day, when things calm down, I’ll really give this a try.Things never calmed down.One Thursday, after a long meeting, she dropped her notebook on her desk and it fell open, pages spilling out. A coworker walking by noticed a drawing of a small, determined fox wearing a too‑big backpack.“Whoa,” he said, picking up the notebook. “You drew this?”Lena’s first instinct was to grab it back and laugh it off. “Oh, that? It’s nothing. Just doodles.”But he lingered on the drawing. “This is… actually really good. Have you ever thought about doing something with them?”The question made her heart race and her stomach sink at the same time. She had thought about it—a lot. She just hadn’t done anything. She shrugged, offered a vague “Maybe someday,” and changed the subject.That night, sitting on the edge of her bed, Lena heard a sentence in her mind that she couldn’t shake: How much longer are you going to call the things that matter to you ‘nothing’?It wasn’t a dramatic movie moment. There was no soundtrack, no lightning bolt of clarity. Just a quiet discomfort that felt different this time—not like shame, but like an invitation.She opened her sketchbook and flipped through the pages. There were dozens of characters: brave foxes, shy turtles, anxious owls, adventurous kids. She noticed something she’d never put into words before—almost every drawing was about someone who underestimated themselves and discovered they were capable of 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/

What Makes a Great Product Manager?When I first stepped into product management, I had no idea what I was signing up for. I thought it was about building cool features, running a few sprints, and celebrating launch days with cake and confetti. What I didn’t expect? The emotional rollercoaster of stakeholder battles, last-minute pivots, and the constant juggling between what’s ideal and what’s possible.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/