Question 81: Project managers and functional managers need to be able to recognize a condition that is best suited for a project and a condition that is an operation within an entity. Which one of the following is an example of operations?
A. Creating a new community park
B. Designing a new car
C. Sending monthly invoices to an organization’s 25,000 customers
D. Removing an old server and replacing it with a newer one
Correct Answer: C. Sending monthly invoices to an organization’s 25,000 customers
Explanation: This is the best example of operations because the answer implies that this work is done every month. The other three options are all unique endeavors that may be done once or just occasionally, but they are not part of ongoing operations.
Question 82: When considering the selection of projects to be initiated, project portfolio management considers all of the following except for which one?
A. Risk/reward categories
B. Lines of business
C. The project manager’s experience
D. General types of projects
Correct Answer: C. The project manager’s experience
Explanation: While the experience of the project manager is likely considered during the assignment of projects, it is not considered during project portfolio management. The first option, the risk and reward of the project, is considered. The other two options, the lines of business and the general types of projects, are also considered as part of project portfolio management.
Question 83: What should teams do before Agile sprint planning and execution?
A. Find a large enough collaboration space
B, Compile a list of necessary QA and dev tools
C. Gather software requirements
D. Host a company-wide air hockey tournament
Correct Answer: C. Gather software requirements
Explanation: An organization must establish what functionalities and features its end users want from the software development project. Without knowledge of the requirements that Agile teams must meet, it’s difficult — if not impossible — to plan out their work. Don’t put the cart before the horse.
Question 84: What topic falls outside the scope of a well-run daily stand-up meeting?
A. Recently completed tasks
B. Current obstacles
C. Planning out an iteration or sprint
D. What everyone will work on today
Correct Answer: C. Planning out an iteration or sprint
Explanation: A daily stand-up meeting typically takes no longer than 15 minutes, much too short to plan out an Agile sprint or iteration. Take more time to plan out sprints and gather software requirements — and do that work before the actual iteration or sprint. Limit the scope of daily stand-up meetings to imminent or recent items, such as recently completed tasks, current obstacles and ongoing work.
Question 85: What must the team discuss in a sprint planning meeting?
A. When and how they will deliver backlog items
B. Whether this or an alternative project would deliver more business value
C. Who will be the Scrum master
D. Who on the development team will be on-call during weekends
Correct Answer: A. When and how they will deliver backlog items
Explanation: Before any sprint, an Agile team determines what work will get done and how. At the end of sprint planning, teams should have a clear understanding of the scope of the next iteration and the yardsticks that will gauge work in progress. The Scrum master, who facilitates teamwork and communication throughout the project, requires training and certification. This role shouldn’t be left up to chance, or a group decision during sprint planning.
Question 86: Which of the following options is not part of an Agile software development framework or model?
A. Kanban
B. Extreme Programming
C. Feature-driven development
D. Spiral
Correct Answer: D. Spiral
Explanation: While Spiral is an incremental software development model, it is not considered Agile. Spiral involves planning out a whole project in larger chunks that can take several months to complete — far longer than a typical weeks- or month-long Agile iteration. Spiral more closely resembles Waterfall software development methodologies than Agile. Kanban, defined by its use of visuals on a Kanban board, is an Agile framework and a methodology used for manufacturing and other business. Extreme Programming is another Agile model that heavily stresses communication and simplicity. Lastly, feature-driven development is an Agile process that prioritizes feature delivery to customers.
Question 87: What primarily distinguishes Scrum from its superset Agile?
A. An iterative and incremental development approach
B. A flexibility to constantly changing software requirements
C. Post-release review meetings
D. A set of predetermined roles
Correct Answer: D. A set of predetermined roles
Explanation: A Scrum team calls for three fixed roles: the Scrum master, the product owner and the development team. A post-release review meeting, the need to respond to changing software requirements and an iterative approach are not unique to Scrum. While Scrum outlines roles and responsibilities, it’s not a methodology like Agile; it’s a framework. Accordingly, Scrum can help teams be Agile and observe its principles, and still be its own concept.
Question 88: Which set of priorities below is the opposite of the ideals put forth in the Agile Manifesto?
A. Processes and tools over individuals and interactions
B. Working software over comprehensive documentation
C. Customer collaboration over contract negotiation
D. Responding to change over following a plan
Correct Answer: A. Processes and tools over individuals and interactions
Explanation: The Agile Manifesto prioritizes individuals and interactions over processes and tools. Agile teams should let people, not processes and tools, steer development projects. The manifesto includes these four core statements about empowered individuals, working software, customer collaboration and change, as well as 12 principles related to how Agile teams work together and with their customers.
Question 89: Which of these Agile terms is paired with its correct definition?
A. User personas: a summary of a feature from the user’s perspective
B. Use cases: a characterization of your intended end user
C. User stories: documentation of user paths through an app
D. Acceptance criteria: what needs to be done for a user story to be achieved
Correct Answer: D. Acceptance criteria: what needs to be done for a user story to be achieved
Explanation: Acceptance criteria is the only correct definition. User personas are a characterization of your project’s intended end user. Use cases document user paths through an app. User stories summarize a feature from the user’s perspective.
Question 90: Which metric is relevant to Agile software development?
A. Throughput
B. Lead time
C. Cycle time
D. All of the above
Correct Answer: D. All of the above
Explanation: All these measurements could prove useful to Agile teams as key performance indicators. Throughput measures the amount of work a system can handle within a certain amount of time. Cycle time specifies the time that elapses between when work begins on an item and when that task is complete. Lead time is a metric from the end user’s perspective that gauges the amount of time between when a user requests something and when it is received.
