I don't think it's about quality or productivity, I think it's about predictability. Most teams have an estimation process where features are sized so that they

I don't think it's about quality or productivity, I think it's about predictability. Most teams have an estimation process where features are sized so that they can arrive at a product plan. Most teams also don't have a good way to loop back and see whether their sizing was correct or not. I've seen a number of teams that have a field in Jira for the number of hours/days spent on an issue. It's mostly filled out by developers guestimating based on their unreliable memory how long they spent working on it and they frequently forgot to fill it in at all. This product seems targeted at that. It's automatic feedback on sizing/estimates and it's how teams get more accurate in their future assessments and how businesses get more predictable product plans that they can rely on to make business decisions. Productivity of a development team is almost a secondary concern to predictability. Delivering on-time, whenever that time is predicted to be, might be more important than delivering quickly since the business doesn't have to wait until product is done to start selling, promoting, partnering, etc.