Ryan Ripley Podcasty

Todd and Ryan address a question about handling unplanned work that is not measured in Sprint planning and affects a team's predictability in meeting Sprint goals. They recommend holding back capacity back in Sprint planning to account for the unplanned work and plan realistically rather than at 100% capacity. They suggest cutting capacity in half …

The video discusses who should facilitate a Sprint review in a Scrum team. Todd and Ryan believe the Product Owner should be involved in the process to ensure the right stakeholders are present to adapt the product backlog. However, the Product Owner doesn't necessarily have to be the one facilitating the Sprint Review but should be responsible for…

The video discusses methods for identifying waste and workflow bottlenecks, particularly in lean principles. Ryan and Todd suggest using flow metrics to identify trends, running activities with teams to identify specific issues, and validating that input through visualizations. Balancing efficiency with effectiveness and keeping the customer in min…

The video discusses how someone who took a break from being a Scrum Master to run a food delivery business can get back into the role. Ryan and Todd suggest not to expect to start as a Scrum Master immediately and to consider other paths that may lead back to the role. They also advise preparing a narrative to explain the gap in the resume and upgr…

Andy asks whether all planned work by developers for a product must come from the product backlog. The answer is yes, assuming all developers work on the same product. However, problems arise when teams work on multiple things simultaneously. The product backlog items populate a Sprint backlog, which is then executed, leading to an increment. ⏩ Joi…

We believe that organizations make mistakes by having agile coaches and scrum masters. The scrum master should be the agile coach of the organization, and creating separate hierarchies diminishes the role of the scrum master. We also believe that some organizations claim to use agile but have not actually changed anything. They suggest using eviden…

Todd and Ryan discuss what components should be included in a year-end report or metrics for a Scrum team. They suggest using the Evidence-Based Management (EBM) framework and focusing on key value areas such as time to market, ability to innovate, current value, and unrealized value. They also discuss how the responsibility for creating such repor…

Todd and Ryan discuss how to make Scrum training effective long-term, even after the training. Training can be like injecting steroids into a team, which can wear off over time. They discuss ways they have tried to address this issue, including following up with newsletters and maintaining relationships with students beyond the training. They also …

Todd and Ryan discuss using Scrum with data science teams in this video. They acknowledge that data teams may not always have a tangible or usable product by the end of a Sprint. However, they suggest that focusing on essential slices of work and including visual components can make the process more effective. They emphasized the importance of find…

FIXING YOUR AGILE METRICS - INTRODUCTION TO TIME TO MARKET - CYCLE TIME ⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems. 👉 Buy Fixing Your Scrum at Amazon: https://amzn.to/3BMvkcX ✅Subscribe to our Channel to …

The video discusses whether shorter sprints can help a scrum team learn faster. Ryan and Todd explain that sprint length is a planning horizon and there is no right or wrong sprint length. The length of the sprint should be decided by the team and organization, based on factors such as how long they can go without feedback from customers and the st…

The video discusses essential questions for Scrum Masters to consider when starting with Evidence-Based Management (EBM). EBM involves goals, evidence, and empiricism. The first step is to ensure precise and transparent goals and assess their alignment. Next, measuring the right things, such as unrealized value, current value, time to market, and a…

The video discusses dealing with a team with a "we finish when we finish" mentality and consistently carries over work items from one sprint to the next. Todd and Ryan suggest looking at the aging of work items and discussing this in the daily scrum to help identify if the team is carrying over work that is not being done or if it's an ongoing prob…

Todd and Ryan believe that the potential of new tools, such as ChatGPT apps, to replace the role of a scrum master in facilitating and guiding teams is limited. Ryan, who has been working with ChatGPT, believes that while the AI-powered tool is impressive, it is not yet advanced enough to fully take over the role of a human scrum master. He also th…

The video is about strategies for helping executives with trouble articulating their goals. Todd and Ryan suggest asking executives open-ended questions about what is possible and what they expect to see once specific work is completed. It's important to tread lightly and warmly into the conversation and ensure that it empowers the executive. The a…

The video concerns right-sizing work in Scrum without historical data or cycle time. Todd and Ryan suggest that, in the absence of data, one should aim to complete product backlog items within half the sprint or less and focus on having small, well-refined stories that are tightly defined and understood. Ryan also notes that data can be unreliable …

The video discusses the use of Scrum in regulated environments and how it can be helpful in complex product development. While specific industry regulations may need to be considered, the framework of Scrum can still be applied to uncover better ways of doing things. Todd and Ryan give an example of how they identified and eliminated a labor-intens…

In this video, Ryan and Todd discuss how to deal with the culture of busyness in organizations. They talk about the concept of context switching, where people are assigned multiple tasks, but can't do any of them well due to being too busy. They suggest making the busyness transparent and measuring its impact to show that it is not only disruptive …

The video discusses how to write a good Sprint goal in Scrum. Ryan and Todd suggest avoiding the use of "and," "or," commas, and ticket numbers in Sprint goals. They also address whether it's fine to have Product Backlog Items (PBIs) that are not directly related to the Sprint goal, and conclude that it is acceptable as long as the work tied to the…

In this video, Ryan and Todd discuss the importance of having a clear Sprint goal in Scrum teams. While it is common for teams not to have a Sprint goal, lacking a goal suggests a lack of alignment on higher-level goals, such as a product or a strategic goal. The speaker suggests defining a product goal and creating a clear, concise, concrete step …

FIXING YOUR AGILE METRICS - INTRODUCTION TO TIME TO MARKET - THROUGHPUT ⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems. 👉 Buy Fixing Your Scrum at Amazon: https://amzn.to/3BMvkcX ✅Subscribe to our Channel to …

Ryan and Todd discuss whether it is acceptable for Scrum teams to work overtime to reach a Sprint goal. They believe working overtime can be okay if the Scrum Team misses something significant during Sprint Planning. However, it should not become a regular occurrence, as studies have shown that overtime can negatively impact quality and morale. The…