…between 100 and 120 story points.” Such statements are based on a team knowing its velocity (perhaps as a single, averaged value but even better as a range). But how should a team estimate its future velocity when team members are taking time off, whether personally or because of a…

You’re probably aware that story points are meant to reflect the total effort to implement a user story or any product backlog item. I’m often asked whether a team can determine the total number of story points for an item by summing the number of points needed to program it,…

…by however many percentage points. And my bonus is tied to that. The more I can increase it, the more I get a bonus. Well, it's kind of like if you go to a team and tell them, hey, can you do more story points? They can certainly game that…

…whatever unit the team prefers—story points, ideal days, team days and so on. On the burndown chart pictured above, the team started a project that was planned to be six sprints. They began with 360 story points of work. To finish within six sprints, they planned to average 60 points…

…discuss the common pain points and conflicts that can disrupt professional relationships and share effective strategies for creating a more cohesive and supportive coaching environment. Listeners will gain valuable insights into recognizing and leveraging personal and collective strengths and weaknesses, ensuring that Agile coaches not only preach transformative practices but…

…teams plan. Learn why story points have become the most popular unit for estimating work on agile teams. Explore how the popular Planning Poker technique, paired with story points, helps eliminate common estimating problems. Gain insights into predicting project completion using velocity and confidence intervals, including how to plan a…

…progress of 40 hours, points (or whatever) last sprint, but the burndown chart only shows net progress of 10. Was the team slower than expected, or was more work added to the release? It's important to know the answer to this question, because we cannot really predict when the release…

…with and management can rely on for decision-making. Explore story points, ideal days, and how to estimate with Planning Poker. Leave with new insight into both short–term iteration and long–term release planning.

…apply user stories and story points from the very start of a project up through delivery. Take a look at these highly interactive sessions from agile expert and trainer Mike Cohn. Designed to walk you through an agile project from funding through planning the first iteration, these presentations help put…

…of the big friction points between the business side and the developer side is take SQLMesh. If that's something that my team has never worked with and I have someone on the team who is interested in that and wants to, thinks it might give us some benefits, There's friction…

…abstract approaches such as story points and what a point really means. With an initial plan created, we'll look at how agile teams use the concept of velocity to measure and predict progress. We'll also look at information radiators such as task boards and burndown charts. We'll conclude by looking…

…will complete approximately 240 story points of work.” At the end of each iteration, an agile team assesses its position. However, there are many forces at work, and we need to consider each. First, and ideally most significant, is the amount of progress made by the team. Second is that…

…track sprint progress by story points, days, teams, etc. This section provides a great visual example, as well as an example of an alternative version. The sprint backlog is simply a list of tasks to complete during a sprint, though the tasks do revolve around product backlog items. You have…

__Agile Estimating and Planning__ is the definitive, practical guide to estimating and planning agile projects. In the book, ScrumMaster and CST Mike Cohn discusses the philosophy of agile estimating and planning and shows you exactly how to get the job done with real-world examples and case studies.

…world. [19:05] - Brian points out the pace that AI technology is improving, underscoring its impact on setting new standards of improvement industry-wide. [22:36] - Hunter shares his approach to integrating AI tools in his coding and testing processes, highlighting when they're beneficial and when they're not. [28:46] - Brian…