リアルScrum SAFe-POPM日本語試験問題集には正解56問題と解答があります
有効なSAFe-POPM日本語テスト解答とScrum SAFe-POPM日本語試験PDF問題を試そう
質問 # 19
チーム同期中のプロダクトオーナーの責任は何ですか?
- A. イベントを促進するため
- B. ストーリーの意図を明確にする
- C. 顧客からのフィードバックを伝える
- D. イテレーションに新しい作業を追加する
正解：B
解説：
One responsibility of the Product Owner during Team Sync is to clarify the intent behind each user story or backlog item. This includes providing additional context, details, and answering any queries raised by the development team1. The Team Sync is a daily event where the members of the Agile team synchronize their work and plan for the next 24 hours2. The Product Owner participates in the Team Sync to ensure that the team is working on the right things and that the stories are aligned with the customer and stakeholder needs3.
References:
*What is one responsibility of the Product Owner during Team sync ...
*Team Sync - Scaled Agile Framework
*What's a Product Owner to Do - PO role within SAFe
質問 # 20
ワークフローを表す機能を視覚化するツールは何ですか?
- A. 継続的デリバリーパイプライン
- B. ユーザーエクスペリエンスデザイン
- C. ストーリーマップ
- D. チームカンバン
正解：C
解説：
A story map is a tool that visualizes features representing a workflow. A story map is a two-dimensional arrangement of user stories that shows the relationship between the user activities and the features that support them1. A story map helps the team to understand the user journey, prioritize the features based on value and dependencies, and plan the releases and iterations2.
References:
*Story Mapping - Scaled Agile Framework
*What is User Story Mapping? | Definition and Overview
質問 # 21
イテレーションの振り返り中に特定された改善項目に対する次のアクションは何ですか?
- A. チームバックログにストーリーとして入力されます
- B. 残りのリスクとともにROAM化される
- C. これらはスクラムマスター/チームコーチに渡され、解決されます。
- D. ビジネスオーナーにエスカレーションされます
正解：A
解説：
The next action for improvement items identified during the Iteration Retrospective is to enter them as Stories in the Team Backlog. By adding these improvement items as Stories, they become part of the team's ongoing work and are prioritized alongside other tasks and user stories for future iterations or sprints1. This way, the team can track and implement the improvement actions and measure their impact on the team's performance and quality2.
References:
*Iteration Retrospective - Scaled Agile Framework
*What happens to improvement items identified during the Iteration Retrospective? - Service Centre List
質問 # 22
完了の定義を確立することが重要なのはなぜですか？
- A. すべてのアジャイルチーム間で標準化された作業を作成する
- B. 機能が期待されるビジネス上のメリットをもたらすことを保証する
- C. ストーリーが完了するタイミングについて合意を形成する
- D. スクラムマスター/チームコーチが品質を徹底できるようにする
正解：C
質問 # 23
PI 計画を成功させるために必要なビジョンとバックログを ART が確保できるようにする役割はどれですか?
- A. 製品管理
- B. リリーストレインエンジニア
- C. プロダクトオーナー
- D. リーンアジャイルセンターオブエクセレンス
正解：A
解説：
Product Management is the role that ensures that the Agile Release Train (ART) has the Vision and Backlog needed to engage in PI Planning successfully. Product Management is responsible for defining and communicating the Vision, which describes the future state of the solution and its features1. Product Management also develops and maintains the Program Backlog, which contains the features and enablers that the ART will implement in the upcoming Program Increments (PIs)2. Product Management collaborates with stakeholders, customers, architects, and other roles to discover, prioritize, and refine the backlog items and present them to the ART during PI Planning3.
References:
*Vision - Scaled Agile Framework
*Product Management - Scaled Agile Framework
*PI Planning - Scaled Agile Framework
質問 # 24
アジャイル チームがイテレーション目標を使用するのはなぜですか?
- A. チームがPI目標に対して責任を持つようにする
- B. チームが各イテレーションでコミットしたストーリーを確実に達成できるようにする
- C. チームメンバーとプロダクトオーナーを共通の目的に合わせる
- D. アジャイルチームがPI期間中に達成しようとするビジネス成果を要約する
正解：C
解説：
Iteration Goals are a high-level summary of the business and technical goals that an Agile Team agrees to accomplish in an Iteration. They are vital to coordinating an Agile Release Train (ART) as a self-organizing, self-managing team of teams1. Iteration Goals help the team and the Product Owner to reach agreement on the business value they intend to deliver, align their work to their team PI objectives, and ground everyone on their shared purpose2.
References:
*Iteration Goals - Scaled Agile Framework
*What Is The Purpose Of Iteration Goals? - GoRetro
質問 # 25
ソリューション ロードマップではどのような時間単位が使用されますか?
- A. PI
- B. 年
- C. 反復
- D. 日数
正解：A
解説：
Program Increments (PIs) are the unit of time used on Solution Roadmaps, which are visual tools that forecast and communicate the planned deliverables, milestones, and investments over a time horizon12. PIs are fixed-length timeboxes, typically 8 to 12 weeks long, that provide a regular and predictable planning cadence for the Agile Release Trains (ARTs) and Solution Trains3. PIs are used on Solution Roadmaps to:
*Align the solution delivery with the PI objectives, which are the SMART goals that define the expected outcomes and benefits for each ART and Solution Train in a PI3.
*Coordinate the dependencies and interfaces between the ARTs and Solution Trains that contribute to the solution3.
*Provide a near-term forecast of the features and capabilities that will be delivered in the next two to three PIs12.
*Incorporate feedback and learning from the previous PIs and adjust the scope and priority of the work items as needed12.
Some additional information that might be helpful for you are:
*The other options (A, B, and D) are not the unit of time used on Solution Roadmaps, but rather units of time that may be used for other purposes or in other contexts.
*Iterations are fixed-length timeboxes, typically one or two weeks long, that provide a regular and predictable development cadence for the Agile Teams4. Iterations are used to plan, execute, and demo the work items in the Team Backlog4.
*Years are a unit of time that may be used to provide a high-level overview of the roadmap, outlining major milestones, goals, and initiatives that are planned over multiple years2. Years are not used to plan or forecast the solution delivery in detail, as they are too long and uncertain for Agile planning2.
*Days are a unit of time that may be used to estimate the effort or duration of a work item or a task5. Days are not used to schedule or forecast the solution delivery on the roadmap, as they are too granular and variable for Agile planning5.
質問 # 26
複雑なクリティカルパスの課題を管理するための 1 つの戦略は何ですか?
- A. 他のチームに作業を分配する
- B. 同じ反復依存関係を排除するためのシーケンス作業
- C. 予測されるキャパシティに基づいてチーム間で作業を割り当てる
- D. チーム間で作業を調整したり、機能とストーリーを分割したりする
正解：D
解説：
One strategy for managing complex critical path challenges is to adjust work between teams or split Features and Stories. Complex critical path challenges are situations where the delivery of value depends on the completion of multiple interdependent tasks by different teams1. These challenges can cause delays, bottlenecks, and inefficiencies in the value stream. To overcome these challenges, one option is to adjust work between teams or split Features and Stories, so that the dependencies are minimized or eliminated2. This can help improve the flow of work, reduce the risk of integration issues, and increase the flexibility and responsiveness of the teams3.
References:
*Accelerating Flow with SAFe - Scaled Agile Framework
*Managing Dependencies - Scaled Agile Framework
質問 # 27
効果的な PI 目標を記述する際の特徴は何ですか?
- A. 重要なストーリーを含む
- B. 重大なリスクの特定
- C. 値の説明
- D. コミットされた機能の一覧
正解：C
解説：
One characteristic of writing effective PI Objectives is describing the value that the objectives will deliver to the customers and stakeholders. PI Objectives are a summary of the business and technical goals that the Agile Release Train (ART) intends to achieve in the upcoming Program Increment (PI)1. They are not just a list of features or stories, but rather a statement of the outcomes and benefits that the features or stories will provide2. By describing the value, the PI Objectives help align the teams and stakeholders to a shared vision and mission, and provide a basis for measuring the progress and performance of the ART3.
References:
* PI Objectives - Scaled Agile Framework
* Your Guide to Writing Great Iteration and PI Objectives - Scaled Agile
* How to Write PI Objectives - ValueGlide
質問 # 28
ソリューションと PI ロードマップに影響を与えるものは何ですか?
- A. 市場の動向
- B. 顧客中心の機能
- C. ART容量
- D. バリューストリーム
正解：A
解説：
Market dynamics are one of the influences on Solution and PI Roadmaps, which are visual tools that forecast and communicate the planned deliverables, milestones, and investments over a time horizon12. Market dynamics are the external factors that affect the demand and supply of a product or service in the market, such as customer needs, competitor actions, regulatory changes, technological trends, and economic conditions3.
Market dynamics influence Solution and PI Roadmaps in the following ways:
*They help identify the market problems or opportunities that the solution aims to address or capture12.
*They help prioritize the features and capabilities that deliver the most value to the customers and stakeholders12.
*They help align the solution delivery with the market rhythms and events, which are the periodic or one-time occurrences that have a significant impact on the solution adoption or performance12.
*They help validate the assumptions and hypotheses about the customer and the solution through feedback and learning12.
Some additional information that might be helpful for you are:
*The other options (A, B, and D) are not influences on Solution and PI Roadmaps, but rather elements or outcomes of the roadmaps.
*Value Streams are the primary constructs for understanding, organizing, and delivering value to the customer.
Value Streams are the basis for defining the solution vision, strategy, and roadmap4.
*Customer-centric Features are the work items that represent the benefits or outcomes that the solution provides to the customer or user. Customer-centric Features are the main content of the Solution and PI Roadmaps5.
*ART capacity is the amount of work that an Agile Release Train (ART) can handle in a Program Increment (PI). ART capacity is a factor that determines the feasibility and scope of the Solution and PI Roadmaps.
質問 # 29
複雑なクリティカルパス上の課題を管理するための戦略の一つは何ですか？
- A. 他のチームに作業を分配する
- B. 同じ反復依存関係を排除するためのシーケンス作業
- C. 予測されるキャパシティに基づいてチーム間で作業を割り当てる
- D. チーム間で作業を調整するか、フィーチャーとストーリーを分割します。
正解：D
解説：
One effective strategy for managing complex critical path challenges in SAFe is to adjust the allocation of work between teams or to split features and stories. This approach allows for more flexibility in managing dependencies and workload distribution, ensuring that teams can adapt to changes and maintain progress on the critical path.
The strategy is aligned with the principles of SAFe, which emphasize decentralization of decision-making and enabling teams to manage their own workloads effectively
質問 # 30
PI 計画中にビジョンをアジャイル リリース トレインに伝達して改良することは、どの SAFe コア バリューをサポートしますか?
- A. 絶え間ない改善
- B. 透明性
- C. アラインメント
- D. 人々への敬意
正解：C
解説：
Communicating and refining the Vision to the Agile Release Train (ART) during PI Planning supports the SAFe Core Value of Alignment. Alignment is one of the four core values of SAFe thatguides the behaviors and actions of the people who work under the framework1. Alignment means that everyone understands the strategic direction, the value streams, and the solution intent, and how their role and work contribute to them2.
PI Planning is a crucial event in SAFe where all the teams within the ART come together to plan their work for the upcoming Program Increment (PI)3. During PI Planning, the Product Management presents the Vision, which describes the future state of the solution and its features4. The Vision helps align the teams and stakeholders to a shared mission and goal, and provides the context and purpose for the PI objectives.
References:
*SAFe Core Values - Scaled Agile Framework
*Alignment - Scaled Agile Framework
*PI Planning - Scaled Agile Framework
*Vision - Scaled Agile Framework
質問 # 31
システムデモの効果を高めるものは何ですか?
- A. イテレーション計画中にデモの方法と内容を検討する
- B. デモの準備に多くの時間を費やす
- C. チームレベルの指標に焦点を当てる
- D. チームの混乱を最小限に抑えるためにチームの出席者を制限する
正解：A
解説：
Considering how and what to demo during Iteration Planning increases the effectiveness of System Demos, which are events that provide an integrated view of new features delivered by the Agile Release Train (ART) in each Iteration12. By thinking ahead of how and what to demo, the teams can:
*Align on the product vision and roadmap and ensure that the work items are aligned with the customer value and the PI objectives12.
*Define clear and testable acceptance criteria for each work item and plan how to verify them in the demo12.
*Identify and resolve any dependencies, risks, or impediments that may affect the demo12.
*Prepare the demo environment and the necessary tools and data to support the demo12.
*Practice the demo and rehearse the script and the roles of the presenters12.
Some additional information that might be helpful for you are:
*The other options (A, B, and C) are not actions that increase the effectiveness of System Demos, but rather actions that may reduce it.
*Spending a lot of time preparing for the demo may not be effective, as it may take away time and focus from the actual development and testing of the work items. Instead, the teams should aim for continuous integration and built-in quality practices that enable them to demo the work items as soon as they are done12.
*Limiting team attendance to minimize disruptions to the team may not be effective, as it may reduce the feedback and collaboration opportunities that the demo provides. Instead, the teams should invite and engage all the relevant stakeholders, such as Business Owners, executive sponsors, other Agile Teams, development management, and customers, to the demo12.
*Focusing on team-level metrics may not be effective, as it may not reflect the true value and progress of the integrated work across the ART. Instead, the teams should focus on system-level metrics, such as PI objectives, solution quality, and customer satisfaction, to evaluate the outcome and impact of the demo12.
質問 # 32
SAFeにおけるPIプランニングの主な目的を最もよく要約しているのは、次のうちどれですか？
- A. チームがバックログを確定できるようにする
- B. 次回のPIの詳細なアーキテクチャを定義する
- C. アジャイルリリーストレインのすべての参加者を共通のミッションと目標に合わせる
- D. 各チームの能力に基づいてユーザーストーリーを割り当てる
正解：C
解説：
The SAFe POPM workbook defines PI Planning as "a cadence-based event that serves as the heartbeat of the ART," aligning all teams on the ART to a shared mission and Vision . This makes the primary purpose of PI Planning alignment across ART participants around a common direction and goal.
質問 # 33
問題解決ワークショップが従来の教訓文書よりも効果的なのはなぜですか?
- A. 次のPIのバックログ項目を通じて改善を実行可能にします
- B. ワークショップはドキュメント作成よりも魅力的です
- C. ドキュメントよりもコラボレーションがアジャイル宣言の重要な推奨事項です
- D. 少数のリーダーが関与する
正解：A
解説：
The problem-solving workshop is more effective than traditional lessons learned documents because it makes improvements actionable through backlog items for the next Program Increment (PI). A problem-solving workshop is a structured approach to identify and solve problems that affect the performance and quality of the Agile Release Train (ART) or Solution Train1. Unlike traditional lessons learned documents, which are often passive and rarely implemented, a problem-solving workshop results in a set of improvement backlog items that are prioritized and planned for the next PI2. This way, the teams can implement the improvements and measure their impact on the value delivery3.
References:
*Inspect and Adapt - Scaled Agile Framework
*Why is the problem-solving workshop more effective than traditional ...
*Problem-solving workshop: Step-by-Step - Agilephoria
質問 # 34
PI 計画中に作業を視覚化するために何が役立ちますか?
- A. ART PI の目的
- B. ART PI カンバンボード
- C. ART企画委員会
- D. ART PI リスク
正解：C
解説：
The ART Planning Board is a physical or virtual board that helps visualize the work of the Agile Release Train (ART) during PI Planning. It shows the features and dependencies for each team and iteration in the Program Increment (PI)1. The ART Planning Board helps the teams and stakeholders to see the big picture, identify and resolve issues, and collaborate on the delivery plan2.
References:
*ART Planning Board - Scaled Agile Framework
*PI Planning - Scaled Agile Framework
質問 # 35
ビジョンを伝える際に重要なことは何ですか?
- A. リーン予算ガードレールの重要性
- B. 機能の優先順位付けの重要性
- C. 非機能要件の重要性
- D. 共感インタビューの重要性
正解：A
解説：
The vision is a description of the future state of the solution under development, reflecting customer and stakeholder needs, as well as the features and capabilities proposed to meet those needs1. Communicating the vision effectively is essential for creating a shared understanding of the program's goals and objectives, especially as they evolve due to changing market needs and business drivers1. One of the key aspects of communicating the vision is to establish the importance of Lean budget Guardrails, which are policies and practices that ensure the financial integrity and economic viability of the solution2. Lean budget Guardrails provide the boundaries and context forthe solution development, enabling decentralized decision-making and empowering teams to operate autonomously within the agreed-upon funding2. By communicating the importance of Lean budget Guardrails, the vision helps align the teams with the strategic themes and portfolio priorities, as well as foster a culture of innovation and learning2.
References: 1 Vision - Scaled Agile Framework, 2 Lean Budgets - Scaled Agile Framework
質問 # 36
価値提供においてチームをサポートするプロダクトオーナーの責任はどれですか?
- A. 利点仮説のテスト
- B. 建築のランウェイをサポートする
- C. 市場の力を理解する
- D. 組み込み品質の促進
正解：D
解説：
Fostering Built-in Quality is a Product Owner responsibility that supports the team with value delivery.
Built-in Quality is one of the four core values of SAFe® and it means that every aspect of the solution is continuously verified for quality1. The Product Owner fosters Built-in Quality in the following ways:
*Collaborating with the Development team and other stakeholders to define clear and testable acceptance criteria for each work item2.
*Participating in team events such as Iteration Planning, Backlog Refinement, and Iteration Review to provide feedback and guidance on the quality of the work2.
*Reviewing and approving the work items that meet the Definition of Done and the acceptance criteria2.
*Encouraging the team to apply Agile testing practices such as Test-First, Test-Driven Development, and Behavior-Driven Development3.
*Supporting the team's continuous integration and continuous delivery practices to ensure fast and frequent feedback on the quality of the solution3.
Some additional information that might be helpful for you are:
*The other options (A, B, and C) are not Product Owner responsibilities that support the team with value delivery, but rather responsibilities that belong to other roles or activities.
*Understanding market forces is a responsibility of Product Management, who is accountable for the market and business aspects of the solution4.
*Supporting the Architectural Runway is a responsibility of System Architects/Engineers, who provide technical guidance and enablement to the teams.
*Testing benefit hypotheses is an activity that occurs in the Continuous Exploration step of the Continuous Delivery Pipeline, where Product Owners and Product Managers collaborate to validate their assumptions about the customer and the solution.
質問 # 37
システムデモの目的の一つは何ですか？
- A. チームの構築を実証する
- B. インスペクト・アンド・アダプト(I&A)イベントを計画する
- C. フロー、依存関係、リスクを視覚化する
- D. 本番環境に近い状況で完全なソリューションを実証する
正解：D
解説：
The SAFe POPM workbook explains that the System Demo demonstrates progress from the full system and should be run from a staging environment that resembles production as much as possible. The PI System Demo also demonstrates the current state of the Solution to appropriate stakeholders. This aligns with demonstrating the full Solution in a production-like context , not merely a single team's build.
質問 # 38
完了の定義を確立することがなぜ重要なのでしょうか?
- A. 機能が期待されるビジネス上のメリットを確実に提供する
- B. すべてのアジャイルチーム間で標準化された作業を作成する
- C. ストーリーが完了したときに調整を作成する
- D. スクラムマスター/チームコーチが品質を強化できるようにする
正解：C
解説：
The definition of done specifies the requirements for completeness of a work product or increment of value1.
It is important to establish a clear and consistent definition of done across all Agile Teams to ensure that the work products meet the appropriate quality standards and are ready for integration and delivery23. Without a common definition of done, there may be confusion, rework, delays, and technical debt3.
References:
* What is the Definition of Done (DOD) in SAFe? - Agilemania
* Built-In Quality - Scaled Agile Framework
* Definition of Done - Scaled Agile Framework
質問 # 39
次のイベントのうち、ART が PI 目標の達成に向けてどの程度進んでいるかを示すものはどれですか。
- A. PI 計画
- B. PO同期
- C. 検査と適応
- D. バックログの改良
正解：C
解説：
The event that shows how well the Agile Release Train (ART) is progressing toward meeting the Program Increment (PI) objectives is the Inspect and Adapt (I and A) event. The Inspect and Adapt event occurs at the end of each PI and provides an opportunity for the entire ART to reflect on the progress made during the PI, identify and address the root causes of any impediments, and plan for improvement actions in the next PI1.
* Inspect and Adapt - Scaled Agile Framework
質問 # 40
完了の定義を確立することがなぜ重要なのでしょうか?
- A. 機能が期待されるビジネス上のメリットを確実に提供する
- B. すべてのアジャイルチーム間で標準化された作業を作成する
- C. ストーリーが完了したときに調整を作成する
- D. スクラムマスター/チームコーチが品質を強化できるようにする
正解：C
解説：
The definition of done specifies the requirements for completeness of a work product or increment of value1.
It is important to establish a clear and consistent definition of done across all Agile Teams to ensure that the work products meet the appropriate quality standards and are ready for integration and delivery23. Without a common definition of done, there may be confusion, rework, delays, and technical debt3.
References:
*What is the Definition of Done (DOD) in SAFe®? - Agilemania
*Built-In Quality - Scaled Agile Framework
*Definition of Done - Scaled Agile Framework
質問 # 41
......
SAFe-POPM日本語試験問題と有効なSAFe-POPM日本語問題集でPDF：https://www.goshiken.com/Scrum/SAFe-POPM-JPN-mondaishu.html