My current thoughts are around non-software teams.
Scrum has evolved from software developers for software development. It then expanded into the world of IT Operations, and we got DevOps.
I now see it moving into business teams.
At my Bank job, we had BizDevOpsSec because I think Security was feeling left out of being important and business was driving the transformation.
I have been particularly looking into Agile for Operations. One of the biggest issues I noticed was Scrum Coaches teaching Software Development Scrum to Operational people.
A lot of the Scrum analogies used made stupid sense to Operational people.
I come from an IT Operational background and so understand the differences and care factors between the two groups.
How do we go about introducing Scrum to non-software development teams? How do we change our messages, our analogies our approach?
Operations, Developer, TFS Admin / Auckland, New Zealand
Agile coaches answer:
Scrum originates from software product development, that’s true. But it is not limited to it - and never was.
The Scrum Guide says that Scrum is a framework to solve complex-adaptive problems. Product Development is one of these kinds of problems.
The Scrum Guide further states that a Development Team in Scrum needs to have all the skills to create a Done Increment of Product each Sprint. Done means releasable.
Therefore if you need business people to get something releasable, they have to be on the team. The same goes for operations or security skills.
Therefore in my opinion DevOps and all its derivates are just a new name for Scrum done right. ;)
Answer by Peter Götz