Swarming is a simple way where as many team members as possible work simultaneously on one highest value item. All team members focus on completing this one item before picking the next highest value item. Working on many items / initiatives at a time increases work in progress, that causes delays and eventually waste of time.

The Definition of Ready isn't a practice defined in the Scrum Guide. However, some teams have created a checklist while refining the PBIs, to ensure that the PBIs entering the Sprint Planning are well refined, clear and free from dependencies. Caution must be excercised to avoid the definition of ready from becoming an extensive list that eventually hinders the emergence of right details later. The Scrum Guide hints about readiness of PBIs, however doesn't prescribe any such DOR criteria: "Product Backlog items that can be Done by the Scrum Team within one Sprint are deemed ready for selection in a Sprint Planning event. They usually acquire this degree of transparency after refining activities.

The maximum amount of Work-In-Process (WIP) that can be pulled in for processing / implementation within a workflow. This is a limit on the total amount of items that can be in process. The purpose of having a WIP Limit is to increase the focus on the flow of value. Due to the limits on WIP, the remaining work items can be either Waiting to be Picked up or Completed (Done). In a Scrum environment, to improve the flow of value delivery, it's recommended that the number of work items in progress may be lesser than the number of developers available to execute the work items.

Most popular - Agile and Scrum Glossary

Test Driven Development

Sprint Demo

Swarming

Definition of Ready

WIP Limit

Splitting User Stories