lukadotnet,
@lukadotnet@mstdn.social avatar

Ever wondered when/how to effectively move a task/responsibility outside the team? To a Global/shared Function, a Subject Matter Expert, an external contractor, an Agency, a Team Topologies’ Platform team or a Complicated subsystem team.

Here are some thoughts => https://www.smharter.com/blog/2024/01/01/when-how-to-move-effectively-tasks-responsibilities-outside-the-team/

What is your experience? When did it work well for you? When it did not?

lukadotnet,
@lukadotnet@mstdn.social avatar

Do you have a UX team? A DevOps team? A Platform team? A last-mile UAT team? A Release team? A Support team? Do they work as a boost or a bottleneck for you?

This is an exploration of when/how they are beneficial

AAMfP,
@AAMfP@fosstodon.org avatar

@lukadotnet
We have a wonderful 🙄 platform team that requires us to open a ticket even to create a repository... 🤷🏻‍♂️
It's not a bottleneck, it's a bottle with a stopper! 🤦🏻‍♂️

lukadotnet,
@lukadotnet@mstdn.social avatar

@AAMfP do you know what makes your platform team so inefficient? what was the original intent when it was formed?

Do you find your experience congruent with the reasoning and guidelines emerging from this post ? => https://www.smharter.com/blog/2024/01/01/when-how-to-move-effectively-tasks-responsibilities-outside-the-team/

AAMfP, (edited )
@AAMfP@fosstodon.org avatar

@lukadotnet
Well, yes. It fits.
Actually they've been formed pretty recently (few months) with the idea to better organize and standardize the platform side of the teams.
Offloading this part should help teams focus on the product itself, also having a reference point for platform usage standards and rules.
They are still forming, in the middle of an important reorganization, so there are delays and issue, but I'd give them time to improve.

lukadotnet,
@lukadotnet@mstdn.social avatar

@AAMfP
> but I'd give them time to
> improve.

I find it hard to get a platform team right and I don't see it as an end-state (new things may be moved to the platform team and things they already take care of may face sudden fast evolutions that require them to be moved back to a team for a while, etc)

So instead of the "it will get worse before it gets better" for a platform team I would look for “First, make the change easy, then make the easy change” so that it never hurts or gets worse

AAMfP,
@AAMfP@fosstodon.org avatar

@lukadotnet
True, but they really are in a mess, with missing people and knowledge due to layoffs of other consultancy company.
It's hard for them to manage even the normal activities, actually.
I'm not (yet) blaming them.

lukadotnet,
@lukadotnet@mstdn.social avatar

@AAMfP
good idea.

would help if in the meanwhile the ownership and responsibilities are shared between the platform team and the client teams?
So that client teams will have the autonomy to go ahead without being blocked by the platform team and the platform team will have the time and capacity to set things up?

AAMfP,
@AAMfP@fosstodon.org avatar

@lukadotnet
Indeed! We're actually working in that: unfortunately I'm the Scrum Master of the main client team of Platform... hard job. 🙄

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • khanakhh
  • DreamBathrooms
  • ethstaker
  • magazineikmin
  • osvaldo12
  • Durango
  • Youngstown
  • ngwrru68w68
  • slotface
  • rosin
  • mdbf
  • kavyap
  • InstantRegret
  • tester
  • JUstTest
  • thenastyranch
  • cisconetworking
  • tacticalgear
  • cubers
  • everett
  • modclub
  • GTA5RPClips
  • anitta
  • Leos
  • provamag3
  • normalnudes
  • megavids
  • lostlight
  • All magazines