While discussing team norms, the team determines that within the Delivery Horizon, communication will be:
A. Clear or reviewed
B. Appropriate and planned
C. Casual and as needed
D. Consistent or scheduled
Planning horizons are important because they allow an organization to:
A. Support a structured response supported by all levels of the organization
B. Sense and respond to their changing environment
C. Ensure senior management is informed and engaged
D. Allow management guidance for decision making
A team demonstrating the following characteristics: Expects rapid change Incorporates learning and feedback Has a preference for shorter time frames Treats plans as testable hypothesis
is following planning practices that are described as:
A. Predictive and adaptive
B. Adaptive and hypothesis
C. Iterative and predictive
D. Iterative and adaptive
After a lengthy discussion the team agrees that the agile business analysis principle of "get real using examples" aligns with the BACCM core concept of:
A. Need
B. Value
C. Stakeholder
D. Solution
The organization has a history of delivering products that often don't resonate with potential customers. After some discussion, the team decides to address this challenge by developing:
A. Metrics and KPIs
B. Personas
C. Project plan
D. Customer call center
The team will be performing its first review and trying to determine what should be demonstrated. After a lengthy discussion they decide to demonstrate:
A. Their response to critical customer feedback
B. Key lines of code that describe the solution
C. Slides of screens to be developed
D. An increment of the working solution
The team realizes it is important that solution components are analyzed:
A. In great detail so as much information as possible is available for subsequent work
B. To provide answers to any potential questions from senior management
C. So enough information is available to meet all stakeholder needs
D. To a level of precision that is just enough to make an informed next decision
All team members participate at a review of their delivery process for the past 2 weeks. They consider issues, both pro and con, that influenced how much the team got done, as well as what they can do to make that better. This meeting is an example of the principle:
A. Understand what is doable
B. Iteration and progression
C. Avoid Waste
D. Stimulate collaboration and continuous improvement
When the product owner determines there has been enough value delivered on the initiative to satisfy the need, then the sponsor's immediate next step is to:
A. Cancel future work on the initiative to avoid waste
B. Start work on the list of enhancements to improve the delivered product
C. Hold individual interviews to collect feedback
D. Dive deeper into the next delivery cycle's stories
A team member has written a full user guide about a feature that has not yet been developed. Shortly before delivery is to start, the feature is dropped. What did the team member forget to value highly?
A. Following the plan
B. Detailed processes
C. Fixed iterations
D. Working solutions
Wanting to ensure the delivery team is working as productively as possible, they decide backlog items, including user stories, should be:
A. Fully detailed before they get prioritized
B. Refined and elaborated by the Tech Lead
C. Refined and elaborated throughout the planning horizons
D. Fully detailed as they enter the backlog
Backlog items that are dependent on other backlog items compromise and limit rapid decision making, fast delivery and strategic alignment by not leveraging:
A. Feedback loops
B. Daily standups
C. Retrospectives
D. Thinking like a customer
The delivery team discusses how to maintain the integrity of their backlog items. They decide to?
A. Delay changes until they are caught up
B. Develop a business case for all changes
C. Monitor stories and features for staleness
D. Ensure all changes are approved
The team is prioritizing stories in the backlog and discussing the elements that result in a well-structured, actionable backlog. They identify the following as a central consideration:
A. Accessibility of key stakeholders for signoff
B. Rapid delivery of value
C. Refining the personas used
D. How many features are in the backlog
While reviewing criteria for a well-written story, the team discusses the following criteria:
A. Detailed persona characteristics
B. Cost-benefit valuation
C. Alignment to the organization's vision statement
D. Achievable unit of development