I think Imran Afzal’s previous answer already covered the original question really well, but one angle I would add is patience.
In my experience, one of the first things Scrum does is expose problems that were already there, but had somehow been accepted, tolerated, or pushed under the rug until an agile transition begins. Too many dependencies, unclear priorities, overloaded teams, outside interruptions.
That can make it look like Scrum is not working, when in reality it is simply making those issues more visible.
So for me, one sign that it is becoming real Scrum is not just the ceremonies or roles, but whether the team is becoming more honest, more predictable over time, and more consistent in delivering valuable increments. Saving Changes...
According to the Scrum Guide, the Scrum framework, as outlined in the guide, is immutable. This means that if you're following the Scrum Guide you're using scrum, and if you modify your approach beyond the Scrum Guide you're no longer using Scrum.
But, does it really matter?
If you want your development team to be agile, you can implement Scrum or one of several other agile or hybrid methodologies/frameworks/approaches/whatever. If you want your business to be agile you're going to need more than agile development. You should not expect to implement Scrum and have organizational agility emerge automatically or organically.
Scaled agile models can help, but organizational agility comes from three systemic capabilities - decision agility, funding agility, and structural agility - not from a framework. An organization becomes agile when decision-making, funding, and structure are aligned around fast, informed tradeoffs, not just because it implements an agile framework. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First of all: people need to understand what agile is. Agile was born in 1990 trying to find an alternative to Lean. Agile was born in manufacturing and time after software people took it. I can talk about that because I was part of both movements but no matter that you can check the foundations because documents are there. Then Agile is an approach so it does mean it is independent of the method and the life cycle to use. You can apply agile with waterfall life cycle. Putting this in terms of the PMI you can check in business analysis information belonging to PMI because you will see an activity where the business analyst is accountable to help to define the approach to use to create the solution. Rememenber: we are hired to particpate in the creation of a solution where solution is "the thing" to be created (product/service/result) plus "the way" to create it (the project/program). Scrum is just one of the ways to create the solution. Other thing to remember: Scrum is a framework that must be completed with techniques and tools. Example: you will not find a line in the Scrum description saying that requirements must be writting in User Story format. So, with all my due respect, I do not agree with some of the previous answers (and sorry if I missunderstood some of them).
Community Champion
