47 minutes ago · Tech · hide · 0 comments

I have a lot of conversations about the fine details of software process, because the software that I work on, is a lot like Pivotal Tracker in some ways and very different in others, and we're very deliberate about those differences. For instance: Points. We don't have them. We do all our velocity calculations and predictions with raw story counting. If we're going to add them, I want to be able to articulate very clearly why. So I talking with people a lot about why we haven't added them yet, and about what the point of pointing us.Should we point? Why do we point? What does a point mean? Should we use Fibonacci or a powers of two or a linear scale or t-shirt sizes? Should we top out at 3 or 5 or 8 or 30 or 100? (If you top out at anything above 8 you are wrong.) Is pointing about the points or is it "about the conversation?" Are points really risk & complexity, or are they actually just time?And on and on and on and on.This kind of conversation is fun but I increasingly think that…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.