
検証済みのSAFe-POPMテスト問題集と解答で正確な45問
Scrum SAFe-POPMテストエンジンPDFで全問無料問題集
質問 # 13
What is one responsibility of the Product Owner during Team Sync?
- A. To add new work into the Iteration
- B. To relay Customer feedback
- C. To facilitate the event
- D. To clarify Story intent
正解:D
解説:
Explanation
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
質問 # 14
What is one benefit of capacity allocation?
- A. It enables effective time-tracking
- B. It prevents different types of backlog items from being compared against each another
- C. It ensures all Value Streams in the Portfolio are appropriately funded
- D. It allocates developers and testers to an initiative
正解:B
解説:
Explanation
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
質問 # 15
What unit of time is used on Solution Roadmaps?
- A. PIs
- B. Iterations
- C. Years
- D. Days
正解:A
解説:
Explanation
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.
質問 # 16
What is one tool that visualizes Features representing a workflow?
- A. Story Maps
- B. Continuous Delivery Pipeline
- C. User Experience Design
- D. Team Kanban
正解:A
解説:
Explanation
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
質問 # 17
What is a pattern for splitting Features into Stories?
- A. Variations in data
- B. Team skills
- C. Layers of the technology stack
- D. Tasks to complete
正解:A
解説:
Explanation
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
質問 # 18
What helps visualize work during PI Planning?
- A. ART PI Risks
- B. ART PI Objectives
- C. ART Planning Board
- D. ART PI Kanban Board
正解:C
解説:
Explanation
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
質問 # 19
What is one method to establish a team's velocity?
- A. Calculate the percentage planned versus actual Stories completed during an Iteration
- B. Add the Story points for all the Stories planned for the Iteration
- C. Compare the average Story points completed throughout the previous Iterations
- D. Add the Story points for all Features completed in the Iteration
正解:C
解説:
Explanation
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
質問 # 20
Which role does Product Management work with to prioritize Enablers?
- A. System Architect
- B. Solution Management
- C. Development Manager
- D. Product Owner
正解:A
解説:
Explanation
Product Management works with System Architect to prioritize Enablers, which are backlog items that extend the architectural runway of the solution under development or improve the performance of the development value stream1. System Architect provides technical guidance and enablement to the Agile Release Trains (ARTs) and helps identify and define the enablers needed to support the features and capabilities2. In collaboration with System Architect, Product Management negotiates capacity allocations that balance the concentration of business and enabler features in the ART backlog3.
Some additional information that might be helpful for you are:
*The other options (B, C, and D) are not the role that Product Management works with to prioritize Enablers, but rather roles that have different responsibilities or collaborations with Product Management.
*Development Manager is a role that supports the Development teams in building quality solutions and fosters a culture of technical excellence and innovation4. Development Manager may work with Product Management to provide feedback on the feasibility and effort of the features and enablers, but not to prioritize them.
*Product Owner is a role that represents the customer and stakeholders to the Development team and defines and accepts the work items in the Team Backlog. Product Owner may work with Product Management to align on the product vision and roadmap and to decompose the features and enablers into stories, but not to prioritize them.
*Solution Management is a role that is responsible for defining and delivering complex solutions that require multiple ARTs and Solution Trains. Solution Management may work with Product Management to coordinate the dependencies and interfaces between the solutions and the products, but not to prioritize the enablers.
質問 # 21
Which of the following roles has content authority for the ART Backlog?
- A. Product Management
- B. Product Owner
- C. System Architect
- D. Business Owner
正解:A
解説:
Explanation
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
質問 # 22
What is one input to the Vision?
- A. Feature context
- B. Customer feedback
- C. Team topologies
- D. Portfolio Backlog
正解:B
解説:
Explanation
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
質問 # 23
Which of the following statements is one of the five Lean Thinking principles?
- A. Deliver working software frequently
- B. Identify the Value Stream for each product
- C. Decentralize decision-making
- D. Customer collaboration over contract negotiation
正解:B
解説:
Explanation
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
質問 # 24
What is one step when determining initial team capacity during PI Planning?
- A. Subtract one point for every team member's vacation day, public holiday, or training day
- B. Ensure Product Owner/Product Manager approval for all time-based capacity adjustments
- C. Add together all of the points from recently completed Features
- D. Compare final team capacity across all teams
正解:A
解説:
Explanation
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
質問 # 25
Why do Agile Teams use Iteration Goals?
- A. To hold the team accountable to their PI Objectives
- B. To ensure the team accomplishes the committed Stories for each Iteration
- C. To summarize the business outcomes an Agile Team intends to achieve during the PI
- D. To align the team members and the Product Owner to a common purpose
正解:D
解説:
Explanation
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
質問 # 26
What is one way Kanban boards are used in SAFe?
- A. To manage individual performance
- B. To manage non-functional requirements (NFRs) in the backlog
- C. To manage PI Objectives
- D. To manage WIP limits
正解:D
解説:
Explanation
One way Kanban boards are used in SAFe is to manage Work-In-Progress (WIP) limits. WIP limits are the maximum number of work items that can be in a given state or column of the Kanban board at any time. They help to prevent bottlenecks, reduce waste, improve flow, and increase quality and predictability. WIP limits are applied at every level of the SAFe framework, from the portfolio to the team, to optimize the value delivery123 References:
*SAFe Team Kanban - Scaled Agile Framework
*Applying Kanban in SAFe - Scaled Agile Framework
*What is one way Kanban boards are used in SAFE? a. To manage runway ...
質問 # 27
What is one characteristic of writing effective PI Objectives?
- A. Identifying significant risks
- B. Including critical Stories
- C. Describing the value
- D. Listing out committed Features
正解:C
解説:
Explanation
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
Which Product Owner responsibility supports the team with value delivery?
- A. Fostering Built-in Quality
- B. Understanding market forces
- C. Supporting the Architectural Runway
- D. Testing benefit hypotheses
正解:A
解説:
Explanation
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.
質問 # 29
Which is developed by teams and rolled up to the ART level during PI Planning?
- A. Milestones
- B. Risks
- C. Dependencies
- D. Objectives
正解:D
解説:
Explanation
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
質問 # 30
What is enabled by the Continuous Delivery Pipeline?
- A. End-to-end testing
- B. New functionality delivered more frequently
- C. A predictable release cadence
- D. Transparent measurements
正解:B
解説:
Explanation
The Continuous Delivery Pipeline enables the delivery of new functionality to customers more frequently by streamlining and automating the workflows, activities, and feedback loops from ideation to release1. The Continuous Delivery Pipeline consists of four aspects: Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand2. These aspects work together to support the delivery of small batches of new functionality, which can be released to the market based on the customer demand and business needs3.
References:
*Continuous Delivery Pipeline - Scaled Agile Framework
*Continuous Delivery Pipeline - Scaled Agile Framework
*SAFe Continuous Delivery Pipeline: A Comprehensive Guide to the ...
質問 # 31
......
100%合格率保証付きの素晴らしいSAFe-POPM試験問題PDF:https://www.passtest.jp/Scrum/SAFe-POPM-shiken.html
手に入れよう!最新SAFe-POPM認定有効な試験問題集解答:https://drive.google.com/open?id=1ZHPYoopFf1IMcdvHuYhbM9Q4BKhr_KpU