andrewducker | Interesting Links for 03-06-2024

Entry tags:

Our entire org works that way pretty much. Oh there are POs at the client, but we just have teams, 3-4 "chapter" ambassadors, 2 what would be "C" level and then it's the head of our company within the group, with higher management being over all the groups.

You are not wrong though, it's a bit unclear chaotic (I find).

I assume the logic is that the CLIENT will do whatever management is necessary for the actual projects, our guy just manage us and our career progresseion.

But we are consultants. We are supposed to do the client facing stuff ourselves of course.

But with multiple projects per client, some teams manage better inter team comms and org than others. Like for one client at have a DX team, for others, not.

I actually like client facing stuff, but I'm not getting to do it so I'm waiting on a move. I'm much better at requirements and running a small team than with IaC!

Ah, gotcha.

Yeah, if you were going into one project per customer then you wouldn't need it, but if you're in multiple ones then it makes sense to have some communication between you.

Although if the customer has project managers then having two different channels between projects might get confusing (or highlight when people are being kept in the dark).

Flat | Top-Level Comments Only

Interesting Links for 03-06-2024

Re: 2.

Re: 2.

Re: 2.