A lot of people have free time towards the end of the year. This year some of us are neither traveling nor able to do other outside activities. Below is an eclectic list of some of my favorite blogs and videos you may find interesting. Some are old so you may have missed them. They are still relevant today.Continue reading “An eclectic list of some of my favorite blogs and videos”
Velocity is an excellent planning tool for longer projects and stable teams that are not very small. It allows you to ignore details like vacation and bad estimates. The law of averages smooths out the bumps allowing you to make a reasonable directional estimate of what can be achieved by a given date.
For smaller teams on short projects of four to six sprints the vanilla velocity does not work as well. If a developer goes on a two week vacation both the sprint capacity and release projection can be significantly off. In a recent case we needed a larger team to complete the project but the fifth member was not available until the third sprint. You can manually adjust for these situations but I prefer to automate when it saves time.Continue reading “Template for Automated Release Burn up”
Would you like to get a feel for what the team thinks of many aspects of the team processes in less than 15 minutes? What does the team really think of your work? Continue reading “Comprehensive Team Health Check”
Many teams follow the three questions for their stand-ups: “yesterday I did …; today I will do …; I am blocked by …”. Time and again I see the same anti-patterns: It is not a planning meeting but a status report to the PO or PM. The team is not listening to other team members. Continue reading “Is your stand up working for you?”
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.