• 5 Ways Product Owner Accountability Is Misunderstood
    Jun 20 2024
    1. The Product Owner is assigned to a team
    2. The Product Owner is responsible for the product delivery
    3. The Product Owner’s sole job is to do backlog management
    4. The Product Owner is no Product Manager
    5. The Product Owner owns the Sprint Backlog and determines what the team does

    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/

    Show more Show less
    9 mins
  • Celebrating Juneteenth
    Jun 19 2024

    Juneteenth marks a pivotal moment in American history, commemorating June 19, 1865, the day when Union soldiers, led by Major General Gordon Granger, landed at Galveston, Texas, with news that the Civil War had ended and the enslaved were now free. This announcement came a full two and a half years after President Lincoln's Emancipation Proclamation had officially outlawed slavery in Confederate territories. The delay in the enforcement of the Proclamation highlights the deep-seated resistance to ending slavery and the complexities involved in applying federal laws across a fractured nation.

    The first celebration of Juneteenth was one of both profound joy and cautious optimism. The newly freed African Americans of Galveston rejoiced in the streets, their celebrations a powerful act of communal catharsis. However, this newfound freedom was tempered by the uncertainty of how true emancipation would unfold in the years to come. Despite the challenges they faced, including segregation, economic disparity, and the long struggle for civil rights, Juneteenth has remained a symbol of resilience and hope. It is a day to reflect on the bitter history of slavery, to celebrate the strides toward equality, and to renew the commitment to fighting against systemic injustices. This holiday serves not only as a reminder of past pain but also as an inspiration to strive for a brighter, more inclusive future.

    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/

    Show more Show less
    4 mins
  • 3 Rules For Estimating Work Using Time.. (Are you Serious?)
    Jun 18 2024

    Are we really still having this conversation? I had a student point out an article that explains why everything ties back to time. Yet again we debunked and show how everything should NEVER point back to time. It is so much easier to estimate and forecast without it!!

    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/

    Show more Show less
    12 mins
  • How To PERFECTLY Price Your Products or Services
    Jun 17 2024

    Where is the BEST Price Point for your product or service?

    Too Expensive

    “At what price would you consider the product to be so expensive that you would not consider buying it?

    Too Cheap

    “At what price would you consider the product to be priced so low that you would feel the quality couldn’t be very good?”

    Expensive

    “At what price would you consider the product starting to get expensive, so that it is not out of the question, but you would have to give some thought to buying it?”

    Cheap (Bargain)

    “At what price would you consider the product to be a bargain — a great buy for the money?”

    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/


    Show more Show less
    10 mins
  • Why We Should Learn Everything The Way We Learned To Walk
    Jun 14 2024

    Why We Should Learn Everything The Way We Learned To Walk

    Watch home videos of babies standing and walking for the first time and two things in particular stand out:

    1) They fall over a lot. They are trying and failing constantly, which isn’t surprising considering how tricky standing up and walking can be. What is surprising is just how readily they get up again, without seeming to be at all disheartened by the experience of failing. In fact they often find it funny. They are not only unconcerned by their failures, they are entertained by them. How might we maintain this attitude to our learning later in life?

    2) Their efforts are celebrated and encouraged by everyone around them. If you are lucky enough to witness a baby taking their first steps, take a moment to take your eyes off the magic happening in front of you and look at the parents, grandparents, siblings and friends who are watching. I wonder if we ever really celebrate our children’s achievements with the same amount of genuine excitement, encouragement and love as we do when we watch them take their first steps. What if we could keep replicating that level of encouragement and joint celebration throughout their lives whenever they learn something new?

    Maybe babies have something to teach the rest of us. Maybe they realise more than we do the importance of taking your time, laughing at your failures and encouraging others with genuine love and excitement. Maybe, just maybe, if we learned to do everything the way we learned to walk, learning itself might not seem as painful as it sometimes seems at school. Maybe instead it would feel easy, like … well … like a walk in the park.


    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/

    Show more Show less
    8 mins
  • Are Scrum & Agile Dead? - Mike Cohn
    Jun 13 2024

    Are Scrum & Agile Dead? - Mike Cohn

    I’ve always said I wanted Scrum and agile to go away.
    Is that happening? I don’t think a week passes without some article about their deaths appearing in my browser or email.
    Within a few years of the Agile Manifesto being written, I began to say I wanted agile to go away. I didn’t mean I wanted us to stop using them. Rather, I want them to win.
    I want agile to become so much the accepted approach to product development, or to teamwork in general, that we could stop talking about it.
    Instead of saying “agile software development,” for example, I could just say “software development” and the assumption would be that, of course, that meant agile software development.
    To some extent, we’re there.
    Changes Accelerated by Agile
    When Scrum emerged as the original agile framework in the mid-1990s, cross-functional teams were not common. They are now.
    Software development back then was done in phases—typically an analysis phase followed by design, coding, and testing phases.
    Heavy duty, pixel-perfect prototypes were common back then due to the high cost of iterating over a design. While prototypes are still used today, multiple quick prototypes are now common to help product owners and managers choose between options.
    Before the advent of agile, organizations thought they could add quality to a product by testing quality in at the end. Agile has helped us see that isn’t true.
    Barry Boehm’s spiral model (1986) and Tom Gilb’s evolutionary delivery (1988) had started a shift to iterative, incremental development. But that shift accelerated dramatically after the Manifesto in 2001.
    (Did you know I named Mountain Goat Software after a sentence in Tom Gilb’s book?)
    What I Hear about Agile Today
    Recent articles and podcasts saying agile is dead are not saying we need to reverse the improvements agile initiated or accelerated.
    I haven’t read anything advocating a return to waterfall development or, more accurately, the ad hoc development practices that were more common before agile.
    Instead, the “agile is dead” articles more closely mimic my long-held view that we can eventually stop talking about agile teams, agile development, agile frameworks and more. They’ll just become teams, development, and frameworks.
    So are agile and Scrum dead?
    I don’t think so.
    I think there’s still plenty of work ahead. It’s why we’re focusing more attention toward whole-team training.
    Some of the agile and Scrum fatigue I sense today is analogous to what happens in the music industry. Fans who love an artist’s first few albums often sour on that artist when they’re discovered by the masses. The artist is no longer the hip, new thing and many early fans move on because of that.
    I will be happy when agile wins, when we can drop it as an adjective in front of so many terms. Until then I will remain dedicated to helping teams succeed with agile,

    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/

    Show more Show less
    7 mins
  • How To Fix The Top 3 Most Common Scrum Issues
    Jun 12 2024

    How To Fix The Top 3 Most Common Scrum Issues

    1. Avoid starting projects with a Sprint Zero

    Sprint Zero often doesn’t provide enough time for thorough planning and architectural decisions. Instead, advocate for a flexible approach. Ensure initial planning and setup extend beyond a single sprint. This way, your team can establish a solid foundation for future development without feeling rushed.

    2. Ensure thorough planning and clear acceptance criteria

    Starting sprints without clear acceptance criteria can lead to scope creep and missed deadlines. Before beginning any sprint, ensure a detailed agreement between developers and management. This should outline exactly what needs to be built, including all edge cases and validation rules. Clear criteria help keep the team focused and on track.

    3. Avoid treating story points as hours

    Converting story points into hours undermines the agile methodology by bringing back the rigidity of waterfall projects. Educate your team and management on the correct use of story points to represent relative effort and complexity, not time. This maintains the flexibility and effectiveness of the scrum process, allowing for better adaptation to changes and challenges.

    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/


    Show more Show less
    5 mins
  • The Top 5 Ways You Can Demonstrate Collaboration With Cross-Functional Teams In An Interview
    Jun 11 2024

    The Top 5 Ways You Can Demonstrate Collaboration With Cross-Functional Teams In An Interview

    1. Share Stories
    2. Highlight Empathy
    3. Discuss Outcomes
    4. Use Metrics
    5. Reflect Flexibility

    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/

    Show more Show less
    5 mins