New Scrum Team in a new company which is adopting scrum
Hi together I have switched to another company, and here is a new Team which is completly new to Scrum. And we are a crossfunctional Team, in which I did not work until now. I have only worked in a Scrum Team with developers, PO and SM.
So what will be the difference? And there was also a pretty interesting question from our management:
our company's management has asked itself how far the cft team is empowered to work independently. in the company, there were always strict controls and processes and now that they want to switch to scrum, they are afraid that the controls will fall away. So how far does the scrum team have the power to work independently without someone constantly interfering. And can't that also go in the wrong direction or is that what the reviews are for?
So what will be the difference?
None, unless there is a clear demand for that cross functional team to actually work in a cross functional way and thereby provide different outcomes. Is there a sense of urgency for this?
our company's management has asked itself how far the cft team is empowered to work independently. in the company,
What answer did they then give themselves? How open are they being about the challenge with others? How keen are they to establish a consensus view of reality?
there were always strict controls and processes
In Scrum there are commitments, including a Definition of Done which those doing the work are accountable for.
and now that they want to switch to scrum, they are afraid that the controls will fall away.
Courage is needed. It appears that some people might want change, but they don't want to change.
So how far does the scrum team have the power to work independently
If they are truly cross functional they will have the power. From what you go on to say, perhaps the real question is whether they will be allowed the focus to stop starting and start finishing:
without someone constantly interfering.
That rather depends upon how far are they respected to focus on and meet whatever commitments they make for themselves, each and every Sprint.
And can't that also go in the wrong direction or is that what the reviews are for?
Of course it can go in the wrong direction: that's what empiricism is for. Sprint Reviews play a part in this, because Scrum is a framework for establishing and maintaining empiricism under conditions of high uncertainty. The leap-of-faith being taken before obtaining an outcome is never more than one Sprint.
Scrum is about learning to build the right thing at the right time. The Scrum Values of commitment, focus, respect, openness, and courage may be seen as the professional underpinnings of the framework.
Perhaps the time is ripe to explore these values with everyone concerned, including with management.
Thx very useful answer