Early in 2019, I participated in an excellent game facilitated by Bonsy Yelsangi which provided us a lot of insight into estimation and story writing. I have facilitated the game several times with very positive feedback. The game can be played in less than an hour.Continue reading “Fruit Estimation Game”
Our team decided against estimating stories or tasks in real time (eg hours) during sprint planning. We assign relative points during backlog grooming and may change that number later or during the sprint planning as more information becomes available. I was wondering: How good are our estimates? How do we measure that? How do we improve? Do we care?
Using story points for estimation can get stale after a while. When Kyle Winter mentioned relative mass estimation on our company agile slack channel I was wondering how to implement this with a distributed team. Below are the details and results of our experiment.
How do you estimate a project before it has really started. You have a great idea and want to present it to your CEO. The second question will be how much is this going to cost? You have spent a couple of hours with the customer and they want to know: “Can you do this by the hard deadline we have?” Comparative (story point) estimating works well if you have broken the work down into stories. It is more difficult if the epics are very big and there are a lot of unknowns.