SAFE DevOps Practitioner (SDP) Practice Exam

What indicates that a feature has been completed in the Program Kanban process?

1. The feature is approved by stakeholders

2. The feature has been demonstrated to work

3. The hypothesis has been satisfied

4. The feature is documented properly

The correct answer is: The hypothesis has been satisfied

In the context of the Program Kanban process, a completed feature is fundamentally tied to the satisfaction of a hypothesis. This is because each feature is typically associated with a specific hypothesis that aims to address a user need or solve a problem. When the hypothesis has been satisfied, it indicates that the feature has achieved its intended purpose and fulfills the requirements outlined at the start of its development. This concept is central to Agile and Lean practices, where teams continuously test and validate their assumptions to ensure they're delivering value. The success of a feature is gauged not only by its implementation but also by whether it meets the criteria set out in the hypothesis. This focus on value and outcomes reflects an essential principle in the DevOps culture, prioritizing the delivery of working software that brings tangible benefits. The correct answer aligns with the overarching idea of validating assumptions and ensuring that the outputs of work translate into the desired outcomes. Other options—such as the feature being approved by stakeholders, demonstrated to work, or properly documented—are important but do not directly encapsulate the completion criteria defined by the Program Kanban process. These aspects often come after the hypothesis has been fulfilled, indicating that they contribute to the process but are not sufficient on their own to declare a feature fully completed.