×

Quiz Session - Attempts With Random Questions

PMI-ACP Exam Questions

Page 9 of 25

161.

Which of the following is not included on the left side of the Agile Manifesto values? 

  • Collective code ownership 

  • Responding to change 

  • Customer collaboration 

  • Individuals over interactions 

Correct answer: Collective code ownership 

The four values of the Agile Manifesto represent the left side of the statement more than the right. The only statement that is not included in these four values is collective code ownership, which is an XP core practice.

162.

A Scrum team is meeting for their first daily stand-up. As one of the developers is providing his inputs during the session, the Project Sponsor who is sitting in the room interrupts to ask more detailed questions about his update. What is an observation that can be made about this scenario?

  • Only those who have tasks can talk during a daily stand-up.

  • The Scrum Master is the only one that should be asking the questions in the daily stand-up.

  • The daily stand-up is a great setting to solve problems that arise in the sprint.

  • The daily stand-up should focus on solving specific problems rather than asking open-ended questions.

Correct answer: Only those who have tasks can talk during a daily stand-up.

A daily stand-up is a daily meeting held by the development team to review three main questions:

  1. What did you do yesterday?
  2. What will you do today?
  3. Anything blocking your progress?

The main ground rules for daily stand-ups are:

  • If you have a task, you must attend.
  • Only those who have tasks can talk.
  • Speak to the team, not the coach or Scrum Master.
  • No side conversations.
  • Create a new sticky note for each new task that is started.
  • Discuss issues after the meeting.
  • Solve problems off-line.

In this scenario, the Project Sponsor does not have tasks in the sprint. Thus, he should not ask questions of the team. Anyone can be part of the session, but if they do not have a task in iteration they cannot speak, per the ground rules.

163.

An Agile team is just getting started building its first prototype. During the sprint planning meeting for the third sprint, one of the developers mentions that end-to-end documentation of the current deliverable is needed to make sure new developers know where the team stands in the progress. He advocates for adding this task into the upcoming sprint, replacing other features that had already been selected. What value from the Agile Manifesto is the developer's request reflected in?

  • Working software over comprehensive documentation

  • Individuals and interactions over processes and tools

  • Customer collaboration over contract negotiation

  • Responding to change over following a plan

Correct answer: Working software over comprehensive documentation

The developer is advocating for the right side of the Agile Manifesto value “Working software over comprehensive documentation.” The product is deemed to continue to change since only two sprints have been completed. Creating documentation at this point does not add value to the customer.

This Agile Manifesto value does not mean that you should not create documentation; it means you should create documentation that provides value and at the same time does not hinder the team’s progress.

In this example, the developer is choosing to deliver the second sprint and move the documentation into the third sprint rather than complete it now.

164.

What Scrum artifacts are created in each sprint?

  • The product increment

  • The product backlog

  • The daily standup

  • The groomed backlog

Correct answer: The product increment

There are three Scrum artifacts: product backlog, sprint backlog, and product increment. At the end of each sprint, the development team builds an increment of the solution based on the sprint backlog.

165.

An Agile project manager is building a chart by plotting the total risk identified for the project and how the team is dealing with that risk over the eight completed sprints. The chart shows the risk exposure starting at its maximum point on the left of the chart and progressively decreasing as the eight iterations are plotted. 

What is the name of this chart?

  • Risk burndown chart

  • Risk-adjusted backlog

  • Control chart 

  • Fishbone diagram

Correct answer: Risk burndown chart

A risk burndown chart is a graphical representation of the total risk work addressed and the remaining risk to be addressed by the team.

"Risk-adjusted backlog" refers to a prioritized list of features or requirements that have been adjusted based on their risk level. It is not a chart used to track risk exposure over time.

A control chart helps identify when a process follows set specifications or needs to be adjusted due to non-random events to perform optimally.

A fishbone diagram is a visual depiction of cause and effect.

166.

What are the four stages of the Framework for Integrated Testing (FIT), or FitNesse, in relation to acceptance testing?

  • Discuss, distill, develop, demo

  • Detail, discuss, demonstrate, delete

  • Demo, discern, develop, dilute

  • Discuss, discern, develop, delete

Correct answer: Discuss, distill, develop, demo

The four stages of the Framework for Integrated Testing (FIT), or FitNesse, are: discuss, distill, develop, and demo.

167.

Which of the following is not an example of an empirical process? 

  • Identifying weaker team members for removal 

  • Experimenting to determine what works 

  • Learning from mistakes 

  • Analyzing root cause of any failing results 

Correct answer: Identifying weaker team members for removal 

Empirical processes, by nature, are based on trial and error and experimentation. This allows us to learn from failures fast and identify why something failed in the first place. All options are examples of empirical processes except identifying weaker team members for removal.

168.

Which of the following is not one of the emotional intelligence quadrants?

  • Personal skills

  • Self-awareness

  • Self-management

  • Social awareness

