Scrum Artifacts: Totally Transparent and the Basis for Inspection and Adaptation

Jeb Riordan
A free video tutorial from Jeb Riordan
PMP, Project Management Consultant
4.1 instructor rating • 6 courses • 21,587 students

Lecture description

By the end of this lecture you will know what artifacts are needed in a practical scrum based project for transparency, inspection and adaptation of the product of the project 

Learn more from the full course

Scrum Made Easy: Become an Effective Scrum Team Member Today

Everything You Need to Know About the Scrum Roles, Events and Artifacts for Successful Product Development

03:10:52 of on-demand video • Updated November 2018

  • Become a valuable member of a Scrum Team - Scrum Master, Development Team Member
  • Have a practical understanding of the Scrum processes and what you need to do to contribute to the success of your project. You will be able to use the Scrum process to deliver your product
  • Understand the different roles in a Scrum Team, the Scrum Artifacts and the Scrum Events
  • Confidently facilitate the Scrum Events, daily scrum, sprint planning meetings, sprint reviews, sprint retrospectives
  • Be able to write concise User Stories, develop your Sprint Backlog and create your Sprint Task-board
  • Be able to estimate the effort needed to complete tasks and monitor progress using burn-down charts
  • Appreciate a little theory: The Agile Principles, the Scrum Values
English All are described in the following lectures, so lets begin I always thought you found artifacts in museums. I always thought you found artifacts in museums. Well you do but you also find them in product development projects using an agile or scrum framework. What are they? Well let’s keep it simple, artifacts are the means to record the scope of the work and record the progress of the work. They are visual aids easily understood by all key stakeholders Artifacts in scrum maximise the transparency of key information so that everybody has the same understanding of the product and the progress of the work And as long as we are comfortable with the accuracy of the artifacts can be used as a basis for inspection and adaptation The scrum guide only mentions 3 artifacts, The product backlog, the sprint backlog and the increment But in a practical scrum project we also need a means to limit the work we do through a definition of done We need to estimate the amount of work remaining to be done in the form of a burndown chart And we need to show the status of the works through a very visible sprint task board