We could really chase our tails on this.
I did a blog post awhile ago that basically said we have important work to do, and quibbling is not one of them. So I made a decision that is pretty good for many reasons and am sticking with it.
"The members of a "Development Team" are often seen as "developers" - missing all the other roles that are necessary to create a shippable increment, such as testers, build and integration specialist, etc. Yes, we say the team must be cross-functional and I believe the term "Delivery Team" would address this better than "Development Team".
We cannot sneak anything by you!!! We were trying to get the other cross-functional skills to see their role in developing something that is delivered. They are "developers", not just people who program.
Developers of course deliver, if that is part of the definition of done for that Sprint. In my blog, I refer to this in the SDK entry.
You are suggesting that a "delivery" team wouldn't have any development activities?
Read closely: "...only the Development Team members PARTICIPATE in the Daily Scrum." It can be held in Ebbets field, but only the team members participate.
There are many techniques and procedures for accomplishing the work at team does before and during a Sprint. They fall within the realm of methodology: in a specific set of circumstances or context, this procedure (refining backlog in this manner) will assist in reaching a desired outcome. I look for people to come up with procedures like this. However, we won't bake them into Scrum. Look up Plimsoll mark. Add procedures, techniques, etc. to Scrum and it will go past its Plimsoll mark and won't be seaworthy.
Backlog refinement is so situational that it reminds me of the definition of done. I think of both as practices that depend on ...
As we move forward, out goal will be to keep Scrum a framework that works for all software development, with its flexibility provided by the intelligence, diligence, and determination of the practitioners.