…are six or seven points go into the eight-point bucket, since a six-point item would overflow a five-point bucket. This creates a slight pessimistic bias—items are rounded up instead of to the nearest value. This helps counter the tendency many teams have to under-estimate. And it means the team is…

…with actually owning our story in a way that doesn't feel gross. Brian Milner (06:39) Yeah, I think you make a great point there about the partnership aspect of it because having been on both sides of the table there, I know when I was hiring people as a software…

…got a couple of points to make on this. But for the first time ever in human history, we now have something that might be more intelligent than us. And that is scary because there's some AI neural network engines that people can't explain how it's working anymore. They put…

…theory behind estimating with story points, if you don’t account for human nature and personality dynamics, you can still encounter problems. I’m not saying your team members are problem people; I’m sure they’re awesome. It’s just that people bring baggage and preconceived notions to the estimation process. How People Problems…

…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…

…it. There's a wonderful story about this in… Founders at work a book by Jessica Livingston and she talks about this kind of group of super smart people in late 90s who Came up with a very very efficient Cryptography algorithm and a way to compute the cryptography so they…

…one of the friction points here in shared services is you've got these demands coming at you. all day, every day from all these different corners and from everyone, it's urgent. From everyone, this is the most important thing. So how can you apply some of this product ownership mindset…

…working on a user story, “As a user, I am logged out after n minutes of inactivity.” Before that story can be considered complete, someone is going to need to decide how long n is—30 minutes? 12 hours? But, someone could absolutely begin work on that story without the answer.…

…work. I know my story. I've got all the requirements. I sit down at the IDE, and I start to think about how am I going to write a test. I don't know where to start. I know what I need to do. It's not that. It's picking a place…

…a gross estimating approach (story points). A pull-based system sounds nice, but it doesn’t sound like it’s going to give me a better sense of what we can accomplish in a sprint. Your velocity is somewhat stabilizing, but you’re still committing to more work in Sprint Planning than you can…

…average velocity of 25 points per iteration over the last year and they have time for 8 iterations in this new project; therefore they will complete around 200 points in those 8 iterations.” But what do we do when we are managing an agile project where team membership or size…

…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…

…we already know that story. whole reason, for those listening, consider this, whole reason Agile took off was the option A wasn't working and very clearly wasn't working for complex projects like software. Now for this person to come and recommend XYZ, of course, not surprising for all the listeners…

…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). How to Account for Time Off & Holidays in Long-Term Plans But how should a team estimate its future velocity when team…

…team might split the story in order to create small enough pieces to fit inside one sprint. A team that does agile estimating with story points will also add estimates to any new or split stories that are bubbling up in priority. Why Refine the Product Backlog? By asking questions…