Work Items and Delivery Flow
Tasks and typed work items, backlog, iterations, workflow, estimates and completion criteria. Jira types are adapters, not a universal ontology.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
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 Derived, awaiting review
- Done is defined by criteria and evidence
- A tracker container is not a project
- An effort estimate is not actual time
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: All Closed statuses automatically mean a completed and accepted result.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
PMO / руководитель исполнения
Master systems
- Трекер задач
- PPM
- планы и протоколы приёмки
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 Incomplete
Identity and identifiers required Derived, awaiting review
- WorkItem
- WorkItemType
- WorkflowDefinition
- Transition
- Backlog
- Iteration
- Estimate
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- PMI: project/program/portfolio
- Process-based and flow-based organization of work; compare Scrum/Kanban against primary sources
- Tracker object practice: container, issue, workflow and binding to the business initiative
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
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.