Agile Teams with continuous changing team members of operations

I want to transform the current ITIL based team structure (with Plan, Build and Run focus) to an agile team organization.

Why? What problem is being faced, and why do you think an agile team organization might help solve it?

One key challenge is to make continuous shifts between Operation team and different build teams possible. 

What about the challenge of creating a cross-functional team that delivers release quality work?

Is such an organization possible at all? What could such an organization look like and how can such a change be organized? 

in facts: 50 employees
OP team has 25 employees. All other should be in 4 agile teams

Before you consider multiple teams, can you implement the Scrum framework successfully with just one?

Hi Ian



Why to change to an agile organisation ?

I think I can reduce it to following points: crossfunkctional working; flexible to marketplace; Time2Market; transparency to project stati; Minimal Viable Product; broader knowledge transfer; 

What about the challenge of creating a cross-functional team that delivers release quality work?

All necessary functions are in the team. Cossfunctional is available; 

Before you consider multiple teams, can you implement the Scrum framework successfully with just one?

You mean, Scrum with 50 employees ? I thought, the teams should have the size between 5 and 9. How should a daily standup with 50 employees function ?

My big question is, how can I meaningfully involve the operation team. My vision is, that Operation employees work also as a team member to buid projects acquire know how. And vica versa.