手に入れよう！は2025年最新の有効な実践問題であなたのSAFe-POPM日本語試験を合格させる（本日更新された45問)
Scrum POPM SAFe-POPM日本語試験実践テスト問題集解答豪華セットを使おう！
質問 # 12
チームの速度を確立するための 1 つの方法は何ですか?
- A. イテレーション中に完了したストーリーの計画と実際の割合を計算します。
- B. 前回のイテレーションで完了したストーリーポイントの平均を比較する
- C. イテレーションで計画されているすべてのストーリーのストーリーポイントを追加します。
- D. イテレーションで完了したすべての機能のストーリーポイントを追加します。
正解：B
解説：
One method to establish a team's velocity is to compare the average story points completed throughout the previous iterations. This gives an indication of how much work the team can realistically deliver in a given time frame, based on their past performance. To calculate the team's velocity, you can use the following formula: Team velocity = total story points completed / number of iterations. You can also use various charts and tools to visualize the team's velocity and track itsprogress over time1234 References:
*Velocity in Scrum: How to Measure and Improve Performance - Atlassian
*Discover the Concept of Team Velocity - OpenClassrooms
*A Word on Velocity - LeadingAgile
*Increasing Your Scrum Team's Velocity - ClearlyAgile
質問 # 13
容量割り当ての利点は何ですか?
- 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
質問 # 14
エンドツーエンドの顧客エクスペリエンスを設計するための 1 つの方法は何ですか?
- A. フィーチャーストーミング
- B. ジャーニーマッピング
- C. ペルソナ開発
- D. 全体製品思考
正解：B
解説：
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
質問 # 15
次の記述のうち、5 つのリーン思考の原則のうちのどれですか?
- A. 動作するソフトウェアを頻繁に提供する
- B. 各製品のバリューストリームを特定する
- C. 契約交渉における顧客との協力
- D. 意思決定を分散化する
正解：B
解説：
Identifying the Value Stream for each product is one of the five Lean Thinking principles proposed by Womack and Jones in 1996. A value stream is the sequence of activities that deliver value to the customer, from the initial request to the final delivery1. Identifying the value stream for each product helps to eliminate waste, optimize flow, and increase customer satisfaction2.
References:
*The Five Principles of Lean - Project Management Institute
*Value Streams - Scaled Agile Framework
質問 # 16
PI 計画を成功させるために必要なビジョンとバックログを ART が確保できるようにする役割はどれですか?
- A. プロダクトオーナー
- B. 製品管理
- C. リリーストレインエンジニア
- D. リーンアジャイルセンターオブエクセレンス
正解：B
解説：
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
質問 # 17
顧客に提供される製品、サービス、またはシステムとは何と定義されますか?
- A. 解決策
- B. エピック
- C. 値
- D. 能力
正解：A
解説：
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
質問 # 18
SAFe の継続的デリバリー パイプラインの最初のステップでは、プロダクト オーナーとプロダクト マネージャーはどのようなアクティビティを実行しますか?
- A. チームバックログの優先順位付け
- B. アーキテクチャチームに十分な能力があることを確認する
- C. サプライヤー契約の交渉
- D. 顧客にとって価値を生み出すものを仮説する
正解：D
解説：
Hypothesizing what would create value for customers is the main activity of Product Owners and Product Managers in the first step of SAFe's Continuous Delivery Pipeline, which is Continuous Exploration (CE)12.
In CE, they use design thinking to understand the market problem or customer need and the solution required to meet that need12. They start with a hypothesis of something that will provide value to customers, such as a new feature, capability, or enhancement12. They then validate or invalidate their hypothesis through experimentation, feedback, and learning12.
Some additional information that might be helpful for you are:
*The other options (A, B, and C) are not the main activity of Product Owners and Product Managers in the first step of SAFe's Continuous Delivery Pipeline, but rather activities that may occur in other steps or roles.
*Ensuring the Architecture team has sufficient capacity is an activity that may occur in the second step of SAFe's Continuous Delivery Pipeline, which is Continuous Integration (CI)12. In CI, the Architecture team works with the Development teams to ensure the technical quality and integrity of the solution12.
*Negotiating Supplier contracts is an activity that may occur in the fourth step of SAFe's Continuous Delivery Pipeline, which is Release on Demand12. In Release on Demand, the Solution Management team works with the Suppliers to coordinate the release of the solution components that are provided by them12.
*Prioritizing the Team Backlog is an activity that occurs in the Program Increment (PI) Planning event, which is part of the Agile Product Delivery competency3. In PI Planning, the Product Owner works with the Development team and other stakeholders to define, prioritize, and estimate the work items for the upcoming PI3.
質問 # 19
軽減された ART PI リスクを説明する記述はどれですか?
- A. これ以上何もできないので、リスクが発生した場合、リリースが危うくなる可能性があります
- B. 誰かがリスクの責任を負った
- C. 必要に応じて計画を調整する戦略がある
- D. リスクは解決されており、もはや懸念事項ではない
正解：C
解説：
A mitigated ART PI Risk is one that has an agreed-upon plan for alleviation, which may involve changing the scope, schedule, or resources of the PI. This reduces the impact or likelihood of the risk, but does not eliminate it completely
質問 # 20
問題解決ワークショップが従来の教訓文書よりも効果的なのはなぜですか?
- A. ドキュメントよりもコラボレーションがアジャイル宣言の重要な推奨事項です
- B. ワークショップはドキュメント作成よりも魅力的です
- C. 少数のリーダーが関与する
- D. 次のPIのバックログ項目を通じて改善を実行可能にします
正解：D
解説：
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
質問 # 21
必要なときに価値を利用できるようにするにはどうすればよいでしょうか?
- A. オンデマンドリリース
- B. インフラストラクチャ
- C. 継続的デプロイメント
- D. DevOps
正解：A
解説：
Release on Demand is the process that makes value available to customers when it's needed. It is the final aspect of the Continuous Delivery Pipeline, which represents the workflows, activities, and automation needed to guide new functionality from ideation to an on-demand release of value1. Release on Demand allows the business to release the solution to the end users or customers in acontrolled or staggered manner, based on the market and business needs2. Release on Demand enables the enterprise to respond quickly to customer feedback, optimize the timing and frequency of releases, and reduce the risk associated with each release3.
References:
*Continuous Delivery Pipeline - Scaled Agile Framework
*Release on Demand - Scaled Agile Framework
*What is Release on Demand? | Definition and Overview
質問 # 22
アジャイル チームがイテレーション目標を使用するのはなぜですか?
- A. アジャイルチームがPI期間中に達成しようとするビジネス成果を要約する
- B. チームがPI目標に対して責任を持つようにする
- C. チームメンバーとプロダクトオーナーを共通の目的に合わせる
- D. チームが各イテレーションでコミットしたストーリーを確実に達成できるようにする
正解：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
質問 # 23
PI 計画中に初期チーム容量を決定する際の 1 つのステップは何ですか?
- A. すべての時間ベースのキャパシティ調整について、プロダクトオーナー/プロダクトマネージャーの承認を得る
- B. 最近完了した機能のポイントをすべて合計します
- C. 全チームの最終チーム容量を比較する
- D. チームメンバーの休暇日、祝日、研修日ごとに1ポイント減点
正解：D
解説：
One step when determining initial team capacity during PI Planning is to subtract one point for every team member's vacation day, public holiday, or training day. This step helps the team to adjust their capacity based on the actual availability of each team member for the upcoming Program Increment (PI)1. By accounting for the time-based capacity adjustments, the team can plan their work more realistically and avoid overcommitting or underdelivering2.
References:
*PI Planning - Scaled Agile Framework
*How to Improve Your Agile Team's Capacity Planning - Method
質問 # 24
ソリューション ロードマップではどのような時間単位が使用されますか?
- A. 反復
- B. 年
- C. 日数
- D. PI
正解：D
解説：
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.
質問 # 25
どの 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
質問 # 26
次のイベントのうち、ART が PI 目標の達成に向けてどの程度進んでいるかを示すものはどれですか。
- A. 検査と適応
- B. バックログの改良
- C. PI 計画
- D. PO同期
正解：A
解説：
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&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
質問 # 27
次のロールのうち、ART バックログのコンテンツ権限を持つのはどれですか?
- A. プロダクトオーナー
- B. システムアーキテクト
- C. 製品管理
- D. ビジネスオーナー
正解：C
解説：
Product Management is the role that has content authority for the ART Backlog. The ART Backlog is a Kanban system that captures and manages the features and enablers that the Agile Release Train (ART) will implement in the upcoming Program Increments (PIs)1. Product Management is responsible for defining and communicating the vision, value proposition, and features of the solution, as well as prioritizing and refining the backlog items2. Product Management collaborates with stakeholders, customers, architects, and other roles to ensure that the ART Backlog reflects the needs and expectations of the customers and aligns with the strategic direction of the portfolio3.
References:
*ART and Solution Train Backlogs - Scaled Agile Framework
*Product Management - Scaled Agile Framework
質問 # 28
製品管理の責任の 1 つは何ですか?
- A. チームバックログの管理と優先順位付け
- B. ソリューションの構築
- C. 顧客とのつながり
- D. チームの価値提供をサポートする
正解：C
解説：
One of the key responsibilities of Product Management in SAFe is to connect with the customer and understand their needs, preferences, and feedback. Product Management is the voice of the customer for the Agile Release Train (ART) and represents their interests in defining and prioritizing the features and capabilities of the solution1. Product Management also engages withthe customer throughout the product life cycle, conducting market research, validating assumptions, soliciting feedback, and ensuring customer satisfaction2.
References:
*Product Management - Scaled Agile Framework
*The Role of Product Management in the Scaled Agile Framework (SAFe) - iZenBridge
質問 # 29
検査と適応の議題には何が含まれていますか?
- A. 定量的および定性的な測定
- B. システムデモ
- C. 経営レビューと信任投票
- D. ART バックログの改善
正解：A
解説：
The Inspect and Adapt (I&A) agenda in the Scaled Agile Framework (SAFe) is a significant event at the end of each Program Increment (PI), focusing on continuous improvement and adjustment in Agile processes. It comprises three main parts:
1.PI System Demo: This is the first part of the I&A event, intended to showcase all the features developed by the Agile Release Train (ART) over the course of the PI. It typically includes a broader audience and is more formal than regular system demos. Business Owners collaborate with each Agile team to score the actual business value achieved for their Team PI Objectives.
2.Quantitative and Qualitative Measurement: This part involves the collective review of quantitative and qualitative metrics agreed upon by the teams. This review is aimed at discussing data and trends to measure the team's performance. Important metrics like the programpredictability measure are also analyzed, with each team's planned vs. actual business value contributing to this measure.
3.Retrospective and Problem-Solving Workshop: This structured session allows teams to reflect on their performance, identify areas of improvement, and create action plans. It includes identifying improvements, conducting root cause analysis using tools like the "5 Whys" or fishbone diagrams, brainstorming solutions, prioritizing actions, and creating detailed action plans for implementation.
The I&A event promotes continuous improvement, enhanced agility, increased transparency, higher quality outcomes, better decision-making, improved employee engagement, and alignment with organizational goals.
It's essential for both Agile Release Trains and Solution Trains to effectively inspect and adapt their processes for optimal performance and continuous improvement.
References:
*Scaled Agile Framework: Inspect and Adapt.
*Dee Project Manager: SAFe Inspect and Adapt: Supercharge Agile Excellence.
質問 # 30
......
完全版最新の問題集PDFで最新SAFe-POPM日本語試験問題と解答：https://jp.fast2test.com/SAFe-POPM-JPN-premium-file.html