We can learn so much about how people feel about something like teamwork just by asking questions. That’s especially true when we ask kids.I was traveling last month and ended up in line next to a father and his eight-year-old son. I made small talk with the Dad to pass time in line and learned that the son had just traveled with his team to take part in a hockey tournament.Because I was curious (and a little because it seemed polite), I asked the boy, “So how’d you do?” He said, “Not well. We got eliminated in the first round.”I replied, “Right. But how did you do?”His reply to that question was strikingly different. He told me all about the goals he’d scored and the assists he had made.I learned a few things from this offhand exchange.  His first response was about his team, which means he’s going to be a great agile team member someday. No matter how great we do individually, it’s hard to feel excited when the team doesn’t perform at its best. And it got me thinking, what would happen if someone asked one of your team members, “How’d you do last sprint?” Would they automatically reflect on the team’s performance or default to their own?It might be worthwhile to pose that question to your team. Questions are my favorite way to get team members thinking, because once they’re thinking they automatically start looking for ways to improve a situation or solve a problem.Ask more questions. I know for sure it will help you 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/⁠

Mike Cohn, a leading figure in Agile methodologies, joins Brian Milner to unpack the secrets to Agile success. They emphasize the importance of embracing experimentation and flexible coaching. The duo highlights how effective communication, with a consistent vocabulary, can prevent misunderstandings within teams. They stress tailoring Agile practices to fit unique contexts instead of rigid frameworks. Personal anecdotes and practical tips fill the conversation, providing valuable insights for anyone looking to thrive in Agile environments.

Explore the top 4 reasons behind team resistance to change including lack of awareness, fear of the unknown, job security concerns, and lack of executive advocacy. Learn how transparency, communication, and leadership support can help overcome resistance to change in organizations.

The podcast discusses the evolution of release plans in Agile teams, emphasizing the importance of accurately predicting future deliveries. It explores how plans can be accurate without being overly precise and the balance between accuracy and precision in long-term planning.

Discover the optional nature of user stories and story points in Scrum. Learn how story points can enhance estimation by avoiding debates and improving accuracy. Explore the benefits of utilizing story points for agile development and the flexibility of using a Fibonacci scale.

Agile and Scrum expert Mike Cohn discusses the importance of managing sprint backlog item sizes, using the analogy of elevators to explain the pitfalls of overloading sprints with large tasks. He emphasizes the need for teams to focus on smaller, manageable items for efficient workflow, cautioning against bringing in oversized tasks that can lead to work backlogs.

Exploring re-estimating split stories in Agile, Mike Cohn explains the necessity of adjusting estimates when breaking down stories. Analogies like airplane landings highlight the unpredictability in estimations. Balancing accuracy and precision in estimation is crucial for success in Agile methodologies.

Mike Cohn, an expert in Scrum and Agile practices, discusses the confusion between the roles of Scrum Masters and managers. He emphasizes the importance of defining these roles clearly for effective Agile practices and explores the balance between offering assistance and empowering individuals in leadership and management.

Agile expert Mike Cohn revisits 200 user stories, discussing the importance of meaningful conversations over perfection. They explore the clarity of user stories, the balance between what and how in requirements, and the implications of wording choices. The discussion emphasizes leaving stories open-ended, creating user stories for detailed pages, task prioritization, and analyzing the structure of user stories for effective software development.

Mike Cohn, Agile expert and author, discusses the relationship between user stories and requirements. User stories act as placeholders for future conversations with stakeholders to convey detailed needs. Each story serves as a pointer to a requirement, guiding the team towards necessary discussions for project success.