Following up on team health

[nizar]

@antoviaque

Good question – there is actually a follow-up ticket @nizar has planned to follow-up and check on these points. @nizar would you like to give some details about what you have in mind about this?

I planned to create a follow-up ticket to ensure the impact of the sprint planning changes have been positive on members. In addition, another ticket was created to ensure members, in the meantime, have roles they actually want and means to swap/transfer those roles to others in a more facilitated manner.

I don’t have much to share regarding the sprint planning changes yet, I still need to collect some statistics. But for the second ticket, @joidegn has already created an announcement on the forum, Wanted/Unwanted Metawork - Exchange roles.

I have more plans of further exploring roles and reducing the meta work done by Sprint Planning Managers and Sprint Managers, because they’re the next two huge roles that are being avoided at the moment (after Epic & Sustainability Managers and Recruitment Managers).

However, I need to transition into my role first, to be able to better focus on things first. In the meantime, a portion of my time is going towards coordinating between members in the cell to find backups/reviewers/replacements, which makes it a little harder to focus on other things.

There’s still not enough clarity though on whether that transition can be done now, or not yet. I’m hoping to discuss that in detail with a couple of members in the upcoming week. I’ll then have a better idea what to do.

@antoviaque

That said, a large part of @nizar 's new role is to keep an eye on this too, and help facilitate those discussions & bringing up discussions points. That’s also something on which it might be worth explaining some of the ways you have in mind to approach this @nizar ?

There are a lot of things to target in order to ensure cells are doing well.

But I don’t want the new roles to do that work, because it would kind of contradict with OpenCraft’s philosophy. I still want self management to be practiced, and I want decisions to be taken by members. So my approach, for now, will be to help members recover from the issues they are facing, according to the bi-weekly checkup.

This assistance won’t be provided as some sort of HR, but it would be provided by refining our documentation/processes so it is more developer-friendly. And if necessary, assisting the developers in “debugging their issues” and following that documentation.

That refinement won’t necessarily be done by me, but whenever it cannot be done by others, it will fall on my plate instead of being blocked until someone else has time for it.

I’ll provide a better idea of that soon, hopefully. My approach won’t be set in stone, of course. It’ll be adjusted as I gain more experience in the role I’m in.