You're not completely incorrect in your impression of the Sprint Backlog. The Product Backlog is the tool used by the product owner to keep track of all of the features that stakeholders would like to see implemented in the product whereas the Sprint Backlog is a subset of the Product Backlog representing the current active Sprint iteration.

From The IT BA - Product Backlog vs Spring Backlog:

A product backlog is a list of all desired product features (weather you plan to implement them or not).

Anyone can add anything to the Product Backlog at any time. However, the product owner prioritizes it. So if you and I both add a feature request to add a quote of the day feature to a product, the product owner could very well put this at the bottom of the stack, meaning she doesn't really intend to have that feature added.

The Sprint backlog is a to-do list of backlog items to be completed in the current iteration.

The Sprint Backlog, on the other hand, represents the current Sprint iteration, and once a Sprint begins, no one should be adding or removing anything from the Sprint Backlog. The Sprint Backlog is put together by the team -- and in case this isn't clear, only by the team -- by selecting items from the top of the Product Backlog. If something is not in the Product Backlog then it should not be in the Sprint Backlog.

If someone later on wants to add feature Y to the list, and it's a high priority item, it still goes in the Product Backlog, and if it's an important enough feature, the product owner can move it to the top of the Product Backlog so that it's likely to be selected in the next Sprint iteration.

You're not completely incorrect in your impression of the Sprint Backlog. The Product Backlog is the tool used by the product owner to keep track of all of the features that stakeholders would like to see implemented in the product whereas the Sprint Backlog is a subset of the Product Backlog representing the current active Sprint iteration.

From The IT BA - Product Backlog vs Spring Backlog:

A product backlog is a list of all desired product features (weather you plan to implement them or not).

Anyone can add anything to the Product Backlog at any time. However, the product owner prioritizes it. So if you and I both add a feature request to add a quote of the day feature to a product, the product owner could very well put this at the bottom of the stack, meaning she doesn't really intend to have that feature added.

The Sprint backlog is a to-do list of backlog items to be completed in the current iteration.

The Sprint Backlog, on the other hand, represents the current Sprint iteration, and once a Sprint begins, no one should be adding or removing anything from the Sprint Backlog. The Sprint Backlog is put together by the team -- and in case this isn't clear, only by the team -- by selecting items from the top of the Product Backlog. If something is not in the Product Backlog then it should not be in the Sprint Backlog.

If someone later on wants to add feature Y to the list, and it's a high priority item, it still goes in the Product Backlog, and if it's an important enough feature, the product owner can move it to the top of the Product Backlog so that it's likely to be selected in the next Sprint iteration.

You're not completely incorrect in your impression of the Sprint Backlog. The Product Backlog is the tool used by the product owner to keep track of all of the features that stakeholders would like to see implemented in the product whereas the Sprint Backlog is a subset of the Product Backlog representing the current active Sprint iteration.

From The IT BA - Product Backlog vs Spring Backlog:

A product backlog is a list of all desired product features (weather you plan to implement them or not).

Anyone can add anything to the Product Backlog at any time. However, the product owner prioritizes it. So if you and I both add a feature request to add a quote of the day feature to a product, the product owner could very well put this at the bottom of the stack, meaning she doesn't really intend to have that feature added.

The Sprint backlog is a to-do list of backlog items to be completed in the current iteration.

The Sprint Backlog, on the other hand, represents the current Sprint iteration, and once a Sprint begins, no one should be adding or removing anything from the Sprint Backlog. The Sprint Backlog is put together by the team, by selecting items from the top of the Product Backlog. If something is not in the Product Backlog then it should not be in the Sprint Backlog.

If someone later on wants to add feature Y to the list, and it's a high priority item, it still goes in the Product Backlog, and if it's an important enough feature, the product owner can move it to the top of the Product Backlog so that it's likely to be selected in the next Sprint iteration.

You're not completely incorrect in your impression of the Sprint Backlog. The Product Backlog is the tool used by the product owner to keep track of all of the features that stakeholders would like to see implemented in the product whereas the Sprint Backlog is a subset of the Product Backlog representing the current active Sprint iteration.

From The IT BA - Product Backlog vs Spring Backlog:

A product backlog is a list of all desired product features (weather you plan to implement them or not).

Anyone can add anything to the Product Backlog at any time. However, the product owner prioritizes it. So if you and I both add a feature request to add a quote of the day feature to a product, the product owner could very well put this at the bottom of the stack, meaning she doesn't really intend to have that feature added.

The Sprint backlog is a to-do list of backlog items to be completed in the current iteration.

The Sprint Backlog, on the other hand, represents the current Sprint iteration, and once a Sprint begins, no one should be adding or removing anything from the Sprint Backlog. The Sprint Backlog is put together by the team -- and in case this isn't clear, only by the team -- by selecting items from the top of the Product Backlog. If something is not in the Product Backlog then it should not be in the Sprint Backlog.

If someone later on wants to add feature Y to the list, and it's a high priority item, it still goes in the Product Backlog, and if it's an important enough feature, the product owner can move it to the top of the Product Backlog so that it's likely to be selected in the next Sprint iteration.