The documents / artifacts created in Scrum
Filed Under Document, Product, Product Backlog, Product Owner, Scrum | Posted on January 26, 2010
First, for all those of you are asking what an artifact is. Well, if you consider the Wikipedia definition, “An artifact is one of many kinds of tangible byproduct produced during the development of software.”, it can be used in the current case to refer to the documents that we generate from the Scrum process. The reason I explained what an artifact was, because I had to refer to find the meaning myself, and I would consider that there would be a number of people who would not know what an artifact was. In simple language, it means the documents that one generates from the process, but can also mean other deliverables from the process.
In the case of Scrum, there are 2 main types of artifacts that we generate, one relating to the various documentation, and the other referring to the actual product generated at the end of the Sprint cycle (and for which a demo is given), as well as the final completed process generated from the overall process. The product is assumed to contain all the features that one planned to complete for the current Sprint, with any failures to complete some of these features being evaluated in the Sprint review.
Now, let us consider the various documents that get generated from the entire Scrum process.
Product Backlog: This is the overall prioritized list of features that are being evaluated for getting added to the product. This documents is owned by the Product Owner.
Sprint Backlog: The Sprint Backlog is the listing of features that are to be implemented in the current Sprint cycle, and is created during the Sprint Planning process. The Sprint Backlog is owned by the feature team.
Burndown charts: The Sprint Burndown chart and Release Burndown chart are reports that depict the amount of work required to be completed for the Sprint and Release respectively. They are one of the most important tools to be used for depicting the progress of activities during the progress of the Scrum, and are extremely important in determining whether the schedule of features will be met.
|
|
|
If you are interested in software processes, find this post informative, and want to learn more, why not subscribe ?
Subscribe in a readerSubscribe to get updates by Email
Leave a Reply
