facebooktwittergoogle_plusredditpinterestlinkedintumblrmailby feather

Welcome to your Key Artifact Test.  Please note that the test has both multiple choice style questions with radio buttons and multiple response questions with tick boxes.  A multiple response question will have 1 or more answers.  The breakdown of the results will be emailed to you to help your learning.



When should a user story be broken down?
What is the difference between the sprint burndown and product burn down chart?(choose 3)
What is wrong with this user story?

“As an administrator, I want a way of adding email addresses to old clients”
What  is wrong with this user story?

"As a customer, I can specify files or folders to backup based on file size, date created and date modified.” ( choose 2)
Can the sprint backlog be reprioritised during a sprint?
Why are cards (3 x 5) a good way of recording user stories?(choose 2)
If an item is 90% complete the development team can :
The product backlog should have some of the following characteristics? ( choose 3)
Can the sprint backlog be changed during a sprint?
Who defines the sprint goal?
When can done be defined?(choose 2)
Who creates the performance graphs?
Is at mandatory to release a product revision at the end a sprint?
It is recommended that a task should take no longer?
Who updates the product backlog and ensures the user stories are refined?
The items at the top of the product backlog will be different from those at the bottom because...(choose 2)
What is a sprint burnup chart?
What is the danger of using computerized systems for tracking tasks?
What can you tell from a burndown chart?
How can the sprint backlog be designed to create an incremental shippable product?
When are tasks developed and assigned?
What is wrong with this user story?

“As a power user, I want to refresh the screen regularly, so that I can always have the most up to date information”
It is recommended that a user story should take no longer than?


Be sure to click Submit Quiz to see your results!