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 in style weblog put up addressed the results when a crew calculates the associated fee per level of delivering performance. It’s fascinating as a result of the risks aren’t inherent. However there may be risks in how that price is used, particularly by these outdoors the crew.
Within the ninth-most in style weblog of final yr, I offered three approaches groups can use to make sure they’ve time for refactoring. This put up additionally covers the professionals and cons of sustaining a separate refactoring backlog.
Re-estimating is among the matters I’m most steadily requested about. There’s not a simple rule of thumb that may be utilized in all instances by all groups. However on this put up I present steering that ought to show you how to reply the query in your crew.
Many groups make the error of pondering that the aim of Scrum’s dash planning assembly is to estimate quite a lot of duties. Within the seventh-most in style put up from 2021, I write that the aim of dash planning is one thing else completely.
Final yr’s sixth-most in style put up is among the most essential posts of the yr, I believe. The put up describes three forms 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 in style put up from 2021 covers one thing I’ve modified my thoughts about during the last twenty years: whether or not a crew ought to divvy up duties amongst crew members throughout the dash planning assembly. This put up 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 occasions I’ve seen that, I might in all probability depend on one hand the situations when could-have gadgets find yourself included within the deliverable. So why hassle 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 folks inform me this or that sort of challenge can’t be agile. I think about agile a response to the constraints of a challenge. A buyer who needs to lock down the worth of a challenge provides a difficult constraint, however a crew can nonetheless be agile in that scenario.
I wasn’t shocked that this was the second-most in style put up from final yr. In it I provide recommendation within the type of seven questions that can show you how to resolve 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 put up, I share the kind of groups that don’t profit from a dash aim and what they need to do as a substitute.
What Have 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.