Every January, I look again on the prior yr’s weblog posts and share the most well-liked. Final yr was a busy yr for me–I struggled to remain present with a few of my very own favourite blogs. If, like me, you fell behind in your studying, right here’s an opportunity to make amends for the ten hottest blogs I wrote based mostly on feedback and web page views.
The tenth-most standard weblog publish addressed the implications when a staff calculates the fee per level of delivering performance. It’s fascinating as a result of the hazards aren’t inherent. However there may be risks in how that value is used, particularly by these exterior the staff.
Within the ninth-most standard weblog of final yr, I offered three approaches groups can use to make sure they’ve time for refactoring. This publish additionally covers the professionals and cons of sustaining a separate refactoring backlog.
Re-estimating is among the matters I’m most regularly requested about. There’s not a simple rule of thumb that may be utilized in all circumstances by all groups. However on this publish I present steerage that ought to allow you to reply the query in your staff.
Many groups make the error of considering that the aim of Scrum’s dash planning assembly is to estimate quite a lot of duties. Within the seventh-most standard publish from 2021, I write that the objective of dash planning is one thing else completely.
Final yr’s sixth-most standard publish is among the most necessary posts of the yr, I believe. The publish describes three kinds of necessities:
- These we’re conscious of
- These we overlook
- These our customers can solely assist us uncover as soon as they begin seeing partial implementations of the product
The fifth-most standard publish from 2021 covers one thing I’ve modified my thoughts about during the last twenty years: whether or not a staff ought to divvy up duties amongst staff members through the dash planning assembly. This publish covers my present view and helped me reconcile why I’d modified my thoughts because the early days of agile.
I’ve by no means been a fan of separating necessities into must-have, should-have, could-have, and gained’t-have classes. Out of all of the instances I’ve seen that, I might most likely depend on one hand the situations when could-have objects find yourself included within the deliverable. So why trouble with that? A random dialog with a monetary planner launched me to what I believe are a greater set of phrases.
I discover it tiresome when individuals inform me this or that kind of undertaking can’t be agile. I take into account agile a response to the constraints of a undertaking. A buyer who desires to lock down the value of a undertaking offers a difficult constraint, however a staff can nonetheless be agile in that scenario.
I wasn’t shocked that this was the second-most standard publish from final yr. In it I provide recommendation within the type of seven questions that may allow you to determine if being a Scrum Grasp is best for you.
Lastly, in the most well-liked of my posts from 2021, I take with regards to dash objectives. They’re nice for some however not all groups. On this publish, I share the kind of groups that don’t profit from a dash objective and what they need to do as an alternative.
What Had been Your Favorites?
What had been your favourite posts from final yr? Did I miss something that ought to have been on this listing? Please share your ideas within the feedback under.