II.
Workflow JSON
Structured · liveworkflow:sprint-planning-ceremony
Sprint Planning Ceremony json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "workflow:sprint-planning-ceremony",
"_kind": "Workflow",
"_file": "workflows/workflows/workflows-methodology.yaml",
"_cluster": "workflows",
"attributes": {
"displayName": "Sprint Planning Ceremony",
"workflowKind": "governance",
"triggerType": "scheduled",
"typicalCadence": "bi-weekly",
"complexity": "single-team",
"description": "Facilitates the sprint planning ceremony — reviewing backlog priorities,\nestimating story points, negotiating sprint scope with product, assigning\nownership, identifying dependencies, and publishing the sprint commitment.\nExcludes daily standups and sprint execution.\n"
},
"outgoingEdges": [
{
"from": "workflow:sprint-planning-ceremony",
"to": "role:engineering-manager",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:sprint-planning-ceremony",
"to": "role:tech-lead",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:sprint-planning-ceremony",
"to": "role:planner",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:sprint-planning-ceremony",
"to": "skill-area:domain-driven-design",
"kind": "requires_skill_area",
"attributes": {}
},
{
"from": "workflow:sprint-planning-ceremony",
"to": "domain:software-engineering",
"kind": "applies_to_domain",
"attributes": {}
},
{
"from": "workflow:sprint-planning-ceremony",
"to": "responsibility:retro-facilitation",
"kind": "triggers_responsibility",
"attributes": {}
},
{
"from": "workflow:sprint-planning-ceremony",
"to": "org-unit:engineering",
"kind": "performed_by_org_unit",
"attributes": {}
},
{
"from": "workflow:sprint-planning-ceremony",
"to": "org-unit:product-team",
"kind": "performed_by_org_unit",
"attributes": {}
}
],
"incomingEdges": []
}