This is the test intended for those who have completed the Scrum training course for PO (3-4/7/2014)
Product Owner
ScrumMaster
Team
Everyone within the Project
Rate this question:
Report the Team member to his or her manager
Have the Team member do the testing.
Meet with the Team member to determine a solution
Ask the ScrumMaster to move the Team member off the Team
Rate this question:
The ScrumMaster tells Olivia to prepare an example and presentation for the Team so they can consider using the code
After the Daily Scrum meeting is held, a separate meeting is conducted to discuss the open source solution
All members of the Team are told to evaluate Olivia's solution and report back to the team at the next Daily Scrum meeting
The Product Owner notes the impediment and solves the problem after the meeting
Rate this question:
Team
Product Owner
ScrumMaster
No one
Rate this question:
Product Owner
Team
Stakeholders
ScrumMaster
Rate this question:
Scrum Development Team
ScrumMaster
Product Owner
Stakeholders
Rate this question:
To determine the re-composition of the Team
To facilitate the Team's search for improvements
To lead the Team in the evaluation of each individual Team member
To provide answers to the challenges that the Team identifies
Rate this question:
The Team should not use daily Scrum meetings to report impediments
It is the ScrumMaster's top priority to remove impediments.
It is the Product Owner's job to remove impediments
A slow running server is not considered an impediment
Rate this question:
To comment on the Team's progress
To make sure the Team is still on target for its Sprint goals
To tell the Team which tasks to work on next and update the Product Backlog
To see the progress being made and determine whether the Team needs help
Rate this question:
Four hours maximum
Four to eight hours
At least eight hours
As long as required
Rate this question:
Determine the appropriate release dates.
Determine the appropriate technical solution for the project
Determine the Team composition necessary for success.
Determine the length of the Sprints.
Rate this question:
Features a detailed overview that enlightens and inspires
Provides a complete breakdown structure of the ROI formula
Describes why the project is pursued and the product desired end state
Outlines traceability back to overall corporate governance in IT investment
Rate this question:
Scrum Teams place value in following a plan, but they value responding to change even more
Planning is not important in Scrum
Scrum is intended to be an efficient way to carry out plans that have already been made
Traditional planning is replaced by the Sprint Burndown chart.
Rate this question:
Controls the priority order of items in the team's backlog
Is the Team's Scrum expert.
Creates, refines and communicates customer requirements to the Team.
Is the keeper of the product vision
Rate this question:
ScrumMaster
Product Owner
This is outside of the scope of Scrum
The self-managing Team
Rate this question:
Product Owner and Stakeholders
Product Owner,ScrumMaster, and Team
ScrumMaster, Project Manager, Team
Team
Rate this question:
Functionality that has been deployed to the users and delivers real business value
Functionality that has been designed and analyzed
Product functionality ready to be tested
An increment of potentially shippable product
Rate this question:
Directing the Team's daily activities
Keeping stakeholders from distracting the Team
Managing the project and ensuring that the work meets the commitments to the stakeholders
Optimizing the business value of the work
Rate this question:
Architecture emerges.
Architecture is not important, but functionality is important
Architecture is defined and planned up front.
Architecture is defined and implemented in the first iterations.
Rate this question:
The Team has authority to swap Sprint backlog items with Product Backlog items if it cannot finish them.
The Team works under the authority of the Product Architect, who has set the definition of done
The Team works according to the priorities set by the ScrumMaster, as the ScrumMaster is committed to the Scrum framework.
The Team does whatever is necessary to achieve the goal
Rate this question:
For the ScrumMaster to manage the progress during the Sprint
For the Team to manage themselves during the Sprint
For the Team to manage the number of hours spent on tasks in the Sprint
For the Product Owner to understand what the Team has committed to for a Sprint
Rate this question:
For the Team to review their work and to determine what is needed to complete the next set of backlog items
For Stakeholders to review what the Team has built and to give input on what to do next
For Stakeholders to "hold the Team's feet to the fire" - to make sure something is produced during the Sprint
For the Product Manager to be able to show progress to the Stakeholders
Rate this question:
Delivers design documents
Develops a plan for the rest of the Sprints
Accomplishes the Sprint goal
Predetermines the complete architecture and infrastructure
Rate this question:
The Project Manager
The Team
The Product Owner
The ScrumMaster
Rate this question:
No. The person would have too much power and it would create confusion
Yes, if the person has the authority and empowerment to do both things
No. It would take too much of one person’s time
Yes, as long as the person can balance both responsibilities with care.
Planning is not required in an agile project, as the project is focused on current status.
Responding to change is more important than following a plan
Sign-off on the detail of Product Backlog items is mandatory before any item can be planned into an iteration.
Upfront planning and design is an integral stage before development can begin
Rate this question:
After every Sprint
After every day
After every release
After every week
Rate this question:
Project Manager
Team lead
ScrumMaster
Team
Rate this question:
The Product Owner’s participation is defined by the Team.
The Product Owner outlines the additional changes that must be absorbed by the Team in the Sprint.
The Product Owner ensures the Burndown rate is maintained at the estimated rate
The Product Owner provides instruction to the Team on how to implement a workable solution
Rate this question:
Respect the CEO’s authority and add the story to the current Sprint without any adjustments
Add the story to the next Sprint.
Inform the Product Owner so he/she can work with the CEO
Add the story to the current Sprint and drop a story of equal size
Rate this question:
The Team extends the length of the Sprint until the Product Owner returns
The ScrumMaster assumes the responsibilities of the Product Owner
The Sprint is abnormally terminated
The product increment may not meet expectations.
Rate this question:
Changes are accepted only if other features are removed from the backlog such that a fixed end-date is maintained.
Changes are accepted up until the point that the first Sprint begins. Then, changes are deferred to a future release
Changes are accepted at any time during the development effort depending on the business value of the change, the Product Owner's acceptance, and the ability of the team to respond in a timeframe acceptable to the Product Owner.
Changes are accepted up until about halfway through the project, then all changes are deferred to a future release
Rate this question:
Together with the Product Owner, focus on what can be done and identify a way to deliver something valuable at the end of each Sprint
Extend the Sprint by a few days to accommodate the extra work
Suggest the Product Owner abnormally terminate the Sprint
Immediately escalate to Senior Management
Rate this question:
Transparency, inspection, and adaptation
Planning, committing, and measuring
Feedback, courage, and simplicity
Planning, taking action, and checking for quality
Rate this question:
Quiz Review Timeline (Updated): Mar 14, 2024 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.