Question #1
What is a pattern for splitting Features into Stories?
- A . Tasks to complete
- B . Variations in data
- C . Team skills
- D . Layers of the technology stack
Correct Answer: B
B
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
B
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
Question #2
Which of the following statements is one of the five Lean Thinking principles?
- A . Decentralize decision-making
- B . Customer collaboration over contract negotiation
- C . Identify the Value Stream for each product
- D . Deliver working software frequently
Correct Answer: C
C
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
C
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
Question #3
Which is developed by teams and rolled up to the ART level during PI Planning?
- A . Dependencies
- B . Milestones
- C . Objectives
- D . Risks
Correct Answer: C
C
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
C
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
Question #4
What is essential when communicating the Vision?
- A . The importance of empathy interviews
- B . The importance of Feature prioritization
- C . The importance of Lean budget Guardrails
- D . The importance of non-functional requirements
Correct Answer: C
C
Explanation:
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 for the 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
C
Explanation:
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 for the 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
Question #5
What is included in the Inspect and Adapt agenda?
- A . ART Backlog refinement
- B . System Demo
- C . Quantitative and qualitative measurement
- D . Management review and confidence vote
Correct Answer: C
C
Explanation:
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:
C
Explanation:
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:
Question #5
What is included in the Inspect and Adapt agenda?
- A . ART Backlog refinement
- B . System Demo
- C . Quantitative and qualitative measurement
- D . Management review and confidence vote
Correct Answer: C
C
Explanation:
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:
C
Explanation:
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:
Question #5
What is included in the Inspect and Adapt agenda?
- A . ART Backlog refinement
- B . System Demo
- C . Quantitative and qualitative measurement
- D . Management review and confidence vote
Correct Answer: C
C
Explanation:
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:
C
Explanation:
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:
Question #5
What is included in the Inspect and Adapt agenda?
- A . ART Backlog refinement
- B . System Demo
- C . Quantitative and qualitative measurement
- D . Management review and confidence vote
Correct Answer: C
C
Explanation:
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:
C
Explanation:
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:
Question #9
What is a PI Planning input that demonstrates how Product Management plans to accomplish the Vision?
- A . The business context
- B . The ART planning board
- C . The top ten Features
- D . The Team Backlog
Correct Answer: C
C
Explanation:
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
C
Explanation:
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
Question #10
What is one responsibility of the Product Owner during Team Sync?
- A . To add new work into the Iteration
- B . To clarify Story intent
- C . To facilitate the event
- D . To relay Customer feedback
Correct Answer: B
B
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 C PO role within SAFe
B
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 C PO role within SAFe
Question #11
What system delivers a product or service to a Customer?
- A . Kanban System
- B . Operational Value Stream
- C . Development Value Stream
- D . Dual Operating System
Correct Answer: B
B
Explanation:
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.
B
Explanation:
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.
Question #12
What is one influence on Solution and PI Roadmaps?
- A . Value Streams
- B . Customer-centric Features
- C . Market dynamics
- D . ART capacity
Correct Answer: C
C
Explanation:
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.
C
Explanation:
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.
Question #13
What are the minimum requirements for a Feature?
- A . Acceptance criteria, data models, and priority
- B . Name, benefit hypothesis, and acceptance criteria
- C . Benefit hypothesis, acceptance criteria, and priority
- D . Non-functional requirements, data models, and architecture
Correct Answer: B
B
Explanation:
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.
B
Explanation:
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.
Question #14
Which role does Product Management work with to prioritize Enablers?
- A . System Architect
- B . Development Manager
- C . Product Owner
- D . Solution Management
Correct Answer: A
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.
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.
Question #15
What is the next action for improvement items identified during the Iteration Retrospective?
- A . They are entered as Stories in the Team Backlog
- B . They are ROAMed with the rest of the risks
- C . They are given to the Scrum Master/Team Coach who resolves them
- D . They are escalated to the Business Owners
Correct Answer: A
A
Explanation:
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
A
Explanation:
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
Question #16
Which of the following Agile Manifesto principles aligns with conducting a System Demo?
- A . Welcome changing requirements, even late in development
- B . The team reflects on how to become more effective at regular intervals
- C . The best way to convey information is a face-to-face conversation
- D . Working software is the primary measure of progress
Correct Answer: D
D
Explanation:
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
D
Explanation:
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
Question #17
What helps visualize work during PI Planning?
- A . ART PI Kanban Board
- B . ART Planning Board
- C . ART PI Risks
- D . ART PI Objectives
Correct Answer: B
B
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
B
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
Question #18
Why is the problem-solving workshop more effective than traditional lessons learned documents?
- A . Collaboration over documentation is a key recommendation of the Agile Manifesto
- B . It makes improvements actionable through backlog items for the next PI
- C . It involves a small group of leaders
- D . Workshops are more engaging than document writing
Correct Answer: B
B
Explanation:
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
B
Explanation:
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