PMI-ACP : PMI Agile Certified Practitioner : Part 04

  1. The key elements of a user story in Agile development are:

    • a written description, the story points estimate, and the planned release.
    • conversations about the story, a written description, and success criteria about the story.
    • the story points estimate, conversations about the story, and an agreed priority.
    • tests to determine when the story is done, a written description, and the planned release.
  2. In Agile risk management, a risk burndown chart is best used to:

    • Qualitatively analyze the probability of a risk occurring.
    • Track progress on risk reduction of technical risks.
    • Document the external risks that could impact the project.
    • Illustrate the project risk profile and new and changing risks.
  3. In a vision meeting, the vision for the project is defined and presented by the:

    • management
    • project manager
    • customer
    • project team
  4. In the Lean process, the focus is on:

    • Managing team efficiency.
    • Optimizing completed work across the process stream.
    • Using the optimal resources.
    • Cross training the team to eliminate bottlenecks.
  5. What is the common communication bridge between the team and the Product Owner?

    • Burndown chart
    • Product Backlog
    • Scrum team meeting
    • Sprint release plan
  6. Which of the following best describes a core belief of Agile?

    • The best customer feedback comes near the end of the project when there is working software to review.
    • Project status can be gauged by frequently reviewing completed milestones as reflected in the plan.
    • Working solutions are the most accurate way of seeing the progress of the effort.
    • Unique skill sets are harnessed when team members play different roles on a project.
  7. Test-Driven Development (TDD) is a rapid cycle of:

    • Requirements, coding, and testing.
    • Testing, coding, and refactoring.
    • Testing, refactoring, and validation.
    • Requirements, coding, and refactoring.
  8. A business analyst has identified a new risk in an Agile project. What is the best first step the business analyst should take regarding this risk?

    • Call a meeting with the project manager and senior management to determine how the risk will be managed.
    • Email the project manager and add it to the risk register so that it is discussed during the next daily standup.
    • Add the risk in a clearly visible location and ensure it is discussed after the next daily stand up.
    • Call an immediate meeting with all team members to discuss the newly identified risk.
  9. What are the primary outputs of a release planning session?

    • Release vision, assumptions, action items, and iteration goals
    • Prioritized Product Backlog, risks, action items, and release goals
    • Estimated iteration velocities, risks, action items, and Release Backlog
    • Risks, action items, dependencies, and Release Backlog
  10. Applying the Pareto rule when prioritizing the Product Backlog means that:

    • features that are lower priority are more likely to slip to the next iteration.
    • the value of a feature is not realized until the feature is complete.
    • more recent requests are usually more important to the business.
    • a small percentage of the work will provide a large percentage of the value.
  11. At a strategic level, what is the most appropriate way for an Agile team to estimate a project?

    • Creating a strategic plan by estimating hours and days required
    • Using an abstract measurement to estimate Product Backlog items
    • Estimating source lines of code needed to implement the features
    • Taking an initial set of estimates and adding an appropriate risk factor
  12. A development team has finished identifying the tasks they will be accountable for during the next sprint. Which of the following tools best provides transparency into the progress throughout the sprint?

    • Burndown chart
    • Gantt chart
    • Hours expended chart
    • Management baseline chart
  13. The term “last responsible moment” refers to the moment at which:

    • the iteration testing deadline arrives and code testing must stop.
    • failing to make a decision eliminates an important alternative.
    • release planning is complete and the first iteration planning starts.
    • the implementation date is set and sponsor approval has been received.
  14. A “Scrum of Scrums” meeting is:

    • Another name for the daily standup project meeting in a Scrum team.
    • A mechanism that coordinates multiple teams working on a single project.
    • A project meeting that happens twice every day across the Scrum teams.
    • An occasional leadership meeting that provides direction to multiple Scrum teams.
  15. The cost estimation techniques used on Agile projects are:

    • Rule of thumb
    • Bottom-up
    • Parametric
    • Top-down
  16. Estimating costs for an Agile project starts with which of the following types of meetings?

    • Project Retrospective
    • Steering Committee
    • Release Planning
    • Sprint Planning
  17. Who is responsible for making sure that each user story is associated with at least one user role or persona?

    • User
    • Developer
    • Customer
    • Persona
  18. Who is responsible for determining the business value of each feature?

    • Product Owner
    • Steering committee
    • ScrumMaster
    • Team
  19. During the daily standup meeting, a team member states that an issue has been encountered. This leads to the team members getting into a problem-solving discussion. How should the ScrumMaster respond?

    • Ask the team members to table the discussion until after the meeting is over.
    • If the item is really important, allow the discussion to expedite resolution of the issue.
    • Abruptly end the daily standup meeting and schedule another meeting to discuss the issue.
    • Ask the team how they would like to use the daily standup meeting for that day.
  20. Risk exposure is the:

    • Funds set aside to contain the risk.
    • Probability a risk will occur.
    • Amount of money the risk will cost if it occurs.
    • Amount of damage to the project if the risk occurs.