Correct answer: Personal skills

Emotional intelligence is the ability to assess, identify, and influence the emotions we have, and those that others have around us. The emotional intelligence model is divided into the vertical axis (regulate/recognize) and the horizontal axis (self/others). This leads to four quadrants, which are self-management, self-awareness, social skills, and social awareness. 

"Personal skills" is not a valid quadrant in the emotional intelligence model.

169.

What is not a characteristic of high-performing Agile teams?

  • Agile teams are empowered to decide what user stories go in the next iteration.

  • Agile teams have a team identity to be committed to success.

  • Agile team members trust one another.

  • Agile teams own their decisions.

Correct answer: Agile teams are empowered to decide what user stories go in the next iteration.

There are eight characteristics of high-performing Agile teams:

  1. Agile teams are self-organizing.
  2. Agile teams are empowered to make their own decisions.
  3. Agile teams own their decisions.
  4. Agile teams have the mindset that they can solve any problem.
  5. Agile teams have a team identity to be committed to success.
  6. Agile team members trust one another.
  7. Agile teams communicate and aim for group consensus.
  8. Agile teams know that conflict is natural, but constructive feedback is needed.

Thus, Agile teams do not decide what user stories to include in the next iteration by themselves. The Product Owner will prioritize the user stories based on customer value in the product backlog and select the top ones to work on in the next iteration. During the sprint Planning meeting, the Product Owner, the Development team, and the Scrum Master will discuss this subset and determine whether to include them in the next iteration based on the level of effort.

170.

A feature is being considered for inclusion into the product backlog. This feature will cost $2,000 to develop. It will provide a payback of $200 per week for four weeks after its release. It will also provide a one-time savings of $5,000 once it passes regulatory compliance approval a month after the release. 

What is the true value of this feature using value-based analysis?

  • $3,800

  • $4,000

  • $100

  • $2,800

Correct answer: $3,800

Value-based analysis is the process of assessing and prioritizing the business value of work items. For analyzing the business value of work items, we need to consider not only the business value we are gaining but also any development costs. Then, we can calculate business value using value-based analysis as follows:

The feature brings positive value:

$200 * 4 = $800 for four weeks

$5,000 one-time savings

Total payback value: $5,800 over one month after its release

Development costs are $2,000

Total value for this feature: $5,800 - $2,000 = $3,800

171.

An Agile project manager has collected data on the past two iterations including how long value and nonvalue-added activities take as part of the process. She wants to analyze how to improve the process in future iterations. What is the best technique she can use for this purpose, given the input information?

  • Value stream mapping

  • Process tailoring

  • Fishbone diagram

  • Control chart

Correct answer: Value stream mapping

Value stream mapping is a technique to eliminate wasteful work to reduce the time it takes to create value for the customer. The objective is to reduce total cycle time by looking at process efficiency over an iteration using process cycle efficiency as a key metric. Process cycle efficiency is calculated by dividing value-added time by the total cycle time in the iteration.

A control chart helps identify when a process follows set specifications or needs to be adjusted due to non-random events, to perform optimally.

Process tailoring refers to changing and adapting the implementation of Agile, based on the project needs.

A Fishbone diagram is a visual diagram for root cause analysis.

172.

An Agile team pulls features to work on based on the team members' capacity. The team members display their progress on a task board and move the progression of their work from left to right on the board. What Agile project life cycle is being used in this situation? 

  • Flow-based Agile life cycle 

  • Iteration-based Agile life cycle 

  • Hybrid life cycle 

  • Predictive life cycle 

Correct answer: Flow-based Agile life cycle 

There are two Agile project life cycles: iteration and flow-based. Flow-based Agile relies on the team pulling work based on its capacity and moving its progress on a workflow task board until done. The iteration-based Agile life cycle uses iterations to deliver increments. A predictive life cycle is a serialized way of performing a project where requirements are all gathered at the beginning and the output is not obtained until the end of the project. A hybrid life cycle combines iterative, predictive, incremental, and/or Agile approaches.

173.

An Agile team performed an initial risk assessment before the execution of the first sprint a few months ago. It was observed that an unintended event may occur as a result of mitigating one of the initial risks identified in the initial risk assessment. What is this event called?

  • Secondary risk

  • Issue 

  • Threat   

  • Mitigation

Correct answer: Secondary risk

A secondary risk takes place when you address a risk but the solution creates one or more new risks inadvertently. In this scenario, an unintended event that may occur that is created as a result of a resolved risk is a secondary risk.

An issue is a risk event that has taken place.

A threat is a type of risk that is identified before it occurs in a project and that has negative consequences for the project if it was to materialize.

A mitigation is an action taken to reduce the effects of a risk event.

174.

