DASM問題集で2024年最新のPMI DASM試験問題
無料で使えるDASMブレーン問題集でダウンロード（DASMテスト問題集無料更新された)
質問 # 26
Identity three principles of the Disciplined Agile mindset. (Choose three)
- A. Delight customers.
- B. Enterprise awareness.
- C. Be pragmatic.
- D. Accelerate delivery
- E. Be a servant leader.
正解：A、B、C
解説：
The Disciplined Agile mindset includes principles that guide individuals and teams in making decisions and taking actions that align with Agile values and the specific context of their organization. Three principles of the Disciplined Agile mindset are:
* B. Enterprise awareness: Encourages teams to work with an understanding of their organization's goals, strategies, and needs, ensuring alignment and collaboration across teams and departments.
* C. Delight customers: Focuses on delivering high value and exceptional service to customers, ensuring that their needs are met or exceeded.
* E. Be pragmatic: Involves taking a practical and context-sensitive approach, applying tools and practices that best fit the situation rather than adhering strictly to a particular methodology.
Other options likeA. Accelerate deliveryandD. Be a servant leaderare relevant to Agile practices but are not explicitly stated as Disciplined Agile mindset principles.
Thus, the correct answers areB. Enterprise awareness,C. Delight customers, andE. Be pragmatic.
質問 # 27
Which is not a feature of a user story?
- A. Estimable
- B. Testable
- C. Achievable
- D. Negotiable
正解：C
解説：
In agile practices, particularly in the context of user stories, the features are typically defined by the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, and Testable."Achievable"is not a standard feature of a user story. Instead, user stories should beNegotiable(they are not fixed, and details can be discussed),Estimable(it should be possible to estimate the effort required), andTestable(it should be possible to verify whether the story has been implemented correctly). Therefore, "Achievable" is not one of the features of a user story.
質問 # 28
Which of the following process goals require most of the effort when tailoring your agile strategy?
- A. Improve Quality
- B. Address Changing Stakeholder Needs
- C. Explore Scope
- D. Align with Enterprise Direction
正解：B
解説：
* Address Changing Stakeholder Needs:This process goal involves actively engaging with stakeholders to understand and respond to their evolving requirements, preferences, and concerns throughout the project's life cycle. This goal is dynamic and requires significant effort because stakeholder needs and priorities can change frequently, requiring continuous adjustment of the Agile strategy. Tailoring your strategy to effectively address these needs involves multiple activities, such as conducting frequentreviews, reprioritizing the backlog, aligning deliverables with stakeholder expectations, and incorporating feedback into the development process.
* Why It Requires the Most Effort:
* Dynamic Nature of Stakeholder Needs:Stakeholders' needs are often unpredictable and can change rapidly due to market shifts, regulatory changes, or new business priorities. This requires Agile teams to be highly adaptive and frequently recalibrate their strategies.
* Continuous Engagement and Communication:Maintaining an ongoing dialogue with stakeholders, gathering feedback, and negotiating trade-offs consume considerable time and resources.
* Alignment and Consensus Building:Repeated effort is needed to ensure that all stakeholders are aligned and that there is a consensus on the direction and scope of the project.
Incorrect Options:
* A. Improve Quality:While improving quality is a significant goal in any Agile strategy, it is more focused on refining existing processes, techniques, and tools rather than continuously adapting to external changes. Thus, it may not require as much continuous effort in tailoring the Agile strategy.
* C. Align with Enterprise Direction:This goal involves ensuring that the team's work aligns with the broader organizational objectives. While important, it is generally a less dynamic activity compared to addressing changing stakeholder needs and may not require as frequent adjustments once alignment is initially achieved.
* D. Explore Scope:Exploring the scope is an initial activity in an Agile project where the team works to understand the project's boundaries and deliverables. Although this requires effort at the beginning of the project, it is not a continuous effort throughout the project life cycle like addressing changing stakeholder needs.
Therefore,"Address Changing Stakeholder Needs"is the process goal that requires the most effort due to its dynamic nature and the continuous engagement required to adapt the Agile strategy to evolving conditions.
質問 # 29
What are the three phases of DAD's delivery life cycle?
- A. Introduction. Substance, Alteration
- B. Initiation. Foundation. Conversion
- C. Inception. Construction. Transition
- D. Commencement. Creation. Evolution
正解：C
解説：
The three phases of Disciplined Agile Delivery (DAD)'s delivery life cycle are:
* Inception: This phase focuses on getting the project off the ground. It includes identifying stakeholders, understanding the vision, defining the initial scope, and planning for the necessary resources and timeline.
* Construction: This phase involves building the solution incrementally and iteratively, with continuous delivery of working software and regular stakeholder feedback.
* Transition: This phase prepares the solution for release into production or the marketplace. It includes final validation, user training, deployment planning, and release management.
Other options are incorrect:
* A. Commencement, Creation, Evolutionare not standard DAD phases.
* B. Initiation, Foundation, Conversiondo not match DAD terminology.
* C. Introduction, Substance, Alterationare not relevant to DAD.
Therefore, the correct answer isD. Inception, Construction, Transitions.
質問 # 30
Which method extends the Kaizen loop strategy to help teams identify techniques that are likely to work in their context?
- A. Guided continuous improvement
- B. Cross-team learning
- C. Communities of practice
- D. Explicit workflow policies
正解：A
質問 # 31
What is the first step in choosing your team's way of working?
- A. Make some choices.
- B. Analyze the context.
- C. Connect the dots
- D. Select best-tit life cycle.
- E. Guided continuous improvement
正解：B
解説：
The first step in choosing a team's way of working (WoW) in Disciplined Agile is toanalyze the context.
This involves understanding the specific needs, constraints, and circumstances of the team and its environment. By analyzing the context, the team can make informed decisions about which practices, tools, and frameworks are most appropriate for their situation. This ensures that the chosen WoW is tailored to fit the team's unique challenges and goals.
質問 # 32
The team lead notices that a team member is falling behind on their work. What would a goodDisciplined Agile team lead do?
- A. Provide time management training to the team member.
- B. Redistribute the team member's work across the team to avoid embarrassing the team member.
- C. Have a conversation with the team member to better understand what is getting in their way and look for solutions together.
- D. Have a one-to-one meeting with the team member about their recent failures.
正解：C
解説：
In Disciplined Agile, a good Team Lead (or Scrum Master) should act as a servant leader, supporting and enabling team members to succeed. When a team member is falling behind, the appropriate response is to have a conversation with the team member to understand what is getting in their way and work together to find solutions. This approach fosters an environment of trust and collaboration and helps to identify and remove impediments that may be affecting the team member's performance. The goal is to address the root cause of the issue and provide support, rather than assigning blame or creating discomfort.
質問 # 33
What docs a well-written user story describe?
- A. The expectations of the product owner.
- B. A fixed outcome.
- C. The customers' perspective.
- D. The needs of all users.
正解：C
解説：
A well-written user story in agile practices, including Disciplined Agile, describesthe customer's perspective
. User stories are short, simple descriptions of a feature or requirement from the point of view of the end user or customer. They are intended to capture the "who, what, and why" of a requirement, focusing on the value it delivers to the customer. This perspective ensures that the development team understands the real-world needs and motivations behind the features they are building, allowing them to create solutions that truly meet user needs.
質問 # 34
What arc Disciplined Agile milestones based on?
- A. Lean governance
- B. Documentation
- C. Continuous integration
- D. Lifecycle
正解：A
解説：
Disciplined Agile (DA) milestones are based on the concept ofLean governance, which is focused on ensuring that agile practices are aligned with the organization's overall objectives while minimizing bureaucracy. In the DA framework, milestones provide lightweight checkpoints throughout the lifecycle to ensure that the team is on track to meet its objectives and deliver value. These milestones are not about documentation or merely following a predefined lifecycle but are instead focused on achieving business value in a lean and efficient manner.
* A. Continuous integrationis a practice rather than a basis for milestones.
* B. Documentationis not a central focus of DA milestones.
* D. Lifecyclerefers to the various phases in the DA process, but milestones are specific checkpoints within these phases guided by lean governance principles.
Thus,C. Lean governanceis the correct answer, as it embodies the principles upon which Disciplined Agile milestones are established.
質問 # 35
What is the role of management in Lean?
- A. Create awesome team environments.
- B. Ensure documentation is completed.
- C. Provide minimum viable products to the team.
- D. Ensure decisions are not made regionally.
正解：A
解説：
In Lean and Agile methodologies, the role of management is tocreate awesome team environmentsthat foster collaboration, creativity, and high performance. Lean principles emphasize empowering teams, removing obstacles, and creating a culture of continuous improvement and respect. This means management's role is to support the team, provide the necessary resources, and ensure a safe and conducive environment for delivering high-quality work.
* A. Ensure documentation is completedis not the primary role of management in Lean.
* B. Provide minimum viable products to the teamis more related to the responsibilities of product owners or teams, not management.
* C. Ensure decisions are not made regionallyis not directly related to the core responsibilities of management in Lean.
Therefore,D. Create awesome team environmentscorrectly reflects the Lean management role.
質問 # 36
What are the three phases common across project life cycles? (Choose three)
- A. Inspiration
- B. Construction
- C. Inception
- D. Modulation
- E. Transition
正解：B、C、E
解説：
In Disciplined Agile (DA), the three common phases across project life cycles areInception, Construction, andTransition. These phases reflect the iterative and incremental approach of agile methodologies tailored to suit varying contexts.
* Inception: This phase is about getting things started properly. It includes initial planning activities such as defining the vision, developing a preliminary project plan, identifying stakeholders, securing funding, and setting up the initial environment.
* Construction: This phase focuses on developing a consumable solution in a series of iterations. The team builds, enhances, and evolves the solution to ensure that it meets stakeholders' needs while remaining aligned with the overarching vision and goals.
* Transition: The transition phase ensures that the solution is ready for delivery to the end-users or stakeholders. This includes final validation and verification activities, user training, deployment, and addressing any remaining issues.
These phases are common in the DA life cycles, reflecting the disciplined approach to managing complexity in various types of projects, from straightforward to highly complex, while supporting adaptability and continuous improvement.
質問 # 37
What is the architecture owner responsible for?
- A. Removing impediments
- B. Mitigating key technical risks
- C. Working cross-functionally to deliver the solution
- D. Determining the priorities for the solution
正解：B
解説：
In Disciplined Agile, theArchitecture Owneris responsible formitigating key technical risks. This role focuses on overseeing the architectural integrity of the solution being developed, ensuring that the team makes sound technical decisions that align with the desired architecture and quality attributes of the project. The Architecture Owner helps in identifying and addressing potential technical risks early in the project life cycle, collaborating with the team to adapt the architecture as necessary to mitigate these risks.
This individual works closely with the team to guide architectural considerations, ensures compliance with the chosen architectural strategies, and maintains the overall technical direction of the project. Although they are involved in other cross-functional activities, their primary responsibility is to foresee and address technical challenges that could jeopardize the success of the project.
質問 # 38
What goal diagrams should a team select first?
- A. The goals in which the team has the least experience
- B. The goals that are selected by the customer and stakeholders.
- C. The goals that are the easiest to complete.
- D. The goals that ate most relevant to the team's context and lite cycle.
正解：D
解説：
In Disciplined Agile, teams are encouraged to selectgoals that are most relevant to their context and life cycle. This approach ensures that the team focuses on achieving outcomes that align with their specific needs, challenges, and project phase. Goal diagrams in DA help teams visualize and prioritize their objectives, and by choosing goals most pertinent to their current context, teams can address the most critical aspects first and adjust their practices effectively.
質問 # 39
What are the benefits to having a long-live (stable) team?
- A. Trustworthy
- B. Projectized
- C. Highly collaborative
- D. Ability to multi-task
- E. Specifically resourced
正解：A、C
解説：
A long-lived (or stable) team is a group of individuals who work together over an extended period, typically across multiple projects or product increments. In the context of PMI's Disciplined Agile (DA) framework, having a long-lived team is beneficial for several reasons:
* Trustworthy (A):As team members work together over time, they build a strong sense of trust. Trust within a team is foundational for effective collaboration, decision-making, and conflict resolution.
Team members learn to rely on each other's skills and knowledge, leading to more effective and efficient work processes. Disciplined Agile emphasizes creating environments where trust can be fostered, which is more easily achieved in stable, long-lived teams.
* Highly Collaborative (C):Long-lived teams develop a rhythm of working together, which leads to high levels of collaboration. As team members become more familiar with each other's working styles, strengths, and weaknesses, they can communicate more effectively, align on goals more quickly, and coordinate their efforts more efficiently. This heightened collaboration accelerates delivery, improves quality, and fosters continuous improvement-key principles in the Disciplined Agile toolkit.
Incorrect Options:
* B. Projectized:While the concept of a "projectized" organization focuses on structuring around projects, this does not inherently relate to the benefits of having a long-lived team. In contrast, Disciplined Agile promotes stable teams over project-centric teams to maximize the value delivery and learning curve.
* D. Specifically resourced:This option refers to the allocation of specific resources for projects or tasks, which does not directly align with the idea of having a stable, long-term team.
* E. Ability to multi-task:Multi-tasking is generally not considered a benefit within agile frameworks, including Disciplined Agile. Multi-tasking can lead to inefficiency and reduced focus, which goes against the principles of optimizing flow and delivering value quickly.
Thus, the most appropriate answers that align with the principles of Disciplined Agile areA.
TrustworthyandC. Highly collaborative
質問 # 40
What are the attributes of a leader? (Choose three)
- A. Focuses on goals
- B. Assigns tasks
- C. Goes with the flow
- D. Takes risks
- E. Inspires trust
正解：A、D、E
解説：
The key attributes of a leader in an agile context include the ability tofocus on goals,inspire trust, andtake risks. Agile leaders guide their teams by keeping a clear vision of the goals, building trust through transparency and integrity, and being willing to take calculated risks to achieve desired outcomes. They do not simply "go with the flow" or assign tasks in a top-down manner; instead, they empower their teams, foster a culture of trust, and support innovation by encouraging risk-taking within safe-to-fail boundaries.
質問 # 41
Select two tactical scaling factors that must be considered when analyzing the team's context. (Choose two)
- A. Budget
- B. Domain Complexity
- C. Demographics
- D. Team Size
- E. Dynamics
- F. Best Practices
正解：B、D
解説：
When analyzing a team's context for tactical scaling in Disciplined Agile, two key factors that must be considered areDomain ComplexityandTeam Size:
* C. Domain Complexity: Refers to the complexity of the problem domain the team is working within.
More complex domains require different approaches and potentially more sophisticated techniques to manage uncertainty, dependencies, and risks.
* D. Team Size: The size of the team affects how the team communicates, collaborates, and organizes itself. Larger teams may require additional coordination, communication practices, and role definitions to be effective.
The other options are less relevant for tactical scaling:
* A. Demographics,B. Best Practices,E. Budget, andF. Dynamicsare not directly identified as key tactical scaling factors in the Disciplined Agile context.
質問 # 42
Which characteristic describes a good user story according to the f.N.V.E.S.T. mnemonic?
- A. Incremental
- B. Satisfactory
- C. Valuable
- D. Tangible
正解：C
解説：
According to theINVEST mnemonic, a good user story should beValuable. This means that the user story must deliver value to the customer or stakeholder. Each user story should have a clear purpose, ensuring that the effort invested in its development contributes to the overall product value. Other criteria of the INVEST mnemonic include Independent, Negotiable, Estimable, Small, and Testable, but "Valuable" is key to justifying the user story's inclusion in the product backlog.
質問 # 43
......
PMI DASM 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
検証済みのDASM問題集と解答で合格保証で試験問題集テストエンジン：https://jp.fast2test.com/DASM-premium-file.html