The defined terminology in Scrum was selected, designed, and defined specifically for supporting the Scrum Framework. Understanding the differences between traditional methods and the Scrum Framework will help move teams in the right direction in Scrum adoption.

As a servant/leader, the Scrum Master facilitates conversations through open ended Question:s in order to help the team members make the best possible decisions according to what is known at the time. He/she does not approve or reject team decisions but ensures the team stays within the boundaries of the Scrum framework.

Scrum employs an iterative, incremental approach to optimize predictability and control risk. The primary objective of a Sprint (iteration) is to produce a potentially shippable product Increment. Having an Increment will allow the Scrum Team to know the right thing to do in the upcoming Sprint. Having a velocity is important but working software is the primary measure of progress.

All Product Backlog items selected for the Sprint are owned by the Development Team as a whole. Although individual members may work on specific tasks, the Development Team is still accountable for doing the work to deliver a shippable Increment.

Technical debt is any shortcomings in the code. It is a natural by-product of software development (unavoidable) and can at best be managed. If neglected, it will compound and have a negative effect on the team's ability to the deliver value. A team can have an artificially high velocity by taking shortcuts or introducing technical, debt into the system. This can give a false assumption about the current state of the product. It can look good on the surface but underneath can be a mess.