Work Management
The Work Management domain is the core of Wayd, providing capabilities to manage work items across teams with configurable work processes, workflows, and work types. Work items, workspaces, work processes and workflows are synchronized from external systems like Azure DevOps.
How Work Management Connects Across Wayd
Work items are the atomic unit of delivery, connecting teams, sprints, and projects:
- Teams are assigned to work items and see them in the Backlog section. Team dependencies and cycle time are also tracked.
- Sprints provide time-boxed containers for work items. Sprint progress is measured via sprint metrics.
- Projects can be associated with portfolio-tier work items. Projects track work in their Work Items section.
Sections
- Work Items & Workspaces — Creating, viewing, and managing work items within workspaces
- Sprints & Metrics — Team sprints, the sprint backlog, and delivery metrics (velocity, cycle time, completion rate)
- Work Configuration — Work processes, work types, workflows, and work statuses
- Cycle Time Report — Analyze cycle time for team-owned and employee-assigned work items
- Backlog Health Report — Grade a team's backlog for runway, flow, staleness, readiness and ordering problems
- Delivery Forecasting — Monte Carlo forecasts of when work items, objectives, and projects will be done, and how much a team will finish
- Work Distribution Report — Where a team's or a team of teams' completed work went, by portfolio, program, project, strategic theme or work type
Business Rules Summary
| Rule | Description |
|---|---|
| Unique types per process | A work type can only appear once in a work process |
| Process in use | A work process cannot be deactivated while an active workspace uses it |
| Unique statuses per workflow | A work status can only appear once in a workflow, which sets its status category |
| Name immutability | Work status and work type names cannot be changed |
| Managed read-only | Work items in managed workspaces cannot be edited in Wayd |
| Parent tier | Only Portfolio tier work items can be parents |
| Parent level | A Portfolio tier parent must be a higher level than its Portfolio tier child |
| No self-links | Work items cannot be linked to themselves |
| Dependency health | Automatically calculated from predecessor/successor planned dates |
| Project inheritance | Child work items inherit project assignment from parent, except Other tier items |