Project Sections
Organize project work into phases, sprints, and workstreams.
Overview
Project sections group work inside a Project. They support predictable navigation and timeline planning.
Key Concepts
Project section
A project section is a container inside a Project. Sections group work into phases, sprints, or workstreams.
How It’s Used
Sections are flexible.
Common patterns:
Phases: Plan, Design, Build, Test, Deploy
Subphases: nested under a parent section
Sprints: Sprint 1, Sprint 2, Sprint 3
Workstreams: Change Management, Data Migration, Integrations
Milestones or other stages
Modeling phases and sprints in Transform
Transform does not use dedicated “Phase”, “Subphase”, or “Sprint” object types.
Use sections instead:
Phase → top-level section
Subphase → child section under a parent
Sprint → section named by sprint (for example:
Sprint 2)Workstream → section grouped by functional area
Section fields and behavior
Typical section fields:
Name
Parent section (for nesting)
Start date / end date (for timeline planning)
Status (if enabled)
Budget (if enabled)
Benefits
Predictable navigation for large Projects
Cleaner timelines in Gantt views
Clearer ownership when sections map to workstreams
Setup Steps
Sections on the Gantt chart
When a section has start and end dates, it shows as a bar on the Gantt chart.
This lets you see phases and sprints alongside individual tasks.
Tip: In many setups, you can adjust section dates directly in Gantt.
Best Practices
Use top-level sections for major phases or workstreams.
Use child sections for subphases and sprints.
Keep section names unique within a Project.
Add dates so timelines stay accurate.
Use a consistent naming pattern across Projects.
Summary
Project sections group work into phases, sprints, and workstreams. Section dates enable clear Gantt timelines.
Related:
Last updated

