The Agile Daily Standup - AgileDad

The 3 Pillars of Scrum and Why Adaption Is So Very Powerful! What are the three pillars of Scrum? The Scrum framework uses three pillars of empiricism: Transparency, Inspection and Adaption. Transparency suggests that the details about the product development process are available, accessible, and present to all those involved in the process; including customers, Scrum team and the stakeholders. For example, any information radiators, such as the Sprint report, or Sprint burndown are shared and accessible. In a remote team environment, this could be a link shared in your video chat or pinned on a wiki page. Inspection is the process that evaluates the work done by the development team. Inspection involves the products being developed by the team, and the processes, people, and practices to help drive the continuous improvements of the product. The team collectively evaluates the “done” items by the team. It is recognized as part of the Sprint retrospective in the Scrum process. Adaption is the Scrum team’s ability to respond to change, when working together on the product they are building. This is part of the continuous improvement ethos. Adaption involves the team’s ability to respond to sudden changes by adapting to the feedback that stakeholders provide, typically in the Sprint review. It is then considered and included in the next Sprint. 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 podcast discusses the struggles faced during backlog refinement, including bugs, lack of communication, and disconnect between team and individual goals. It introduces strategies to address these issues and highlights the positive outcomes achieved. The team emphasizes knowledge sharing, building relationships, and creating T-shaped teams for better product delivery.

This podcast discusses the realities of depression and anxiety, highlighting the experiences of famous music artists who have faced mental health challenges. It emphasizes the importance of seeking help and provides resources for support.

This podcast explores the effectiveness of WSJF and objective stack ranking for task prioritization in Agile development. It discusses calculating Cost of Delay and Job Duration in WSJF, assigning priority grades based on impact and effort, and comparing the effectiveness of WSJF and objective stack ranking in creating an objective backlog.

Mike Cohn, an expert in teaching agile and Scrum methodologies, shares tips on teaching others about story points. He explains that story points are abstract units of measure used to estimate effort rather than time. The main benefit of story points is that they allow team members with different skill levels to communicate and agree on estimates. The podcast delves into the challenges of effort estimation and discusses the process of estimating story points in Agile development, considering factors like complexity and risk. Keeping the estimation method simple and aligned with previous experience is crucial.

Signs of a failed Agile transformation include reliance on consultants, excessive documentation, preconceived solutions, and rigid processes. Team autonomy and growth are important, while criticizing without providing opportunities for improvement is counterproductive. Coaches should understand change psychology and avoid dogmatism.

The podcast discusses signs that indicate a ScrumMaster's lack of understanding of Scrum, such as not having a clear Definition of Done, sticking to a standard process even if it's not effective, and neglecting facilitation and servant leadership. It emphasizes the importance of transparency, timely resolution of impediments, and learning during the sprint. Key aspects of Scrum are highlighted, including the need for addressing issues promptly, good facilitation skills, and a transparent Definition of Done.

The podcast discusses eight behaviors that result in a decrease in trust, such as 'Boundaryless Freedom' and 'avoiding confrontation.' They also highlight the negative impacts of being a know-it-all, playing the victim, and overpromising while underdelivering.

This podcast explores the role of a great ScrumMaster through various analogies, including the navigator of a road trip, the conductor of an orchestra, the facilitator of a discussion, the playground mediator, and the team cheerleader. It also discusses how a ScrumMaster can be likened to a traffic cop, a wedding planner, a gardener, a sports team coach, a theater director, and a chef in a kitchen.

The podcast discusses the purpose and structure of the daily scrum meeting in Agile, emphasizing the importance of setting goals, adjusting unplanned work, and providing progress updates. It highlights the benefits of daily scrums, such as improved communication and quick decision making. The chapter delves into the definition provided in the Scrum Guide 2020 and explores the dynamics of the daily scrum meeting.