← Back to catalogue
Published

Work Items and Delivery Flow

EM-WRK-01 · em-wrk-01

Tasks and typed work items, backlog, iterations, workflow, estimates and completion criteria. Jira types are adapters, not a universal ontology.

Enterprise profiles Enterprise subject EnterpriseWRK

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 5 findings · 10 questions

Work items Typed units of work and the containers that hold them.

Item and type

What a work item is, independent of the tracker that stores it.

Work item identity

A work item with its type mapped from the source tracker.

  1. Which tracker and key identify this item, and what canonical type does it map to?
  2. Is this epic or feature a unit of work, or a product requirement?
  3. Was this item imported before under another key?

Container

The tracker space that holds items, separate from any project.

  1. Which tracker container holds the item, and which business project does it serve, if any?
Flow and completion Workflows, iterations, estimates and what counts as done.

Workflow and transitions

Statuses and transitions with their meaning preserved across trackers.

Outcome status

The outcome an item reached, keeping cancelled, rejected and accepted apart.

  1. Which source status does the item hold, and which canonical outcome does it map to?
  2. Does a closed status mean accepted, cancelled or rejected for this workflow?

Completion and estimate

Done criteria, evidence, estimates and actual effort.

Done evidence

The criteria met and the evidence that the result was accepted.

  1. Which completion criteria apply, and what evidence shows each was met?
  2. Who accepted the result, and when?

Estimate and actual

Planned effort kept separate from recorded time.

  1. What was the effort estimate, in which unit, and what actual time was recorded?
  2. Which iteration was the item planned in, and which did it finish in?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseWRK
Industry
Cross-industry
Tags
EM-WRK-01W1subjectWorkItemWorkItemTypeWorkflowDefinitionTransitionBacklog

What it is Filled

Tasks and typed work items, backlog, iterations, workflow, estimates and completion criteria. Jira types are adapters, not a universal ontology.

Why it exists Filled

Tasks and typed work items, backlog, iterations, workflow, estimates and completion criteria. Jira types are adapters, not a universal ontology.

Distinguishing features Filled

  • Done means that completion criteria were met with evidence, not that a tracker shows a closed status.
  • A tracker container is a storage space for items and is not the same as a business project.
  • An effort estimate is a forecast and never replaces recorded actual time.
  • Tracker-specific item types are adapters mapped onto canonical types, not a universal ontology.

What robots and AI may and may not do Filled

Must not

  • Treat every closed status as a completed and accepted result.
  • Merge cancelled, rejected and accepted outcomes into one status.
  • Report an estimate as actual effort or as hours worked.
  • Declare a tracker container to be a business project.
  • Create a duplicate item when the same source item is imported again.

Only with a human decision

  • Accepting a deliverable on behalf of the customer or product owner.
  • Changing workflow mappings that alter how past outcomes are reported.
  • Using item and effort data to assess an individual's performance.

May

  • Map source statuses and item types onto canonical outcomes and types, keeping the mapping visible.
  • Detect duplicate items on repeated import by source key.
  • Report items that are closed without completion evidence.
  • Compare estimates with recorded actual time per iteration.

Moral aspects Filled

  • Work item data is often reused to judge individuals, which can be unfair without context.
  • Misreported completion can mislead customers and managers about what was delivered.

Who is affected

  • Team members whose work is tracked
  • Product owners and customers accepting results
  • Managers planning delivery

Owners Filled

Steward

The project management office or delivery lead who answers for how work is tracked and accepted.

Master systems

  • Task tracker
  • Project portfolio management system
  • Plans and acceptance records

Links to other meta-models Filled

neighbor

  • EM-COM-04
  • EM-OPS-01
  • EM-RSK-02
  • EM-TEC-05
  • EM-WRK-02
  • EM-WRK-05
  • EM-WRK-06

references

  • WM-ACT-006 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by tracker instance and item key, with a stable canonical identifier across imports.
  • Workflows and item types are identified by tracker, scheme and version.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A work item has a type, a status in a workflow and usually an assignee and a container.
  • Often confused with a product requirement, an incident or the tracker project that contains it.

Capabilities and actions required Filled

  • Items can be moved between workflows with their outcomes mapped explicitly.
  • Flow metrics such as cycle time can be computed from recorded transitions.

Hazards and failure modes required Filled

  • Inflated delivery figures when closed statuses are counted as accepted results.
  • Duplicates from repeated imports that distort flow and capacity data.
  • Loss of meaning when one tracker's statuses are forced onto another's.

Standards and interfaces required Filled

  • ISO 21502 from ISO for guidance on project management.
  • ISO 8601 for dates and durations of iterations and estimates.
  • W3C PROV-O for provenance of acceptance evidence.

Context of use required Filled

  • Used by delivery teams working with trackers in product, project or operational work.
  • Common source for flow metrics, capacity planning and customer reporting.

Sources Filled

  1. PMI: project/program/portfolio
  2. Process-based and flow-based organization of work; compare Scrum/Kanban against primary sources
  3. Tracker object practice: container, issue, workflow and binding to the business initiative
  4. The Scrum Guide - Checked live (HTTP 200) on 2026-10-07.
  5. The Kanban Guide - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • When is an Epic/Feature a work item, and when a product requirement?
  • How is meaning preserved across different source workflows?
  • Which statuses genuinely evidence an accepted result?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-wrk-01/brief.json, ver-cy/world-models/card-supplements/em-wrk-01.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.