Bring project ownership, team membership, issue types, workflow gates, WIP policy, estimate units, current backlog, sprint history and verified repository/branch mappings.
Implementation
Configure PM for IT Projects around your team’s operating policy.
Implementation phases
- Agree project boundariesProject Lead / Product Owner
- Configure the delivery loopTeam and ERP.ai
- Reconcile historical workTeam and ERP.ai
- Verify live handoffsTeam and ERP.ai
Phase 1 · Project Lead / Product Owner
Agree project boundaries
The Project Lead / Product Owner maps teams, reporter/stakeholder audiences and canonical project roles.
| Role | Screens |
|---|---|
| Project Lead / Product Owner | 13 |
| Scrum Master / Iteration Manager | 12 |
| Developer / Engineer | 6 |
| Stakeholder | 5 |
| Reporter | 1 |
| QA / Tester | 5 |
Role permissionsRoles and permissions →
Phase 2 · Team and ERP.ai
Configure the delivery loop
Version workflows, decision gates, board membership, WIP policy and estimate units.
Phase 3 · Team and ERP.ai
Reconcile historical work
Preserve issue identity, sprint commitments, closure snapshots and release scope.
Phase 4 · Team and ERP.ai
Verify live handoffs
Test authenticated intake, repeated merge events, QA denial and a release containing unfinished work.
Workflow changes affecting active work require the declared co-sign and a reviewed state migration. Preserve issue history, starting commitments, closed outcomes and released scope. A changed issue revision invalidates its affected approval; missing provider evidence stays unresolved.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.