Ryan Ripley awam
[search 0]
lebih
Download the App!
show episodes
 
Loading …
show series
 
Todd discusses how to monitor work item age using Kanban. Discover how to define work's start and end points and how work item age is calculated. Learn about the tracking tools and how to monitor it using a traditional card-based board manually. For more details, check out our other videos on work item age. ⏩ Join Ryan and Todd for a Scrum.org cour…
  continue reading
 
A listener asks about the International Scrum Institute and its legitimacy. We've never heard of it, so we direct listeners to other ways to get trained and certified. ⏩ 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 Pr…
  continue reading
 
A listener asks about the challenges faced by an infrastructure team working in Kanban, juggling two different tracking systems. This video delves into the complications of handling disjointed work and suggests streamlining processes using tools like Zapier and Python. ⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhuman…
  continue reading
 
Can an inexperienced development team without any senior members can implement scrum? While there's a debate on the necessity of technical excellence for scrum's foundation, one suggestion is to define a clear DOD (definition of done) to unify the team. By revisiting and evolving this definition, teams can incrementally improve and move towards bet…
  continue reading
 
In this episode, Todd and Ryan discuss what to do if you’re a Scrum Master whose team is performing so well you’re afraid of losing your job. Todd emphasizes analyzing your team under a broader sphere to see where gaps between your team and other teams may be. In addition, Ryan also emphasizes the importance of analyzing your team according to data…
  continue reading
 
In this episode, Todd and Ryan discuss the do’s and don’ts of new product owners. Todd emphasizes the need to be decisive to ensure your people know who decides the order, and what your expectations are as the product owner. However, Todd also emphasizes the importance of being humble, and having a strong team of developers behind you. ⏩ Join Ryan …
  continue reading
 
When dealing with working agreements gone wrong with a developer, we always hope that it’s a misunderstanding that can be solved with an easy conversation. In the cases where it’s not, we believe this is when a Scrum Master needs friends. Scrum Masters should always be willing to work with other areas of management such as leadership, financial, hu…
  continue reading
 
A YouTube viewer sent in a question asking about the typical day in the life of a Scrum Master. Todd and Ryan talk about what their days look like when they are in the Scrum Master role and how each day usually looks a little different. Check out the video to learn about the things you'll see as a Professional Scrum Master. Want to learn more about…
  continue reading
 
Richie Peters has experience as a Scrum Master with a background in engineering management and has worked in various software companies. Richie and Ryan discuss how Scrum implementations in organizations are challenging due to a lack of understanding and education about Agile principles among senior leadership. Executives often try to impose Scrum …
  continue reading
 
In their conversation, Todd and Ryan discussed some self-study resources for Flow Metrics and Evidence-Based Management (EBM). They suggested starting with their YouTube channel's EBM series and reading Dan Vacanti's book "When Will It Be Done" for a comprehensive dive into Flow Metrics. ProKanban.org was recommended for further information on Flow…
  continue reading
 
Todd and Thomas introduce The Modern Software Developer Series and examine the Battle Ship codebase. Grab the repo, follow along, and learn new modern software developer techniques. Battleship Case Studies can be found here: https://github.com/proscrumdev ⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc Todd and …
  continue reading
 
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 …
  continue reading
 
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…
  continue reading
 
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…
  continue reading
 
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…
  continue reading
 
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…
  continue reading
 
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…
  continue reading
 
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…
  continue reading
 
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 …
  continue reading
 
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…
  continue reading
 
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 …
  continue reading
 
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…
  continue reading
 
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…
  continue reading
 
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…
  continue reading
 
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…
  continue reading
 
Loading …

Panduan Rujukan Pantas

Podcast Teratas