Every January, I look again on the prior yr’s weblog posts and share the preferred. 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 atone for the ten hottest blogs I wrote based mostly on feedback and web page views.
The tenth-most standard weblog put up addressed the results when a staff calculates the associated fee per level of delivering performance. It’s fascinating as a result of the risks aren’t inherent. However there might be risks in how that price is used, particularly by these outdoors the staff.
Within the ninth-most standard weblog of final yr, I introduced 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 straightforward rule of thumb that may be utilized in all circumstances by all groups. However on this put up I present steering that ought to make it easier to reply the query to your staff.
Many groups make the error of considering that the aim of Scrum’s dash planning assembly is to estimate a whole lot of duties. Within the seventh-most standard put up from 2021, I write that the aim of dash planning is one thing else solely.
Final yr’s sixth-most standard put up is among the most vital posts of the yr, I feel. The put up 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 put up from 2021 covers one thing I’ve modified my thoughts about during the last 20 years: whether or not a staff ought to divvy up duties amongst staff members in the course of the dash planning assembly. This put up covers my present view and helped me reconcile why I’d modified my thoughts for the reason that 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 rely on one hand the situations when could-have objects find yourself included within the deliverable. So why hassle with that? A random dialog with a monetary planner launched me to what I feel are a greater set of phrases.
I discover it tiresome when individuals inform me this or that kind of venture can’t be agile. I think about agile a response to the constraints of a venture. A buyer who needs to lock down the value of a venture 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 put up from final yr. In it I provide recommendation within the type of seven questions that may make it easier to resolve if being a Scrum Grasp is best for you.
Lastly, in the preferred of my posts from 2021, I take with reference 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 an alternative.
What Have been Your Favorites?
What have 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 beneath.