What is a benefit of keeping stakeholders engaged throughout the project? 

  • Identify potential risks and change requests as early as possible

  • Share project information radiators to keep expectations under control

  • Identify resources to add to upcoming sprints

  • Learn who is resistant to Agile methods, so they can be educated

Correct answer: Identify potential risks and change requests as early as possible

Keeping stakeholders engaged from the beginning to the end of the project is a good idea because it helps identify potential risks and change requests that may arise. This helps adjust the team’s work and prioritize the backlog as needed to avoid rework down the road.

None of the other options are a benefit of keeping stakeholders engaged in the project.

175.

A features chart used in an Agile project shows:

  • the number of features remaining and the number of features completed.

  • the number of features added to the backlog and the number of features to be added in the future.

  • the number of features completed against the project number of features to complete.

  • the number of features rejected against the number of features accepted.

Correct answer: the number of features remaining and the number of features completed.

A features chart is a combination of burnup and burndown charts. Effectively, it shows the number of features remaining and the number of features completed. It could also include the total number of features over time.

176.

A team is using a chart to the work completed to date for the last five sprints. The y-axis shows the scope of work completed in units of story points and the x-axis shows time. The curve is going up towards the right steeply, but goes flat in certain areas. What is true about this plotted curve? 

  • The gradient of the curve shows the team’s velocity at each sprint.

  • Where the curve goes flat, the team was blocked from proceeding.

  • Where the curve is vertical, the team is idle.

  • Scope was added where the curve goes vertical.

Correct answer: The gradient of the curve shows the team’s velocity at each sprint.

A plot of story points completed (features built) against time (sprints completed) shows how much work got done in each sprint to date. The gradient of the curve (y-axis over x-axis) will then show the team’s velocity. The team velocity measures the units of work completed in a given timeframe.

Where the curve goes flat, the team’s progress was slow. Where the curve goes steep, the team accomplished a lot of story points quickly. It is not possible to know from this curve, as described, when scope was added.

177.

Laurie just joined an Agile project management team in her organization. She observes that the team has adopted a few practices that distinguish them from other teams, such as individual code ownership and domain object modeling. 

What kind of Agile method is being used in Laurie’s project?

  • FDD

  • Lean product development

  • XP

  • DSDM

Correct answer: FDD

Feature-driven development (FDD) is initiated by developing an overall model using domain object modeling. It also uses individual code ownership, an approach that advocates having a single owner for parts of the code to maintain integrity and consistency, contrary to XP where the code is collectively owned and DSDM where the business need and business case drive development.

178.

During the iteration meeting, a user story was found to be too large for execution. It will need to be resized to a smaller size. Who on the Agile team is likely to be in the best position to slice the story in preparation for execution?

  • Development team

  • Scrum master

  • Value management team

  • Customer

Correct answer: Development team

User stories may be resized into smaller chunks during iteration planning. Those who will execute the work are in the best position to divide the story in preparation to execute the work. It is the development team who will do this. However, it is the customer or value management team who will prioritize it.

The Scrum master is responsible for facilitating the Agile process and ensuring that the team is following the Agile principles and practices.

The value management team is responsible for ensuring that the project is delivering value to the stakeholders. They provide input on the user story and its prioritization, but they are not directly responsible for slicing the story.

The customer is responsible for providing input on the user story and its requirements.

179.

After a product is successfully delivered, what is the best way for business users to verify the usability of the product and ensure the definition of done and acceptance criteria are met?

  • Acceptance Test-Driven Development 

  • Test-Driven Development

  • Continuous Integration

  • Exploratory and Usability Testing

Correct answer: Acceptance Test-Driven Development 

Acceptance test-driven development allows the development team to pull the business user and validate system usability against the original user story card.

Test-driven development is more relevant the the functionality of the product VS the usability of the product.

Continuous integration in the context of verifying and delivering value is mostly relevant to finding development and deployment errors while building code.

Exploratory and usability testing are mainly used by the team and their ability to try different ways that the system can be bent and additional functionality can be tested.

180.

A team is finalizing story maps after a series of workshops. They approach the Scrum master to ask where they should store the maps. The Scrum master asks them to post the maps on the walls for everyone to see. 

What are the story maps an example of in this scenario?

  • Information radiators

  • Participatory decision models

  • Reporting

  • User story workshops

Correct answer: Information radiators

Information radiators are artifacts created in an Agile project that are displayed openly. The information displayed could be from any part of the project, including retrospective findings, story maps, burndown charts, burnup charts, etc. In this scenario, since the story maps are being displayed openly to inform others of the work in the Agile project, the story maps are information radiators.

Participatory decision models are used to encourage teams to stay engaged and motivated by making decisions within the projects. These models have no specific action in storing project artifacts.

Reporting tools are used to provide project status and project health data. Reporting is not used to store story maps.

User Story workshops were completed as indicated in the original question. Therefore, these workshops are more about discovering rather than storing abilities for story maps.

×