Skip to main content

Scrum Framework - Three Artifacts - By Ankur Mistry

In this article, we will discuss three artifacts in Scrum Frameworks.
There are three artifacts in Agile Scrum Framework.
  1. Product Backlog
  2. Sprint Backlog
  3. Working Product

    (Figure: Scrum Process from : https://commons.wikimedia.org/wiki/File:Scrum_process.svg)

Product Backlog is an ordered list of tasks or features that need to be done within the project. It may have short descriptions of all functionality desired in the product. Product Backlog is owned by the Product Owner.
  • It is an ordered list of features for the product.
  • Each product item has an Order, Value, Description, and Estimation.
  • Generally, tasks which have more business values are the top priority.
  • Product Owner owns the product backlog.
  • Product Owner makes sure that the product backlog is clear and transparent to the team.
  • Anyone from the team can add an idea in the product backlog but it's product owner who decides which one stays there.
  • There is one Product Backlog for one product, multiple teams who are working on the same product use the same product backlog.
Product backlog has the following different types,
  • Features
  • Bugs
  • Technical work
  • Knowledge acquisition
Sprint Backlog is an ordered list of tasks that are selected by the Scrum team from the product backlog to be achieved or completed in the sprint. The sprint backlog is owned by Development Team.
  • Set of product backlog items selected for the sprint.
  • Sprint Backlog makes visible all of the work items that development team identifies as a priority to meet the sprint goal.
  • Owned by development team and updated by only development team during the sprint.
  • Sprint goal is fixed but new tasks which need to complete the sprint goal can be added to the sprint backlog during the sprint.
  • It is critical that team will only commit to items that they can complete in particular sprint.
  • Sprint Burndown and Sprint Burnup Chart will be managed during the sprint.
Working Product is something that we have created using product backlog and scrum process which provides benefits to a market.
  • It's a sum of all the tasks from product backlog that are completed during the sprint and all previously completed sprints.
  • All tasks must meet acceptance criteria and meet the definition of 'Done'.
  • Product Owner decides which tasks have been done and are ready for release. 
Scrum depends or relies on transparency and the above 3 artifacts help manage transparency among the Product Owner, Scrum Master, and Development Team.

It is the Scrum Master's duty to work with the Product Owner and Development Team to understand if the artifacts are completely transparent. I hope you liked this article, please leave your comments and suggestions in the comment box.
Reference
  • https://www.scrumalliance.org/
  • http://staragile.com

Comments

Post a Comment

Popular posts from this blog

What is User Story ?

A User Story is a short description of something that your customer will do when they come to your website or use your application/software,  focused on the value or result they get from doing this thing. User stories are: written from the point of view of a person using your website or application written in the language that your customers would use. Three C’s of the user story: Card – stories are traditionally written on note cards, and these cards can be annotated with extra details Conversation – details behind the story come out through conversations with the Product Owner Confirmation – acceptance tests confirm the story is finished and working as intended. Template for User Stories : A user story template often uses the following type of format: As a <role> , I want <feature> so that <reason> . Examples of user stories are: As a  user , I want  to upload photos  so that  I can share photos with others . A...
1 comment
Read more

Agile Story Point Estimation Techniques - T-Shirt Sizing by - Ankur Mistry

In my previous articles, we have discussed  Agile Story Point Estimation  and  Agile Story Point Estimation Techniques - Planning Poker . In this article, we will learn Story Point Estimation using T-Shirt Size Technique. What is T-shirt sizing? T-shirt Sizing is one of the Story points sizing technique to estimate user story usually used in agile projects. It's a relative Estimation Technique. Rather than using a number of planning pokers, here, Items are classified into t-shirt sizes: XS, S, M, L, XL. The term originates from the way T-shirt sizes are indicated in the US. Rather than having T-shirts in sizes 4, 5, 6 etc, there are just a few sizes: Small (S), Medium (M), Large (L) and Extra Large (XL) and so on. With T-shirt measuring, the development team is made a request to evaluate whether they think a story is extra-small, small, medium, large, extra-large, or double extra-large. By expelling the numerical score, the development team is allow...
Post a Comment
Read more

Scrum Framework - 5 Events in Scrum Framework - By Ankur Mistry

In my previous articles, we have discussed  3 Roles  and  3 Artifacts  in Scrum. In this article, we are going to discuss 5 events in the Scrum Framework. There are Five events in Agile Scrum Framework. Sprint Planning Daily Scrum Sprint Review Sprint Retrospective The Sprint ( Figure: Life cycle of Scrum from  http://www.agiletroop.com/product/life-cycle-of-scrum/ ) Sprint Planning  is the event in which the Product Owner presents the ordered product backlog to the development team. As the word suggests, 'Sprint Planning' means we are going to plan the work to be done in the Sprint. There are two main parts - 'What' and 'How'. 'What' can be done in this Sprint? 'How' will the selected work get done? What can be done in the Sprint - In this part, the Product Owner presents the product backlog items with high business value tasks as a first priority to the development team. All team members collaborate to understand ...
1 comment
Read more