最新 [2025年04月14日]SAFe-POPM日本語試験正確解答SAFe Product Owner/Product Manager POPM (6.0) (SAFe-POPM日本語版)のPDF問題
あなたのキャリアーを稼いで飛躍せよScrum 45問題
質問 # 20
どのようなシステムが顧客に製品またはサービスを届けますか?
- A. デュアル オペレーティング システム
- B. カンバンシステム
- C. 開発バリューストリーム
- D. 運用バリューストリーム
正解：D
解説：
An Operational Value Stream (OVS) is the sequence of activities needed to deliver a product or service to a customer1. Examples include manufacturing a product, fulfilling an order, admitting and treating a medical patient, providing a loan, or delivering a professional service1. An OVS is the system that delivers value to the customer and generates revenue for the enterprise2. In SAFe®, OVSs are the primary focus of the Customer Centricity competency, which aims to understand and meet the needs and expectations of the customer3.
Some additional information that might be helpful for you are:
*The other options (A, C, and D) are not systems that deliver a product or service to a customer, but rather systems or concepts that support or enable the delivery of value.
*A Kanban System is a method of visualizing and managing the flow of work in a value stream4. A Kanban System can be applied to any type of value stream, whether operational or developmental, to improve efficiency, quality, and predictability4.
*A Development Value Stream (DVS) is the sequence of activities needed to convert a business hypothesis into a digitally-enabled solution that delivers customer value. A DVS is the system that develops and supports the solutions used by the OVSs. In SAFe®, DVSs are the primary focus of the Agile Product Delivery competency, which aims to continuously explore, integrate, deploy, and release value.
*A Dual Operating System is a concept proposed by John Kotter that describes the need for organizations to balance the traditional hierarchical structure with a more agile and networked structure. A Dual Operating System enables organizations to exploit their existing capabilities while exploring new opportunities for innovation and growth. In SAFe®, a Dual Operating System is achieved by applying the Lean-Agile Leadership competency, which fosters a culture of learning and empowerment.
質問 # 21
エンドツーエンドの顧客エクスペリエンスを設計するための 1 つの方法は何ですか?
- A. 全体製品思考
- B. フィーチャーストーミング
- C. ジャーニーマッピング
- D. ペルソナ開発
正解：C
解説：
Journey mapping is one method for designing the end-to-end customer experience. It is a visual representation of the steps, emotions, and pain points that a customer goes through when interacting with a product or service. It helps to identify the customer needs, expectations, and goals, as well as the gaps and opportunities for improvement in the current experience. Journey mapping also helps to align the stakeholders on the customer perspective and prioritize the features and solutions that will deliver the most value and satisfaction123 References:
*The expanding role of design in creating an end-to-end customer experience
*End to End Customer Experience: Know and Control its 3 Elements - HEFLO BPM
*How Design thinking Can Shape end to end Customer Experience
質問 # 22
PI 計画中にビジョンをアジャイル リリース トレインに伝達して改良することは、どの SAFe コア バリューをサポートしますか?
- A. 透明性
- B. アラインメント
- C. 人々への敬意
- D. 絶え間ない改善
正解：B
解説：
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
質問 # 23
PI 計画中にチームによって開発され、ART レベルにロールアップされるのはどれですか?
- A. リスク
- B. 依存関係
- C. 目的
- D. マイルストーン
正解：C
解説：
Objectives are developed by teams and rolled up to the ART level during PI Planning. Objectives are a summary of the business and technical goals that the teams and the ART intend to achieve in the upcoming Program Increment (PI)1. During PI Planning, each team creates their own team PI objectives, which are then presented and reviewed by the ART and the stakeholders2. The aggregated team PI objectives form the ART PI objectives, which provide a common vision and alignment for the ART3.
References:
*PI Objectives - Scaled Agile Framework
*PI Planning - Scaled Agile Framework
質問 # 24
機能の最小要件は何ですか?
- A. 受け入れ基準、データモデル、優先順位
- B. 名前、利点仮説、受け入れ基準
- C. 利益仮説、受け入れ基準、優先順位
- D. 非機能要件、データモデル、アーキテクチャ
正解：B
解説：
The minimum requirements for a feature are a name, a benefit hypothesis, and acceptance criteria12. A name is a brief and descriptive phrase that summarizes the feature. A benefit hypothesis is a statement that describes the expected outcome and value of the feature for the customer or user. Acceptance criteria are a set of conditions that the feature must satisfy to be accepted by the customer or stakeholder12.
Some additional information that might be helpful for you are:
*The other options (A, C, and D) are not the minimum requirements for a feature, but rather additional or optional elements that may be included in the feature definition.
*Data models are representations of the data structures and relationships that the feature requires or affects.
Data models are not mandatory for a feature, but they may be useful for complex or data-intensive features3.
*Priority is the relative importance or urgency of a feature compared to other features. Priority is not a requirement for a feature, but it is a factor that influences the feature selection and sequencing4.
*Non-functional requirements (NFRs) are system qualities that guide the design of the solution and often serve as constraints across the relevant backlogs. NFRs are not specific to a feature, but they may affect the feature implementation or testing5.
*Architecture is the design and structure of the system that supports the solution. Architecture is not a requirement for a feature, but it is an enabler that facilitates the feature delivery.
質問 # 25
製品管理がビジョンを達成するためにどのように計画するかを示す PI 計画入力とは何ですか?
- A. チームバックログ
- B. トップ 10 の機能
- C. ビジネスコンテキスト
- D. ART計画ボード
正解：B
解説：
The top ten Features are a PI planning input that demonstrates how Product Management plans to accomplish the Vision. 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. The top ten Features are the highest priority features of the ART backlog, which are derived from the vision and roadmap, and provide the most value to the customers and stakeholders2. By presenting the top ten Features to the Agile Release Train (ART) during PI planning, Product Management communicates the main objectives and scope of the upcoming Program Increment (PI), and guides the teams to plan their work accordingly2. The top ten Features also help align the teams and stakeholders to a shared mission and vision, and foster cross-team and cross-ART collaboration2.
References: 1 Vision - Scaled Agile Framework, 2 PI Planning - Scaled Agile Framework
質問 # 26
バックログ改善の効果を高めるにはどうすればよいですか?
- A. 主題の専門家と個別に会議を開く
- B. チームメンバーを数人含める
- C. 定期的にイベントをスケジュールする
- D. イテレーション計画中にストーリーを洗練する
正解：C
解説：
One of the factors that can increase the effectiveness of Backlog Refinement is to schedule the event on a regular cadence. Backlog Refinement is the process of reviewing, updating, and prioritizing the backlog items to prepare them for future iterations or sprints1. By scheduling the event on a regular cadence, such as once or twice per week, the team can ensure that the backlog is always accurate, relevant, and ready for planning2. A regular cadence also helps the team to avoid cramming too much work into a single session, which can lead to lower quality and reduced collaboration3.
References:
*Team Backlog - Scaled Agile Framework
*Backlog refinement - How I learned to love agile business analysis ...
*Essential Checklist for Effective Backlog Refinement (and What To Avoid ...
質問 # 27
効果的な PI 目標を記述する際の特徴は何ですか?
- A. 値の説明
- B. 重要なストーリーを含む
- C. 重大なリスクの特定
- D. コミットされた機能の一覧
正解：A
解説：
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
ワークフローを表す機能を視覚化するツールは何ですか?
- A. チームカンバン
- B. 継続的デリバリーパイプライン
- C. ユーザーエクスペリエンスデザイン
- D. ストーリーマップ
正解：D
解説：
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
質問 # 29
どの Agile チーム イベントが絶え間ない改善をサポートしますか?
- A. システムデモ
- B. イテレーションの振り返り
- C. チーム同期
- D. 検査と適応
正解：B
解説：
The iteration retrospective is an Agile Team event that supports relentless improvement by allowing the team to reflect on the iteration just completed and to derive new ideas to improve the team's process12. This reflection helps instill the concept of relentless improvement-one of the pillars of the SAFe House of Lean3-in the individuals and the team.
References:
*Iteration Retrospective - Scaled Agile Framework
*SAFe POPM 5 Flashcards | Quizlet
*SAFe Lean-Agile Principles - Scaled Agile Framework
質問 # 30
次のアジャイル宣言の原則のうち、システムデモの実施に一致するものはどれですか?
- A. 開発の後半であっても、要件の変更を歓迎します
- B. チームは定期的に、より効果的に活動するための方法について検討します。
- C. 情報を伝達する最良の方法は対面での会話です
- D. 動作するソフトウェアは進捗状況の主な指標です
正解：D
解説：
The System Demo is an event where the Agile Release Train (ART) demonstrates the integrated and working software to the stakeholders and customers1. The System Demo aligns with the Agile Manifesto principle that states: "Working software is the primary measure of progress"2. This principle emphasizes the value of delivering functional and usable software over comprehensive documentation or adherence to a plan3. The System Demo provides feedback on the quality, usability, and value of the software, as well as the effectiveness of the ART1.
References:
*System Demo - Scaled Agile Framework
*12 Principles Behind the Agile Manifesto | Agile Alliance
*Manifesto for Agile Software Development
質問 # 31
容量割り当ての利点は何ですか?
- A. 異なるタイプのバックログ項目が互いに比較されるのを防ぎます
- B. ポートフォリオ内のすべてのバリューストリームに適切な資金が供給されていることを保証する
- C. 開発者とテスターをイニシアチブに割り当てる
- D. 効果的な時間追跡を可能にします
正解：A
解説：
Capacity allocation is an allocation of work by work item type for an upcoming planning period1. It helps the Agile Teams to balance their investments across different types of backlog items, such as new features, enablers, defects, and technical debt2. One benefit of capacity allocation is that it prevents different types of backlog items from being compared against each other based on their relative value or priority, which can be misleading or subjective3. Instead, capacity allocation allows the teams to focus on delivering value and quality in each work item type, without compromising the other2.
References:
*Capacity Allocation - Scaled Agile Framework
*Team Backlog - Scaled Agile Framework
*How Does SAFe Handle Capacity Planning and Resource Management? - Value Glide
質問 # 32
機能をストーリーに分割するパターンは何ですか?
- A. データの変動
- B. チームスキル
- C. テクノロジースタックのレイヤー
- D. 完了すべきタスク
正解：A
解説：
A pattern for splitting Features into Stories is to use variations in data, which means identifying different types of data that the feature can handle and creating a story for each type. For example, a feature that allows users to upload files can be split into stories for different file formats, sizes, or sources. This way, the stories are independent, testable, and valuable12 References:
*Story - Scaled Agile Framework
*User stories splitting by data variations and interfaces
質問 # 33
ソリューションと PI ロードマップに影響を与えるものは何ですか?
- A. バリューストリーム
- B. ART容量
- C. 市場の動向
- D. 顧客中心の機能
正解：C
解説：
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.
質問 # 34
カンバンボードは何を示していますか?
- A. イテレーションで完了した作業のバーンダウンチャート
- B. チームの作業の蓄積された価値
- C. ボード上の各アイテムの遅延コスト
- D. チームの進行中の作業 (WIP) が多すぎる場合
正解：D
解説：
A Kanban board is a visual tool that helps teams manage the flow of work from start to finish. It shows the steps of the team's workflow, the work items in each step, and the work-in-process (WIP) limits for each step1. A Kanban board demonstrates where a team has too much work-in-process (WIP), which is the number of work items that are being worked on at any given time. Having too much WIP can cause delays, bottlenecks, and waste in the value stream2. By using a Kanban board, teams can identify and resolve the sources of excessive WIP, and optimize their flow and throughput3.
References:
*SAFe Team Kanban - Scaled Agile Framework
*Applying Kanban in SAFe - Scaled Agile Framework
*What is a Kanban Board, and How Do You Use It? - How-To Geek
質問 # 35
顧客に提供される製品、サービス、またはシステムとは何と定義されますか?
- A. 値
- B. 能力
- C. 解決策
- D. エピック
正解：C
解説：
A solution is defined as a product, service, or system delivered to the customer in SAFe. A solution can be a small mobile application built by a single Agile Release Train (ART) or a large automotive system of systems built by a network of Development Value Streams (DVSs) in a supply chain1. A solution may also be an insurance or banking product offered by a financial institution. Solutions can be the products a company sells or the internal products they use to run the business. They may provide direct value to an end-user or may be a component of a larger solution1.
References:
*Solution - Scaled Agile Framework
質問 # 36
複雑なクリティカルパスの課題を管理するための 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
質問 # 37
ビジョンへの入力の 1 つは何ですか?
- A. チームトポロジ
- B. 機能コンテキスト
- C. ポートフォリオバックログ
- D. 顧客からのフィードバック
正解：D
解説：
One input to the Vision is customer feedback. Customer feedback is the information and opinions that customers and stakeholders provide about the solution, its features, and its value proposition1. Customer feedback helps to validate the assumptions, test the hypotheses, and measure the satisfaction of the solution2.
Customer feedback also helps to identify the needs, preferences, and expectations of the customers and stakeholders, which are essential for defining and communicating the Vision3. The Vision is a description of the future state of the solution under development, and it reflects the problem(s) that the solution will solve and the benefits that it will deliver4.
References:
*Customer Feedback - Scaled Agile Framework
*Continuous Exploration - Scaled Agile Framework
*Solution Vision - Scaled Agile Framework
*Vision - Scaled Agile Framework
質問 # 38
......
正真正銘のベスト資料はSAFe-POPM日本語オンライン練習試験：https://jp.fast2test.com/SAFe-POPM-JPN-premium-file.html