WorksheetsPSMI-Practice Exam
Total questions: 130
Worksheet time: 4hrs 20mins
When can a Development Team cancel a Sprint?
It can’t. Only Product Owners can cancel Sprints.
When functional expectations are not well understood.
When the Product Owner is absent too often.
When the selected Product Backlog items for the Sprint become unachievable.
When a technical dependency cannot be resolved.
How should a Development Team deal with non-functional requirements?
Ensure every Increment meets them.
Make sure the release department understands these requirements, but it is not the Development Team’s responsibility.
Handle them during the Integration Sprint preceding the Release Sprint.
Assign them to the lead developers on the team.
Scrum has a role called “Project Manager”.
True
False
In the Sprint Planning meeting, the Product Owner and the Development Team were unable to reach a clear understanding about the highest order Product Backlog items. Because of this, the Development Team couldn’t figure out how many Product Backlog items it could forecast for the upcoming Sprint. They were able to agree on a Sprint Goal, however.
Which of the following two actions should the Scrum Master support? (Choose two.)
Cancel the Sprint. Send the entire team to an advanced Scrum training and then start a new Sprint.
Forecast the most likely Product Backlog items to meet the goal and create a Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint.
Continue the Sprint Planning meeting past its time-box until an adequate number of Product Backlog items are well enough understood for the Development Team to make a complete forecast. Then start the Sprint.
Discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.
Ask everyone to take as much time as needed to analyze the Product Backlog first, and then reconvene another Sprint Planning meeting.
Which answer best describes the topics covered in Sprint Planning?
What to do and who will do it.
How conditions have changed and how the Product Backlog should evolve.
What can be done and how to do it.
What went wrong in the last Sprint and what to do differently this Sprint.
Who is on the team and what team member roles will be.
Which of the following is required by Scrum? (Choose all that apply.)
Sprint Retrospective.
Members must be stand up at the Daily Scrum.
Sprint Burndown Chart.
Release planning.
All of the above.
Who determines when it is appropriate to update the Sprint Backlog during a Sprint?
The Project Manager.
The Development Team.
The Scrum Team.
The Product Owner.
Who must attend the Daily Scrum?
The Scrum Master and Product Owner.
The Development Team.
The Development Team and Product Owner.
The Scrum Team.
The Development Team and Scrum Master.
When do Development Team members take ownership of a Sprint Backlog item?
At the Sprint planning meeting.
During the Daily Scrum.
Never. All Sprint Backlog Items are “owned” by the entire Development Team, even though each one may be done by an individual Development Team member.
Whenever a team member can accommodate more work.
The purpose of a Sprint is to produce a done Increment of product.
True
False
Who creates the definition of “Done”?
The Scrum Master as he/she is responsible for the Development Team’s productivity.
The Scrum Team, in a collaborative effort where the result is the common denominator of all members’ definition.
The Product Owner as he/she is responsible for the product’s success.
The development organization (or Development Team if none is available from the development organization).
Five new Scrum Teams have been created to build one product. A few of the developers on one of the Development Teams ask the Scrum Master how to coordinate their work with the order teams. What should the Scrum Master do?
Teach the Product Owner to work with the lead developers on ordering Product Backlog in a way to avoid too much technical and development overlap during a Sprint.
Teach them that it is their responsibility to work with the other teams to create an integrated Increment.
Collect the Sprint tasks from the teams at the end of their Sprint Planning and merge that into a consolidated plan for the entire Sprint.
Visit the five teams each day to inspect that their Sprint Backlogs are aligned.
Which two things should the Development Team do during the first Sprint? (Choose two.)
Make up a plan for the rest of the project.
Analyze, describe, and document the requirements for the subsequent Sprints.
Develop at least one piece of functionality.
Analyze, design, and describe the complete architecture and infrastructure.
Create an increment of potentially releasable software.
What are three ways Scrum promotes self-organization? (Choose three.)
By not allowing documentation.
By the Development Team deciding what work to do in a Sprint.
By preventing stakeholders from entering the development room.
By removing titles for Development Team members.
By being a lightweight framework.
What does it mean to say that an event has a time-box?
The event must happen at a set time.
The event must happen by a given time.
The event must take at least a minimum amount of time.
The event can take no more than a maximum amount of time.
A properly functioning Scrum Team will have at least one Release Sprint and may well have several.
True
False
Scrum is a methodology that tells in detail how to build software incrementally.
True
False
For which is the Scrum Master responsible?
Managing the performance of the Scrum Team.
The meetings and the objectives that a Scrum Team sets for itself.
The Scrum framework being adopted and used properly.
Keeping track of resource allocation.
A Development Team asks their Product Owner to re-order the Product Backlog. The team is waiting for an external supplier to deliver a specific software component. Without that component there won’t be enough work in the next Sprint to occupy the full team. The Product Owner asks the Scrum Master for help. What would be good advice to give the Product Owner?
Remind the Product Owner that his primary concern is the flow of value reflected in the ordering of the Product Backlog.
Tell the Product Owner to re-order the Product Backlog so the work involving the external component can be planned in a separate sprint.
Tell the Product Owner that the Product Backlog should be ordered to maximize utilization of the Development Team.
As the Sprint Planning meeting progresses, the Development Team sees that the workload is greater than they can handle. Which two are valid actions? (Choose two.)
Recruit additional Development Team members before the work can begin.
The Development Team ensures that the Product Owner is aware, starts the Sprint, and monitors progress.
Cancel the Sprint.
Remove or change selected Product Backlog items.
The Development Team works overtime during this Sprint.
Currently, your Development Teams are organized to address a single layer only (for example, front end, middle tier, back end, and interfaces). What are three things to consider when deciding to move away from such component teams toward feature teams? (Choose three.)
You cannot do Scrum without feature teams.
Productivity may suffer when making this kind of move.
Getting support from the business side first helps.
Feature teams have less communication overhead.
With feature teams, it is easier to calculate the productivity per team.
How often should Development Team membership change?
As needed, while taking into account a short term reduction in productivity.
Never, because it reduces productivity.
As needed, with no special allowance for changes in productivity.
Every Sprint to promote shared learning.
Who should make sure everyone on the Development Team does his or her tasks for the Sprint?
The Project Manager.
The Product Owner.
The Scrum Master.
The Development Team.
All of the above.
When is it most appropriate for a Development Team to change the definition of “Done”?
During Spring Planning.
Prior to starting a new Sprint.
During the Sprint Retrospective.
Prior to starting a new project.
The Daily Scrum is an event that happens every day. What would be three key concerns if the frequency were to be lowered to every two or three days? (Choose three.)
Opportunities to inspect and adapt the Sprint Backlog are lost.
Impediments are raised and resolved more slowly.
The Product Owner cannot accurately report progress to the stakeholders.
Too much work is spent updating the Scrum board before the meeting.
The Sprint plan may become inaccurate.
Which statement best describes Scrum? www.
A defined and predictive process that confirms to the principles of Scientific Management.
A complete methodology that defines how to develop software.
A cookbook that defines best practices for software development.
A framework within which complex products in complex environments are developed.
Which Scrum Values are exhibited by not building Product Backlog items that have low business value? (Choose three.)
Economic Value Added.
Respect.
Focus.
Earned Value.
Courage.
Who starts the Daily Scrum?
The person coming in last. This encourages people to be on time and helps to stay within the time box.
Whoever the Development Team decides should start.
The person who has the token.
The Scrum Master. This ensures that the Development Team has the meeting and stays within the time-box.
The person who last broke the build.
A Development Team selects a set of Product Backlog items for a Sprint Backlog with the intent to get the selected items “Done” by the end of the Sprint. Which three phrases best describe the purpose of a definition of “Done”? (Choose three.)
It controls whether the developers have performed their tasks.
It provides a template for elements that need to be included in the technical documentation.
It creates transparency over the work inspected at the Sprint Review.
It trucks the percent completeness of a Product Backlog item
It defines what it takes for an Increment to be ready for release.
Select two ways in which technical debt impacts transparency. (Choose two.)
When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.
It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint.
As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways.
It enhances transparency for the Product Owner as a Development Team is not allowed to do additional feature development in a Sprint as long as there is technical debt.
Which of these may a Development Team deliver at the end of a Sprint?
Failing unit tests, to identify acceptance tests for the next Sprint.
An increment of software with minor known bugs in it.
An increment of working software that is “done”.
A single document, if that is what the Scrum Master asked for.
How much of the Sprint Backlog must be defined during the Sprint Planning event?
Just enough tasks for the Scrum Master to be confident in the Development Team’s understanding of the Sprint.
The entire Sprint Backlog must be identified and estimated by the end of the Sprint Planning meeting.
Enough so the Development Team can create its best forecast of what is can do, and to start the first several days of the Sprint.
Just enough to understand design and architectural implications.
A Development Team is required to deliver a done Increment by the end of a Sprint. Select two statements that explain what “Done” means. (Choose two.)
All work the Development Team is willing to do.
Ready for integration.
No work left from the definition of “Done”.
Whatever the Product Owner defines as quality.
All work to create software that is ready to be released to end users.
What two factors are best considered when establishing the Sprint length? (Choose two.)
The organization has mandated similar length sprints.
The level of uncertainty over the technology to be used.
The frequency at which team formation can be changed.
The risk of being disconnected from the stakeholders.
Which of the following are true about the length of the Sprint? (Choose two.)
The length of the Sprint should be proportional to the work that is done in between Sprints.
It is best to have Sprints of consistent length throughout a development effort.
Sprint length is determined during Sprint Planning, and should hold the time it will take to code the planned features in the upcoming Sprint, but does not include time for any testing.
Sprint length is determined during Sprint Planning, and should be long enough to make sure the Development Team can deliver what is to be accomplished in the upcoming Sprint.
All Sprints must be 1 month or less.
The CEO asks the Development Team to add a “very important” item to a Sprint that is in progress. What should the Development Team do?
Add the item to the current Sprint and drop an item of equal size.
Add the item to the current Sprint without any adjustments.
Inform the Product Owner so he/she can work with the CEO.
Add the item to the next Sprint.
The time-box for a Daily Scrum?
Two minutes per person.
15 minutes.
15 minutes for a 4 week sprint. For shorter Sprints it is usually shorter.
4 hours.
The same time of day every day.
Which phrase best describes a Product Owner?
Go-between development team and customers.
Value optimizer.
Requirements engineer.
Team manager.
During a Sprint Retrospective, for what is the Product Owner responsible?
Participating as a Scrum Team member.
Summarizing and reporting the discussions to the stakeholders that he/she represents in the Scrum Team.
Capturing requirements for the Product Backlog.
The Product Owner should not take part in Sprint Retrospectives.
Marian is the Product Owner envisioning a project for a new release of her product. She made a projection of a release date based upon a sustained velocity of 17 completed units of work per Sprint. Over the first 3 Sprints, the average velocity was 13 for work that the Development Team estimated as 90% done. The Development Teams, feeling the need to meet the plan, figured that a velocity of 17 was within their reach.
A good way to continue is:
The Development Team makes sure that all of the selected scope per Sprint is as “Done” as possible. The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn’t mess up the Product Backlog.
Add enough people to the Development Team for the deadline to be made.
The opportunity to inspect and adapt is lost. Opaqueness has replaced transparency. Predictability has dropped below zero. The produced software is not usable. As the rules of Scrum have not been respected, it is the Scrum Master’s duty to assess whether repair is possible, or a restart with a more reliable team. If not, the Scrum Master should cancel the project.
The Development Team should remind Marian to find funding for enough Release Sprints in which the remaining work can be done.
For the purpose of transparency, when does Scrum say a new increment of working software must be available?
After the acceptance testing phase.
Before the release Sprint.
Every 3 Sprints.
At the end of every Sprint.
When the Product Owner asks to create one.
Which two ways of creating Development Teams are consistent with Scrum’s values? (Choose two.)
Existing teams propose how they would like to go about organizing into the new structure.
Managers personally re-assign current subordinates to new teams.
Managers collaborate to assign individuals to specific teams.
Bring all the developers together and let them self-organize into Development Teams.
The Chief Product Owner determines the new team structures and assignments.
A Scrum Master is essentially the same thing as a traditional PM (Project Manager).
True
False
A Product Owner wants advice from the Scrum Master about estimating work in Scrum. Which of these is the guideline that a Scrum Master should give?
Product Backlog items must be estimated in story points.
Estimates are made by the Development Team.
Estimates must be in relative units.
Scrum forbids estimating.
Estimates are made by the Product Owner, but are best checked with the Development Team.
Which Scrum Value is affected by a lack of trust in the Scrum Team?
Focus
Respect
Openness
Courage
Commitment.
A product Increment must be released to production at the end of each Sprint.
True
False
How is management external to the Scrum Team involved in the Daily Scrum?
The Scrum Master speaks on their behalf.
The Development Team self-manages and is the only management required at the Daily Scrum.
Management gives an update at the start of each Daily Scrum.
The Product Owner represents their opinions.
What is the time-box for the Sprint Review?
As long as needed.
2 hours for a monthly Sprint.
4 hours for a monthly Sprint.
4 hours and longer as needed.
1 day
Who is responsible for tracking the remaining work of the Sprint?
The Development Team.
The Scrum Master.
The Project Manager.
The Development Team is consultation with the Product Owner.
The Product Owner.
Which of the following best describes an increment of working software?
A decomposition of all Product Backlog items into tasks for future Sprint Backlog lists.
Additional features in a usable state that complement those delivered in previous iterations.
A new user interface design for functionality delivered in previous iterations.
An automated test suite to verify functionality delivered in previous iterations.
UML diagrams that describe how to deliver functionality in future iterations.
The Product Owner determines how many Product Backlog items the Development Team selects for a Sprint.
False.
True, accordingly to what was committed to the stakeholders.
True, but only after confirmation by the resource manager that the Team has enough capacity.
True.
False, the Scrum Master does that.
Which three of the following are feedback loops in Scrum? (Choose three.)
Sprint Review.
Release Planning.
Sprint Retrospective
Refinement Meeting.
Daily Scrum.
Which of the following services are appropriate for a Scrum Master in regard to the Daily Scrum?
Lead the discussions of the Development Team.
Make sure that all 3 questions have been answered by each member of the team.
Keep track of whether each team member has a chance to speak.
Teach the Development Team to keep the Daily Scrum within the 15 minute time-box.
All of the above.
Which of the following might the Scrum Team discuss during a Sprint Retrospective?
Methods of communication.
The way the Scrum Team does Sprint Planning.
Skills needed to improve the Development Team’s ability to deliver.
Its Definition of “Done”.
All of the above.
You are the Scrum Master of a new, to-be-developed product. Development is going to require 45 people. What is a good first question for you to suggest the group thinks about when forming into teams?
How will we make sure all teams have the right amount or expertise?
What is the right mixture of senior and junior people on each team?
Who are going to be the team leads?
Who are the subject matter experts on each team?
Which two activities will a Product Owner engage in during a Sprint? (Choose two.)
Run the Daily Scrum.
Prioritize the Development Team’s work on the Sprint Backlog.
Update the Sprint burndown chart.
Answer questions from the Development Team about items in the current Sprint.
Work with the stakeholders.
Which three questions might be answered by Development Team members at the Daily Scrum? (Choose three.)
How is the Sprint proceeding?
What did I do yesterday that helped the Development Team meet the Sprint Goal?
Why were you late?
What will I do today to help the Development Team meet the Sprint Goal?
Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
Cross-functional teams are optimized to work on one technical layer of a system only (e.g. GUI, database, middle tier, interfaces).
True
False
A Scrum Master is working with a Development Team that has members in different physical locations. The Development Team meets in a variety of meeting rooms and has much to do logistically (for example, set up conference calls) before the Daily Scrum. What action should the Scrum Master take?
Allow the Development Team to self-manage and determine for itself what to do.
Set up the meeting and tell the Development Team that is how it will be done.
Ask the Development Team members to alternate who is responsible for meeting setup.
Inform management and ask them to solve it.
What are two good ways for a Scrum Team to ensure security concerns are satisfied? (Choose two.)
Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items.
Add security concerns to the definition of “Done”.
Add a Sprint to specifically resolve all security concerns.
Delegate the work to the concerned department.
Have the Scrum Team create Product Backlog items for each concern.
Which are the properties of the Daily Scrum? (Choose two.)
It is facilitated by the team lead.
It is held first thing in the morning.
It is fifteen minutes or less in duration.
It consists of the Scrum Master asking the Team members the three questions.
Its location and time remain constant.
Every Scrum team must have a Product Owner and Scrum Master.
True. Outcomes affected by their participation and availability.
False. A Product Owner can be replaced by a business analyst in the Development Team.
False. A Scrum Master is only required when asked for by the Development Team.
True. Each must be 100% dedicated to the Scrum Team.
The Sprint Goal is a result of Sprint Planning, as is the Sprint Backlog.
True
False
When should a Sprint Goal be created?
It should have been created in the previous Sprint during Product Backlog refinement.
It must be established before Sprint Planning in order to begin planning.
A Sprint Goal is not mandatory in Scrum.
At any time during the Sprint.
During Sprint Planning.
In accordance with Scrum theory, how should a group of 100 people be divided into multiple Development Teams?
Understanding the product, the product vision and the rules of the Scrum framework, the group divides itself into teams.
It doesn’t really matter because you can rotate the teams every Sprint to spread knowledge.
Check with the allocation department to see who has worked together before and make these the first teams.
Create a matrix of skills, seniority, and level of experience to assign people to teams.
A Sprint Retrospective should be held:
At the end of each Sprint.
At the beginning of each Sprint.
Only when the Scrum Team determines it needs one.
At the end of the last Sprint in a project or a release.
A new developer is having continuing conflicts with existing Development Team members and creating the hostile environment. If necessary, who is responsible for removing the team member?
The hiring manager is responsible because he/she hired the developer.
The Scrum Manager is responsible because he/she removes Impediments.
The Development Team is responsible and may need help from the Scrum Master.
The Product Owner is responsible because he/she controls the return on investment (ROI).
The Product Owner makes sure the team selects enough from the Product Backlog for a Sprint to satisfy the stakeholders.
True
False
Which statement best describes the Sprint Review?
It is used to congratulate the Development Team if it did what it forecast, or to punish the Development Team if it failed to meet its forecast.
It is a demo at the end of the Sprint for everyone in the organization to check on the work done.
It is a mechanism to control the Development Team’s activities during a Sprint.
It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.
Who owns the Sprint Backlog?
The Scrum Team.
The Product Owner.
The Scrum Master.
The Development Team.
Every Development Team should have:
At least one representative from each major software engineering discipline (like QA, Dev, UX).
The competencies and skills needed to deliver a Done Increment in a Sprint.
One Lead Developer and no more than 8 other members.
Why does the Product Owner want the Development Team to adhere to its definition of “Done”?
To have complete transparency into what has been done at the end of each Sprint.
To be able to reprimand the team when they don’t meet their velocity goal for the Sprint.
To know what the team will deliver over the next three Sprints.
To predict the team’s productivity over time.
The Development Team should have all the skills needed to:
Turn Product Backlog items into an Increment of potentially releasable product functionality.
Do all of the development work, except for specialized testing that requires additional tools and environments.
Complete the project within the date and cost as calculated by the Product Owner.
Which two things are appropriate for a Scrum Master to do if the Development Team doesn’t have the engineering tools and infrastructure to completely finish each selected Product Backlog item? (Choose two.)
Coach the Development Team to improve its skills, tools, and infrastructure over time and adjust the Definition of “Done” accordingly.
Encourage the Product Owner to accept partially “Done” increments until the situation improves.
Refocus the current Sprint on establishing the Development Team’s infrastructure instead of delivering an increment.
Declare the Development Team not ready for Scrum
Have the Development Team establish a Definition of “Done” that is actually possible to achieve given current circumstances.
When is implementation of a Product Backlog item considered complete?
At the end of the Sprint.
When the item has no work remaining in order to be potentially released.
When QA reports that the item passes all acceptance criteria.
When all work in the Sprint Backlog related to the item is finished.
Choose two responsibilities of a self-organizing Development Team. (Choose two.)
Reorder the Product Backlog.
Pull Product Backlog items for the Sprint.
Do the work planned in the Sprint Backlog.
Increase velocity.
Report daily progress to stakeholders.
A Scrum Master is introducing Scrum to a new Development Team. The Development Team has decided that a Sprint Retrospective is unnecessary. What action should the Scrum Master take?
Call a meeting between the Development Team and senior management.
Comply with the decision of the self-organizing team.
Consult with the Product Owner to see how he/she feels about the situation.
Begin facilitating productive and useful Sprint Retrospectives.
When does the second Sprint start?
Once the architectural changes for the second Sprint have been approved by the senior architect.
After the Product Backlog for the second Sprint has been selected.
Immediately after the first Sprint.
After the customer completes acceptance testing of the first Sprint.
What is included in the Sprint Backlog?
User Stories.
Tasks.
Use Cases.
Tests.
Any of the above (or others) which are a decomposition of the selected Product Backlog items.
Why should the Product Owner be present at the Daily Scrum?
He/She doesn’t need to be there.
To hear about impediments in functionality.
To represent the stakeholders’ point of view.
To participate as a Scrum Team member.
What two techniques could the Scrum Master use when the Scrum Team gets caught in an internal disagreement about which development techniques to apply?
(Choose two.)
Involve the complete Development Team.
Use coaching techniques; such as open questions and active listening.
Ask an external technical specialist to make the decision.
Send every team member to the company’s HR department to express their concerns.
Who is responsible for clearly expressing Product Backlog items?
The Scrum Master, or the Scrum Master may have the Development Team do it.
The Scrum Master.
The Product Owner.
The business analyst who represents the Product Owner in the Development Team.
What are three benefits of self-organization? (Choose three.)
Increased creativity.
Increased rule compliance.
Increased accuracy of estimates.
Increased self-accountability
Increased commitment.
If burndown charts are used to visualize progress, what does a trend line through a release burndown chart indicate?
The evolution of the cost spent on the project.
When all work will be completed to the Scrum Team can be released for other work.
When the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team.
When the project will be over if the Product Owner removes work that is equal in effort to any new work that is added.
Who is responsible for engaging the stakeholders?
The Business Analyst.
The Development Team.
The Team Manager.
The Project Manager.
The Product Owner.
How much work must a Development Team do to a Product Backlog item it selects for a Sprint?
A.
A proportional amount of time on analysis, design, programming, testing, and documentation
As much as it can fit into the Sprint. Any remaining work will be transferred to a subsequent Sprint.
All development work and at least some testing.
As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of “Done”.
Which statement best describes the Sprint Backlog as outcome of the Sprint Planning?
It is a complete list of all work to be done in a Sprint.
Every item has a designated owner.
Each task is estimated in hours.
It is the Development Team's plan for the Sprint.
It is ordered by the Product Owner.
Sprint burndown charts are an efficient tracking tool, because they show:
An estimate of the total work remaining for the Sprint.
How much effort has gone into a Sprint.
How many hours have been worked by each Development Team member.
How many Product Backlog items remain.
User documentation is part of your definition of “Done”. However, there aren't enough technical writers for all teams. Your Development Team doesn't have a technical writer. What should you do?
Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.
Let the user documentation remain undone and accumulate until after the last development Sprint. It will then be done by any available technical writers.
Wait until you have a technical writer on your Development Team to take care of this.
Your Development Team is still responsible for creating user documentation. In this case, the Development Team members will write it.
You have just been hired by a company new to Scrum. Your management has assigned you to be the Scrum Master of six new Scrum Teams. These teams will build one product. Select two conditions you should strive for in this scenario. (Choose two.)
There should be six Product Owners, one for each Scrum Team.
There should be six Product Owners, reporting to a chief Product Owner.
The product has one Product Backlog.
Each Scrum Team should have a separate Product Backlog.
There should be only one Product Owner.
A Scrum Team has been working on a product for nine Sprints. A new Product Owner comes in, understanding he is accountable for the Product Backlog.
However, he is unsure about his responsibilities. Which two activities are part of the Product Owner role according to Scrum? (Choose two.)
Ensuring that the most valuable functionality is produced first, at all times.
Interacting with stakeholders.
Providing the Development Team with detailed specifications.
Describing features as Use Cases.
Creating detailed functional test cases.
Who is on the Scrum Team? (Choose all that apply.)
Scrum Master
Product Owner
Development Team member
Project Manager
None of the above
A Scrum Team is only allowed to meet with stakeholders during Sprint Review.
True
False
Which best describes the Product Backlog?
It is allowed to grow and change as more is learned about the product and its customers.
It provides just enough information to enable a Scrum team to start the design phase of a product.
It contains all foreseeable tasks and requirements from which the Scrum team can develop and maintain a complete project plan
It is baselined to follow change management processes.
How should a Development Team deal with non-functional requirements?
Ensure every Increment meets them.
Make sure the release department understands these requirements, but it is not the Development Team’s responsibility.
Handle them during the Integration Sprint preceding the Release Sprint.
Assign them to the lead developers on the team.
In the Sprint Planning meeting, the Product Owner and the Development Team were unable to reach a clear understanding about the highest order Product Backlog items. Because of this, the Development Team couldn’t figure out how many Product Backlog items it could forecast for the upcoming Sprint. They were able to agree on a Sprint Goal, however.
Which of the following two actions should the Scrum Master support? (Choose two.)
Cancel the Sprint. Send the entire team to an advanced Scrum training and then start a new Sprint.
Forecast the most likely Product Backlog items to meet the goal and create a Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint.
Continue the Sprint Planning meeting past its time-box until an adequate number of Product Backlog items are well enough understood for the Development Team to make a complete forecast. Then start the Sprint.
Discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.
Ask everyone to take as much time as needed to analyze the Product Backlog first, and then reconvene another Sprint Planning meeting.
Which of the following is required by Scrum? (Choose all that apply.)
Sprint Retrospective.
Members must be stand up at the Daily Scrum.
Sprint Burndown Chart.
Release planning.
All of the above.
When do Development Team members take ownership of a Sprint Backlog item?
At the Sprint planning meeting.
During the Daily Scrum.
Never. All Sprint Backlog Items are “owned” by the entire Development Team, even though each one may be done by an individual Development Team member.
Whenever a team member can accommodate more work.
Which two things should the Development Team do during the first Sprint? (Choose two.)
Make up a plan for the rest of the project.
Analyze, describe, and document the requirements for the subsequent Sprints.
Develop at least one piece of functionality.
Analyze, design, and describe the complete architecture and infrastructure.
Create an increment of potentially releasable software.
For which is the Scrum Master responsible?
Managing the performance of the Scrum Team.
The meetings and the objectives that a Scrum Team sets for itself.
The Scrum framework being adopted and used properly.
Keeping track of resource allocation.
As the Sprint Planning meeting progresses, the Development Team sees that the workload is greater than they can handle. Which two are valid actions? (Choose two.)
Recruit additional Development Team members before the work can begin.
The Development Team ensures that the Product Owner is aware, starts the Sprint, and monitors progress
Cancel the Sprint.
Remove or change selected Product Backlog items.
The Development Team works overtime during this Sprint.
Currently, your Development Teams are organized to address a single layer only (for example, front end, middle tier, back end, and interfaces). What are three things to consider when deciding to move away from such component teams toward feature teams? (Choose three.)
You cannot do Scrum without feature teams.
Productivity may suffer when making this kind of move.
Getting support from the business side first helps.
Feature teams have less communication overhead.
With feature teams, it is easier to calculate the productivity per team.
How often should Development Team membership change?
As needed, while taking into account a short term reduction in productivity.
Never, because it reduces productivity.
As needed, with no special allowance for changes in productivity.
Every Sprint to promote shared learning.
The Daily Scrum is an event that happens every day. What would be three key concerns if the frequency were to be lowered to every two or three days? (Choose three.)
Opportunities to insect and adapt the Sprint Backlog are lost.
Impediments are raised and resolved more slowly.
The Product Owner cannot accurately report progress to the stakeholders.
Too much work is spent updating the Scrum board before the meeting.
The Sprint plan may become inaccurate.
A Development Team selects a set of Product Backlog items for a Sprint Backlog with the intent to get the selected items “Done” by the end of the Sprint. Which three phrases best describe the purpose of a definition of “Done”? (Choose three.)
It controls whether the developers have performed their tasks.
It provides a template for elements that need to be included in the technical documentation.
It creates transparency over the work inspected at the Sprint Review.
It trucks the percent completeness of a Product Backlog item.
It defines what it takes for an Increment to be ready for release.
Select two ways in which technical debt impacts transparency. (Choose two.)
When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.
It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint.
As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways.
It enhances transparency for the Product Owner as a Development Team is not allowed to do additional feature development in a Sprint as long as there is technical debt.
A Development Team is required to deliver a done Increment by the end of a Sprint. Select two statements that explain what “Done” means. (Choose two.)
All work the Development Team is willing to do.
Ready for integration.
No work left from the definition of “Done”.
Whatever the Product Owner defines as quality.
All work to create software that is ready to be released to end users.
What two factors are best considered when establishing the Sprint length? (Choose two.)
The organization has mandated similar length sprints.
The level of uncertainty over the technology to be used.
The frequency at which team formation can be changed.
The risk of being disconnected from the stakeholders.
Which of the following are true about the length of the Sprint? (Choose two.)
The length of the Sprint should be proportional to the work that is done in between Sprints.
It is best to have Sprints of consistent length throughout a development effort.
Sprint length is determined during Sprint Planning, and should hold the time it will take to code the planned features in the upcoming Sprint, but does not include time for any testing.
Sprint length is determined during Sprint Planning, and should be long enough to make sure the Development Team can deliver what is to be accomplished in the upcoming Sprint.
All Sprints must be 1 month or less.
Which two ways of creating Development Teams are consistent with Scrum’s values? (Choose two.)
Existing teams propose how they would like to go about organizing into the new structure.
Managers personally re-assign current subordinates to new teams.
Managers collaborate to assign individuals to specific teams.
Bring all the developers together and let them self-organize into Development Teams.
The Chief Product Owner determines the new team structures and assignments.
How is management external to the Scrum Team involved in the Daily Scrum?
The Scrum Master speaks on their behalf.
The Development Team self-manages and is the only management required at the Daily Scrum.
Management gives an update at the start of each Daily Scrum.
The Product Owner represents their opinions.
Which of the following best describes an increment of working software?
A decomposition of all Product Backlog items into tasks for future Sprint Backlog lists.
Additional features in a usable state that complement those delivered in previous iterations.
A new user interface design for functionality delivered in previous iterations.
An automated test suite to verify functionality delivered in previous iterations.
UML diagrams that describe how to deliver functionality in future iterations.
Which three of the following are feedback loops in Scrum? (Choose three.)
Sprint Review.
Release Planning.
Sprint Retrospective
Refinement Meeting.
Daily Scrum.
Which two activities will a Product Owner engage in during a Sprint? (Choose two.)
Run the Daily Scrum.
Prioritize the Development Team’s work on the Sprint Backlog.
Update the Sprint burndown chart.
Answer questions from the Development Team about items in the current Sprint.
Work with the stakeholders.
Cross-functional teams are optimized to work on one technical layer of a system only (e.g. GUI, database, middle tier, interfaces).
True
False
Which are properties of the Daily Scrum? (Choose two.)
It is facilitated by the team lead.
It is held first thing in the morning.
It is fifteen minutes or less in duration.
It consists of the Scrum Master asking the Team members the three questions.
Its location and time remain constant.
When should a Sprint Goal be created?
It should have been created in the previous Sprint during Product Backlog refinement.
It must be established before Sprint Planning in order to begin planning.
A Sprint Goal is not mandatory in Scrum.
At any time during the Sprint.
During Sprint Planning.
When is the implementation of a Product Backlog item considered complete?
At the end of the Sprint.
When the item has no work remaining in order to be potentially released
When QA reports that the item passes all acceptance criteria.
When all work in the Sprint Backlog related to the item is finished.
What two techniques could the Scrum Master use when the Scrum Team gets caught in an internal disagreement about which development techniques to apply?
(Choose two.)
Involve the complete Development Team.
Use coaching techniques; such as open questions and active listening.
Ask an external technical specialist to make the decision.
Send every team member to the company’s HR department to express their concerns.
If burndown charts are used to visualize progress, what does a trend line through a release burndown chart indicate?
The evolution of the cost spent on the project.
When all work will be completed to the Scrum Team can be released for other work.
When the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team.
When the project will be over if the Product Owner removes work that is equal in effort to any new work that is added.
Sprint burndown charts are an efficient tracking tool, because they show:
An estimate of the total work remaining for the Sprint.
How much effort has gone into a Sprint.
How many hours have been worked by each Development Team member.
How many Product Backlog items remain.
You have six teams using a traditional method to deliver a product. Your management has asked you to start using Scrum. In the initial project there were separate plans and teams for the layers of a software system, i.e. one for the front-end, one for the middle tier, one for the back-end, and one for the interfaces and services.
This resembles what is known as component teams. But you have read that it’s a good idea to have teams organized by feature.
What are the advantages of keeping component teams while starting Scrum?
There’s less initial disruption than organizing into new teams. As they start, they will discover what works best, and how to potentially re-organize towards this.
Component teams generally have the skills needed to create a working Increment of software that provides business value.
Because they have worked together for some time, they are likely able to start producing shippable Increments faster that new feature teams would.
There are fewer cross-team dependencies than working in feature teams.
How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?
The Scrum Team with the highest velocity pulls Product Backlog items first.
The Development Teams pull in work in agreement with the Product Owner.
The Product Owner should provide each team with its own Product Backlog.
Each Scrum Team takes an equal numbers of items.
The Product Owner decides.
How often should Development Team membership change?
As needed, while taking into account a short term reduction in productivity.
Never, because it reduces productivity.
As needed, with no special allowance for changes in productivity.
Every Sprint to promote shared learning.
A Scrum Master is keeping a list of open impediments, but it is growing and he/she has been able to resolve only a small portion of the impediments. Which three techniques would be most helpful in this situation? (Choose three.)
Consulting with the Development Team.
Prioritizing the list and working on them in order.
Arranging a triage meeting with all project managers.
Alerting management to the impediments and their impact.
To get started in terms of what to build, Scrum requires no more than a Product Owner with enough ideas for a first Sprint, a Development Team to implement those ideas and a Scrum Master to help guide the process.
True
False
The Sprint Review is mainly an inspect and adapt opportunity for which group?
The Development Team and stakeholders.
The Product Owner and Development Team.
The Scrum Team and stakeholders.
The Product Owner and management.
The Product Owner and stakeholders.
In order to achieve the benefits of Scrum, it is important to enact the value of commitment. What two actions demonstrate the commitment of Scrum Team members? (Choose the best two answers.)
Always deliver the items in the Sprint forecast.
Help the other Scrum Team members.
Do your best
Send out a daily status report.
Work late.
When a Development Team is having trouble delivering a working Increment because they don’t understand a functional requirement, what should they do?
(Choose the best answer.)
Add a specialist to the Development Team.
Partially complete the functionality, and discuss the remaining work at the Sprint Review.
Collaborate with the Product Owner to determine what is possible and acceptable.
the work to a more appropriate Sprint
Which two of the following are appropriate topics for discussion during a Sprint Retrospective? (Choose the best two answers.)
Identifying high priority process improvements for the next Sprint.
The order of items in the Product Backlog.
How the team collaborates.
Documenting acceptance criteria for items in the next Sprint.
