We call artefacts in Scrum the results of the Scrum Process.
A vision is a clear, bold, attractive and emotionalizing image of the product you are striving for.
Product Backlog Item
In Scrum we identify the functions to be delivered listed in the product backlog as product backlog items.
The product backlog is a list of product backlog items that are prioritized by the Product Owner according to their importance for the success of the project.
The Product Owner determines the sprint goal together with the team. It focuses all the Scrum team and Product Owner efforts related to this as a mutually agreed upon issue.
Selected Product Backlog
The selected product backlog originates in the sprint planning 1 meeting. It contains the backlog items that the team can deliver by the end of the sprint. The selected product backlog is oriented to the sprint goal.
We describe tasks and jobs as everything that must be done in order to achieve the goal of the sprint and to develop the requested functions.
In Sprint Planning 2 a list of tasks is created that the team must work through in order to achieve the sprint goal. We call this list the Sprint Backlog. It is reworked and updated daily. The team adds new tasks and checks off completed tasks on it. The Sprint Backlog creates an overview of who is doing what and lists what still needs to be done.
The Release Plan
The release plan shows during which sprint the team will deliver a backlog item. It is not an instrument to tell a team what they have to deliver when. It only shows when the respective backlog items are expected from the team. So it is an information instrument and not a planning instrument in the classic sense.
The Impediment Backlog
The impediment backlog is the list of all blockades that must be cleared up for a team to become more productive.
The Product Increment – usable software
The team strive to deliver something they can present at the end of a sprint. The functions that are presented at the end of a sprint must actually be in a deliverable state.