work-organisation

Design and enforce owner-based Azure DevOps work-item hierarchies with area paths and iterations.

Updated Mar 31, 2026

Search Tags:#feature #iterations #epic #azure-devops #work-items #pbi #area-paths

Ready to run

npx skills add https://github.com/shellicar/skills --skill work-organisation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work-organisation
Source: https://github.com/shellicar/skills/tree/main/skills/work-organisation
Command: npx skills add https://github.com/shellicar/skills --skill work-organisation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Azure DevOps work-item governance often leads to unstable hierarchies where Epics are tied to technologies or motives that drift over time. This Skill enforces a stable, owner-based three-dimensional model to keep strategy aligned with delivery.

Core Features & Use Cases

Defines a three-dimensional model: Hierarchy (Initiative → Epic → Feature → PBI → Task) × Area Path × Iteration Path for a stable organizational map.
Provides naming and ownership guidance to keep Epics and Features aligned with business capabilities and responsible teams.
Includes references and example diagrams to visualise current mappings and plan future growth across projects.

Quick Start

Start by reading the governance principles and then run the references scripts to generate the hierarchy diagrams.

Frequently Asked Questions about work-organisation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I stabilize Azure DevOps work item hierarchy when Epics drift over time?▼

To stabilize Azure DevOps work item hierarchy, enforce an owner-based model where Epics align with business capabilities instead of drifting technologies. This approach keeps strategy aligned with delivery by applying governance across hierarchy, area paths, and iterations.

What is the best way to map area paths and iterations in Azure DevOps boards?▼

The best way to map area paths and iterations is applying a three-dimensional governance model. This defines a stable organizational map covering the Initiative to Task hierarchy alongside area paths and iterations for clear ownership.

How do I visualize current Azure DevOps work item mappings to plan future changes?▼

You visualize current Azure DevOps mappings by running reference scripts to generate hierarchy diagrams. These illustrative outputs help you analyze existing structures and accurately plan future growth across projects.

Why should Azure DevOps Epics be tied to business capabilities rather than technologies?▼

Azure DevOps Epics should be tied to business capabilities because technologies and motives drift over time, creating unstable hierarchies. An owner-based model keeps Epics aligned with responsible teams for stable governance.

Do I need an existing Azure DevOps project to use this work item governance model?▼

Yes, this governance model applies to projects already using Azure DevOps boards. It requires an active project environment to enforce the three-dimensional work-item hierarchy and run the visualization scripts.

Can I enforce naming and ownership standards for Features and PBIs in Azure DevOps?▼

Yes, you can enforce naming and ownership standards for Features and PBIs using this governance model. It provides specific guidance to align work items with business capabilities and responsible teams across dimensions.