True
False
Rate this question:
When the Development Team finds it necessary
When the Product Owner determines it makes no sense to finish it
When the Scrum Master decides to
When the infrastructure and tools are not ready for the whole project
Rate this question:
A set of tests designed to be used in the next Sprint
A document that shows the solution design and helps the team develop the product
An Increment of Done software
A user interface layout designed to be used for the solution
Rate this question:
True
False
Rate this question:
8 hours for a one month Sprint
8 hours for a two week Sprint
6 hours for a one month Sprint
6 hours for a two week Sprint
Rate this question:
When needed, based on lessons learned
When asked by the Scrum Master
When asked by the Product Owner
Each Sprint
Rate this question:
Just enough to understand the design and architecture.
Just enough for the Development Team to be able to forecast what it can do, and start the first several days of the Sprint.
Just enough for the Scrum Master to be able to assign tasks to developers
Just enough for the Scrum Master to be able to assign tasks to developers
Rate this question:
True
False
Rate this question:
True
False
Rate this question:
The Product Owner
The project manage
The Scrum Master
The Development Team
The team leader
Rate this question:
True
False
Rate this question:
Ordering the Product Backlog items properly
Preventing changes to the Sprint Backlog once the Sprint begins
Assigning tasks to developers and following up on them
Facilitating meetings and removing impediments
Rate this question:
True
False
Rate this question:
When all Sprint Backlog tasks are done
When the timebox expires
When all Sprint Backlog items are done
When the Product Owner considers it done, with any appropriate reason
Rate this question:
True
False
Rate this question:
In the previous Sprint Retrospective
In the beginning of the project
In the Sprint Planning meeting
Any time during the Sprint
It’s not mandatory
Rate this question:
There’s no such thing as Sprint zero
Prepare the Product Backlog for the next few Sprints
Prepare the Product Backlog for the whole project
Communicate with the customer and understand the requirements
Rate this question:
There’s no tester role in Scrum
They proactively verify the programmers output
They help the team incorporate the test driven development practice
They verify the programmers output
They find bugs
Rate this question:
The Scrum Master
The Development Team
The Product Owner
The Development Team and the Product Owner together
The whole Scrum Team
Rate this question:
Product Backlog ordering
When to release
Sprint length
How to best accomplish its work
Rate this question:
The Development Team members and the Product Owner
The Development Team members and the Scrum Master
The Development Team members
The whole Scrum Team
Rate this question:
It’s the Development Team’s plan for the Sprint
Each of its items is assigned to a team member
Each of its items has been estimated in hours
It’s composed by the Product Owner
Rate this question:
The business analyst
The Development Team
The solution architect
The Product Owner
The Scrum Team
Rate this question:
Reject the request
Refer the customer to the Product Owner
Add the item to the current Sprint Backlog
Replace an item in the current Sprint Backlog with the new one
Add the item to the Product Backlog
Rate this question:
True
False
Rate this question:
Facilitating Scrum events
Removing impediments for the Development Team
Assigning tasks to individual developers
Coaching the organization in Scrum adoption
Rate this question:
True
False
Rate this question:
Optimizing the work required for Sprint Backlog items
Resolving internal team conflicts
Measuring the performance of the Sprint
Selecting the Product Owner
Rate this question:
Increments will be more complete
Reporting to the project manager will be easier
There will be increased transparency of the Increments
Increments will be closer to being potentially shippable
Rate this question:
Based on the value of the items
Based on the size of the items
Based on the criticality of the items
Based on dependencies among the items
Based on the amount of risk related to each item
Rate this question:
The technical debt
The progress
The amount of remaining work
The capacity of the team
Rate this question:
Every 3 Sprints
At the end of each Sprint
Whenever the user acceptance testing is done
When the Product Owner asks for it
Before each planned release
Rate this question:
The Sprint doesn’t make sense any more
They can’t cancel Sprints
There’s an unsolved technical dependency
Not enough information is available for the development
Rate this question:
Scrum is a framework for developing and maintaining complex products
Scrum is a methodology for managing complex projects
Scrum is based on empirical process control theory
Scrum is like a traditional process but with Sprints and related artifacts
Rate this question:
It grows and change as more is learned about the project
It provides information required for the design phase of the project
It’s a baseline for the change management process
It contains all the tasks required for the project
Rate this question:
The won’t need Sprint Reviews any more
They won’t need a Scrum Master any more
They will improve the Definition of Done
They won’t need Sprint Retrospectives any more
They can release every Increment
Rate this question:
Daily Scrum
Sprint Retrospective
Sprint Review
Product Backlog refinement
Release planning
Rate this question:
Nothing
The Development Team will continue to the next Sprint without a Sprint Review
The Sprint will be canceled
The Sprint will be extended
Rate this question:
Throughout the project
In the Sprint zero
Before the first Sprint
Rate this question:
They can be added to the Product Backlog
They can be added to the Definition of Done
They can be handled in a separate Sprint dedicated to security
They can be outsourced to a department responsible for security
Rate this question:
When all of its tasks are complete
When everything is done based on the Definition of Done
When the Sprint is over
When the user acceptance tests are done
Rate this question:
Nothing; there’s no time between the two
Refactor the developed items
Release the Increment
Prepare for the Sprint Planning
Rate this question:
True
False
Rate this question:
True
False
Rate this question:
Increased commitment
Increased predictability
Increased self-accountability
Increased rule compliance
Rate this question:
An opportunity for improving the Scrum processes
An opportunity for reviewing the viability of the project
An opportunity for inspection and adaptation
An opportunity for receiving approval for the work done
Rate this question:
True
False
Rate this question:
The Product Owner
The Development Team
The resource manager
The Scrum Master
Rate this question:
Quiz Review Timeline (Updated): Jan 10, 2025 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.