As I promised in my previous articles, Roles in Scrum and Events in Scrum, I’m following up with a related article on Artifacts in Scrum.
In Scrum there are three tangible deliverables, called artifacts. These artifacts consist of the requirements for the overall project, the requirements for each piece of the project, and the project itself.
Continue reading “Artifacts in Scrum”
This article will focus on the Roles in Scrum and it will be followed by another two which will contain details about the Events in Scrum and Artifacts in Scrum.
Scrum is an Agile framework used to develop projects and is based on the concept of “KISS” (i.e. Keep it Simple Stupid). The first mention of this technique can be found in 1986, by Hirotaka Takeuchi and Ikujiro Nonaka and then it was used for commercial product development. The first official document defining Scrum was presented in 1995 and was written by Jeff Sutherland and Ken Schwaber.
The name “Scrum” is a term from rugby, and it’s used as a metaphor to reflect the degree of cooperation needed to succeed. So scrum is a Team pack in rugby where everyone in the pack acts together to move the ball down the field.
Magda Miu 