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.
In 2015 Cheryl Hammond introduced me to the GetKanban game. The game is an awesome way for the participants to experience the impact of queues and the decisions you need to make using the Kanban framework. The players simulate 2-3 weeks of development with daily standups where the team decides prioritization and who should work on what. Life is not fair and neither is the game. But we learn through our struggles and this is only a game.
We read blogs because we want to learn, expand our horizons and keep up with new developments in the Industry. We write blogs because we are passionate about a topic, want to share some cool ideas and very often to market ourselves. There is an overlap but readers and writers are not always in sync. There is so much to read and so little time. Over the last few months I have looked at about 250 somewhat random blogs. I stumbled upon some excellent articles but the majority was either talking to the absolute beginner audience or plain mediocre.
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.