PMI Agile Certified Practitioner (PMI-ACP)® 온라인 연습
최종 업데이트 시간: 2026년06월04일
당신은 온라인 연습 문제를 통해 PMI PMI-ACP 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 PMI-ACP 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 717개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Agile emphasizes sustainable pace and continuous improvement, not overworking or overcommitting. The appropriate response is to identify why the team overcommitted, learn from it, and adjust future sprint planning. This aligns with the PMI Agile Practice Guide (Section 5.4: Sprint Planning and Velocity) and Section 5.6: Retrospectives, which recommend using retrospectives to address such issues.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) explains that over-committing leads to poor predictability, and inspecting root causes helps refine estimation and velocity in future sprints.
Option C is correct: it supports learning and improves future planning.
Option A promotes unsustainable practices.
Option B misunderstands velocity―it’s a measurement, not something to be increased by will.
Option D undermines team stability and agile planning based on consistent team capacity.
정답:
Explanation:
In agile, the Product Owner is the ultimate decision-maker regarding backlog prioritization and scope changes. According to the PMI Agile Practice Guide (Section 5.1: Backlog Prioritization), any changes that affect value delivery, schedule, or scope should be discussed with the Product Owner, who evaluates the business impact.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) reinforces that product direction and scope decisions must be handled through collaboration between the team and the Product Owner.
Option D is correct: seeking Product Owner input ensures value-based decision-making and customer alignment.
Option A (re-estimating the entire project) is unnecessary and burdensome.
Option B rejects valuable input and ignores iterative flexibility.
Option C goes against agile principles of focus and sustainable pace.
정답:
Explanation:
When a team reports that user stories are unclear or lack sufficient detail, the correct agile response is to foster collaborative refinement and shared understanding. A user story workshop is a well-recognized practice that involves the team and product owner collaborating to write, clarify, and refine stories. This is supported by the PMI Agile Practice Guide (Section 5.2: User Stories and Backlog Refinement), which recommends story-writing workshops as a proactive way to clarify requirements.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) notes that good agile teams collaboratively refine stories in grooming sessions or workshops to ensure shared clarity and alignment.
Option C is correct: a workshop enables both the team and product owner to collaborate in improving story clarity.
Option A oversimplifies the solution―acceptance criteria alone don’t fully define a story.
Option B misuses the retrospective, which is for process improvement, not story editing.
Option D escalates prematurely and undermines team ownership and collaboration.
정답:
Explanation:
Predictable flow in agile is achieved by reducing variability in story size and complexity. According to the PMI Agile Practice Guide (Section 5.7: Flow-based Agile and Kanban), working with small, similarly sized user stories increases throughput predictability and improves cycle time.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) supports breaking large stories into smaller, testable chunks as a way to stabilize delivery and forecasting.
Option A is correct: small user stories reduce variability and support predictable flow.
Option B supports testability but doesn’t directly improve flow.
Option C and D are too broad or conceptual to specifically improve predictability.
정답:
Explanation:
Planning Poker is a well-known estimation technique where team members use numbered cards (usually Fibonacci series) to estimate story point values based on relative size. It’s a consensus-based estimation method, as described in the PMI Agile Practice Guide (Section 5.2: Estimation Techniques) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Estimating Techniques).
Option D is correct: Planning Poker is explicitly designed for estimating stories in terms of points.
Option A (Parametric) is more common in traditional (predictive) planning.
Option B (One-to-one comparison) refers to relative sizing without collaboration.
Option C (Affinity) is another agile technique but typically used for grouping stories into size buckets, not direct story point consensus estimation.
정답:
Explanation:
Once the team has clarity on the user stories and agrees they are ready, the next step in agile planning is to estimate them. According to the PMI Agile Practice Guide (Section 5.2: Estimating) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), agile estimation techniques like story points or Planning Poker help the team gain a shared understanding of effort, complexity, and delivery time.
Option A is correct: estimating comes before development and guides prioritization and planning.
Option B prematurely dives into task-level detail before effort is understood.
Option C skips planning and development entirely.
Option D refers to retrospective, which comes after execution, not before.
정답:
Explanation:
The "Life Timeline" exercise is a technique used to build psychological safety and vulnerability-based trust. According to Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), exercises that encourage sharing personal stories and emotional journeys foster deep interpersonal connection, which is foundational to high-performance teams.
The PMI Agile Practice Guide (Section 4.3.2: Building Trust) emphasizes the role of emotional intelligence and trust-building in agile teams, stating that teams become high-performing when they feel safe to express themselves without fear of judgment.
Option B is correct: the exercise builds vulnerability and trust―key drivers of high performance.
Option A focuses on trust but doesn't emphasize vulnerability, which is central here.
Option C is too generic.
Option D misframes the purpose―it’s about building connection, not assessing competencies.
정답:
Explanation:
When issues recur across multiple iterations, it’s a strong indication that the root cause has not been addressed. The PMI Agile Practice Guide (Section 5.6 Retrospectives) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) recommend performing root cause analysis techniques (e.g., 5 Whys, Fishbone diagram) to ensure that the true source of recurring problems is uncovered and resolved.
Option B is correct: identifying root causes is essential to sustainable improvements.
Option A may help but doesn’t address the underlying team-level process.
Option C is useful after a solution is implemented but not the priority when the cause is unknown.
Option D is helpful for tracking, but again, ineffective if the root cause is unidentified.
정답:
Explanation:
Upon joining a team, a Scrum Master should focus on facilitating team collaboration, removing impediments, and creating a psychologically safe space. The PMI Agile Practice Guide (Section 3.3: Scrum Master Role) and Mike Griffiths (Chapter 3: Team Performance) stress that early efforts should center on servant leadership, helping the team identify and solve their own challenges.
Option C is correct: supporting the team through facilitation reflects the core role of a Scrum Master.
Option A is prescriptive and not aligned with cross-functional team philosophy.
Option B may be necessary later, but first, trust and team dynamics must be established.
Option D falls under the Product Owner’s responsibility, not the Scrum Master’s.
정답:
Explanation:
The retrospective is the agile ceremony designed for teams to inspect and adapt their process based on actual performance. According to the PMI Agile Practice Guide (Section 5.6: Retrospectives), discussing velocity issues and delivery concerns during retrospectives allows the team to collaboratively identify improvement actions.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) also notes that retrospectives are the best setting to discuss variations in velocity and refine estimation or planning practices based on empirical evidence.
Option C is correct: the retrospective is where the team adapts based on reality.
Option A may come later but doesn’t address the root issue.
Option B goes against agile principles of stable teams and empirical planning.
Option D is reactive and may mask underlying process issues.
정답:
Explanation:
The first step for a new Scrum Master is to gain context and alignment. According to the PMI Agile Practice Guide (Section 2.3: Agile Mindset), agile leaders must understand the product vision and goals to provide proper support to the team and align delivery efforts with organizational objectives.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 2: Agile Principles and Mindset) emphasizes that new leaders should start by understanding stakeholder expectations, enterprise context, and business drivers before making operational decisions like backlog setup or sprint planning.
Option B is correct: understanding the project vision provides critical context.
Option A is premature without first understanding the broader organizational objectives.
Option C (sprint 0) can be useful but should follow alignment on vision and context.
Option D skips necessary discovery and planning.
정답:
Explanation:
After the product vision is communicated, the product owner should ensure that the product backlog is prioritized so the team can focus on delivering the most valuable features first. According to the PMI Agile Practice Guide (Section 5.1 Product Backlog and Vision Alignment), prioritizing the backlog helps teams understand the product roadmap and plan their efforts accordingly.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) reinforces that the product owner’s key responsibility is backlog prioritization, not task management or detailed design.
Option C is correct: prioritizing the backlog enables the team to understand and plan the roadmap.
Option A and B are too detailed for the product owner and move into the team's domain.
Option D is a team responsibility, not the product owner’s.
정답:
Explanation:
Agile teams are self-organizing and should strive for consensus-based decision making. The PMI Agile Practice Guide (Section 4.3.1 Team Empowerment) supports facilitative leadership where leaders guide decision-making, not override it. Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 3: Team Performance) emphasizes that leaders should foster collaboration and respect diverse views to prevent disengagement.
Option A is correct: encouraging consensus builds ownership, trust, and engagement.
Option B and C still place control with the leader, reducing team empowerment.
Option D is too passive; agile leaders participate actively as facilitators.
정답:
Explanation:
Agile relies on regular retrospectives to reflect, adapt, and implement improvements. According to the PMI Agile Practice Guide (Section 5.6 Retrospectives), teams should continuously inspect their process and collectively own the changes needed to improve. This supports a culture of learning and accountability.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) encourages frequent retrospectives that include open discussion and shared responsibility for change implementation.
Option A is correct: holding retrospectives and collaborating on actions promotes ownership and progress.
Option B neglects process change.
Option C limits transparency and team collaboration.
Option D addresses trust but not the recurring problems.
정답:
Explanation:
Agile promotes transparency and ongoing communication with all stakeholders, including legal and compliance teams. According to the PMI Agile Practice Guide (Section 7.1 Communications), one of the Scrum Master's responsibilities is to keep stakeholders informed of project progress and projections using tools like burnup/burndown charts, velocity trends, or product roadmaps.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) emphasizes that sharing the trajectory of progress and scope delivery builds trust and provides clarity to non-technical stakeholders.
Option C is correct: sharing actual progress and trends with legal ensures alignment and transparency.
Option A misplaces the responsibility―it's the stakeholders who need visibility.
Option B shifts product decisions prematurely.
Option D assumes satisfaction trumps contractual obligations―this can cause legal issues.