Although I already talked about them in my previous articles, I decided to make an article dedicated to all of the scrum artifacts. This will allow you to have all of the artifacts in one single article.
To begin with, what does the term “artifact” mean?
Take the definition from Wikipedia:
An artifact is one of many kinds of tangible by-products produced during the development of software. Some artifacts help describe the function, architecture, and design of software. Other artifacts are concerned with the process of development itself—such as project plans, business cases, and risk assessments.
In scrum, we thus define 3 classic artifacts and 1 transparency artifact:
- product backlog
- sprint backlog
- definition of done (transparency artifact)
Indeed these 4 elements respond at the wikipedia definition. In scrum, this term of “artifact” is really important because they are one of main elements of scrum.
I am surprised at the use of this word because there is another definition which may be associated with this word (but less known) and which could be used to criticize the scrum artifacts:
An artifact is also an undesirable effect, a parasite for example in electronics.
Suddenly, some anti-scrum could say that the product backlog, the sprint backlog, the increment and the definition of done are undesirable effects … Obviously, you will understand that scrum does not use this definition of the word.
Our scrum artifacts
Having already described precisely these 4 scrum artifacts, I will describe them in one sentence and give you the link of the corresponding articles.
The product backlog is the set of needs collected to create the desired product:
Article : Backlog – definition
The sprint backlog constitutes all the elements that have been selected at the start of the sprint (during the sprint planning) with the aim:
- meet the sprint goal
- to increment the product with new things:
- new features
- new functions
- the plan to deliver the selected elements (technical subtasks, prioritization, etc.)
Article: Sprint backlog
The increment in scrum represents all the “done” elements of the current sprint in addition to those already finalized in the previous sprint.
Definition of Done
The development team will define together all the criteria which will allow to affirm that an item (user story for example) can be considered “done”. We commonly use the acronym Dod to define this practice.
Article: Definition of Done (DOD)
Conclusion scrum artifacts
Now I hope that this term of scrum artifacts will hold no secrets for you. It is not uncommon to have a lot of teams having a lot of trouble with this term, now, it’s probably clear for you.
So this term of scrum artifacts is clearer to you? Do you have any ideas for creating other scrum artifacts?
Useful link: board kanban