APM APM Release Planning & Delivery 2 — Questions and Answers
Question 1: Which practice helps Agile teams minimize the risk of a failed production release?
- Big bang releases once per year
- Feature flags and incremental rollouts to subsets of users (Correct answer)
- Freezing the codebase six months before release
- Avoiding automated testing
Correct answer: Feature flags and incremental rollouts to subsets of users
Feature flags let teams deploy code to production without exposing it to all users, enabling gradual rollouts and instant rollbacks.
Question 2: What is the 'definition of done' (DoD) and why is it critical for release readiness?
- A list of features the product owner wants in the next sprint
- A shared checklist that defines when an increment is truly complete and releasable (Correct answer)
- A synonym for the acceptance criteria of a single story
- A manager's approval sign-off process
Correct answer: A shared checklist that defines when an increment is truly complete and releasable
The DoD ensures every increment meets quality, testing, and documentation standards before it is considered releasable, reducing post-release surprises.
Question 3: In Agile release management, what does 'release cadence' refer to?
- The number of defects per release
- The regular rhythm or frequency at which a team delivers software to production (Correct answer)
- The sequence of steps in a CI/CD pipeline
- The team's sprint ceremony schedule
Correct answer: The regular rhythm or frequency at which a team delivers software to production
A consistent release cadence builds predictability, reduces coordination overhead, and conditions stakeholders to expect regular deliveries.
Question 4: What is the role of an APM practitioner during a release retrospective?
- Writing the next sprint's user stories
- Reflecting on what went well and what to improve in the release process to enable better future releases (Correct answer)
- Presenting the roadmap to investors
- Conducting user acceptance testing
Correct answer: Reflecting on what went well and what to improve in the release process to enable better future releases
Release retrospectives examine the end-to-end delivery cycle, surfacing systemic improvements beyond what a sprint retrospective covers.
Question 5: Which of the following is a leading indicator that an Agile team may miss its release commitment?
- High team satisfaction scores
- Increasing cycle time and growing work-in-progress (WIP) (Correct answer)
- Declining defect density
- Consistent sprint velocity
Correct answer: Increasing cycle time and growing work-in-progress (WIP)
Rising cycle time and WIP signal bottlenecks or scope creep that will erode throughput and threaten the release timeline.
Question 6: What is the purpose of a 'go/no-go' meeting before a production release?
- To plan the next quarter's roadmap
- To assess release readiness criteria and make a collective decision on whether to deploy (Correct answer)
- To conduct performance reviews
- To assign post-release support ownership
Correct answer: To assess release readiness criteria and make a collective decision on whether to deploy
A go/no-go meeting ensures all stakeholders confirm that quality gates, infrastructure checks, and business readiness criteria are satisfied before deployment.
APM APM Release Planning & Delivery 2
Which practice helps Agile teams minimize the risk of a failed production release?