The Digital Practitioner Body of Knowledge: Foundation Concepts
This domain covers the DPBoK Standard itself: what it is, how it is organized, and the vocabulary the Foundation exam uses. Questions here test whether you can place a scenario inside the framework and pick the practitioner-appropriate response - not whether you can configure a toolchain.
What the standard is
- A vendor-neutral standard from The Open Group, published as DPBoK Standard, Version 1.0 (2019), describing the knowledge a person needs to create and operate digital products.
- "Digital practitioner" is deliberately broad: product people, engineers, operations and support staff, data and security specialists, and the managers who fund and govern them.
- It is a body of knowledge, not a method. It does not mandate Scrum, SAFe, or a particular cloud platform; it describes what competent practice looks like and leaves method choice to the organization.
- It complements other Open Group standards - TOGAF for enterprise architecture, IT4IT for the IT operating model - and takes a product-and-value view rather than an architecture-governance view.
Scope as the organizing device
The same concerns recur at nested scopes: the individual practitioner, the team, and the enterprise (including partners and the wider ecosystem).
- Individual: craft, skills, ethics, continuous learning, personal ways of working.
- Team: cross-functional, self-organizing, product-oriented, owning outcomes and using flow and fast feedback.
- Enterprise: funding and portfolio decisions, platforms and architecture, risk, data governance, and how teams stay connected to customers.
Exam implication: identify the scope in the stem before you choose an answer.
Recurring themes
Product over project; value streams and flow; automation and continuous delivery; data as an asset; security and compliance handled continuously; platforms treated as products.
Worked example
A firm funds twelve-month projects, hands work off between development and operations, and responds to outages by blaming individuals. What does the body of knowledge point to? The symptom is technical, but the cause is enterprise-scope: a project funding model and a team topology that break ownership at the handoff. The practitioner-appropriate answer is persistent, cross-functional product teams with end-to-end ownership, funded against products or value streams. Buying better monitoring is a team-scope partial fix and does not remove the handoff.
Traps that cost marks
- Treating DPBoK as a prescriptive methodology with mandated ceremonies.
- Answering at the wrong scope: an enterprise funding problem answered with a team tooling change.
- Equating "digital" with "the IT department" rather than business models and customer outcomes enabled by technology.
- Confusing DPBoK's purpose with TOGAF's architecture governance remit.
- Choosing the tool answer when the stem describes an organizational or ownership problem.