B · Business understanding and domain modeling
Product and project model
Expressing a product or project as objects, boundaries, and states others can discuss.
Classification boundary
Include: Include questions that model products, projects, domain objects, boundaries, states, and relationships.
Choose a neighboring leaf when: Use B for representing objects and rules, and C for whether work is worth doing and how to trade off outcomes.
This capability may appear in standards across different stages. Explore stage expectations
28 questions
Choose a group based on the evidence you need. Groups follow existing question formats, not difficulty or mandatory prerequisites. Each batch has up to eight questions.
Judgment and options25
Compare goals, constraints, options, and trade-offs.
Questions 1–8
- Map the area you have owned over time: what users are trying to do, where the main process obstacles are, what your module can influence, and what is outside its control.
- Where does your project sit in the wider business? Who gives it input, who uses its results, and who is affected if it is late or wrong?
- After a promotion ends, operations considers the campaign complete, product sees orders still being fulfilled, and finance says settlement is not yet possible. How would you define each party’s objects, states, and state transitions?
- Teams define “done,” “awaiting acceptance,” and “paused” differently, distorting roll-up data. How would you design a shared state model and transition rules?
- A user can belong to several organizations and hold different roles in each. How would you model identity, membership, and permissions without conflating accounts with business roles?
- An order moves through created, awaiting confirmation, processing, partially fulfilled, canceled, and refunded states; different pages and services interpret “complete” differently. How would you model state, events, and valid transitions so each client does not invent its own meaning?
- An enterprise customer uses one contract for several departments; employees may work across departments, and administrators may operate on behalf of multiple accounts. How would you distinguish organizations, contract accounts, individual identities, memberships, and authorization scope?
- A cross-team project launches on schedule, but user feedback, operating costs, and data corrections remain; the project team is about to disband. How would you model product, platform, operations, and project responsibilities after delivery?
No questions in this section match your target. ·
Questions 9–16
- A product feature is configured by customer contract, adjusted by experiment group, and constrained by regional rules; analysts need to explain which combination shaped a user's experience. How would you model configuration sources, scope, effective time, and decision provenance?
- A plan includes entitlements, users can purchase add-on capacity or receive temporary campaign credits, and contract changes may require manual compensation. How would you distinguish entitlement definitions, granted balances, sources, expiry, and consumption records?
- A cross-team objective spans several projects, each with routine tasks, risks, and incidents; retrospectives struggle to trace which decisions and work drove an outcome. How would you model relationships among objectives, projects, work items, events, and evidence?
- Business users can edit rules ahead of time, schedule them after approval, and still have older versions referenced by some users and asynchronous jobs. How would you model draft, review, publication, effective time, and rollback?
- An accountant uses one identity to manage several legal entities, each with separate contracts, invoices, and approvers; some group reports allow cross-entity summaries. How would you model identity, membership, resource ownership, and cross-entity access?
- Several users file cases about one incident. Some can share a resolution, but each has different contract deadlines, communications, and compensation eligibility. How would you model the parent issue, linked cases, individual commitments, and closure criteria?
- Plans sold through different channels share a display name but have different features, quotas, and renewal terms; users may switch channels during an upgrade. How would you distinguish the catalog display, sellable offer, contract version, and effective entitlements?
- An employee creates a project space and later hands it to another owner; the department manager still approves its budget, while audit requires the original creator to remain visible. How would you separate resource ownership, operational responsibility, authorization, and historical attribution?
No questions in this section match your target. ·
Questions 17–24
- An enterprise plan includes seats, feature modules, and regional restrictions. The customer adds and removes seats mid-term. How would you model the contract, entitlements, usage, and change history?
- A service depends on platform capabilities, partner fulfillment, and the customer’s own process. The owner wants to know where failures occur. How would you map the parties, commitments, handoffs, and outcomes?
- A user may try a service, subscribe, pause, and later return. Product, operations, and finance count different events. How would you define lifecycle stages and transition rules?
- A feature serves newcomers, administrators, and expert users, each with different obstacles. How would you separate shared needs from role-specific needs without forcing them into one solution?
- Sales materials combine several features into one offer, while entitlements and service levels live in separate configurations. How would you map the customer promise to verifiable product capabilities?
- A partner replaces manual review with batch processing. Wait time drops, but exceptions appear later. How would you decide whether customer workflows, service promises, and internal operations should change together?
- Three business teams need similar approval capabilities. Some want a shared platform; others fear an abstraction layer will slow delivery. Which user tasks, change patterns, and governance costs would guide the boundary?
- Conversion rose after a product redesign, while the service team also changed its workflow. How would you model the shared outcome without attributing it only to the online funnel?
No questions in this section match your target. ·
Questions 25–25
No questions in this section match your target. ·
Experience and reflection3
Use past facts to examine contribution, results, and learning.
Questions 1–3
- Write a one-page product overview for someone who just joined. How would you mark which statements are fact, which are inference, and which are simply unanswered questions?
- A customer-facing capability spans identity, billing, notifications, and data teams. Each team can explain its local behavior, but no one owns the end-to-end promise. How would you define interfaces, owners, and acceptance boundaries?
- A proposal repeatedly refers to “core users” without identification rules, observation windows, or exclusions. What would you clarify so the team can study the same population?
No questions in this section match your target. ·
No questions in this capability match your target. ·