Sure, if you start with an established team, where the majority of the team has been trained in Scrum or done Scrum before, and you're working on BAU (Business As Usual) development, it's reasonably straightforward.
If you have a free choice about where to start implementing Scrum, I would highly recommend starting *there*.
But...
If you have a newly formed team, where the majority of the team has not done Scrum before or been on Scrum training, and you're working on a ground-up development project, implementing Scrum can be a painful and frustrating experience for everyone involved!
I have seen this situation quite a few times now. And without fail the experience seems to be the same.
Almost as much time is spent discussing the process and how things should be done as actually doing it. The product backlog is confusing and disorganised. Requirements are not clear. User Stories are not adequately prepared. Sprint Planning takes *days* instead of hours. And we all know how much developers love sitting in meetings!