Project Management

Entry: /projects. Projects owns delivery accountability, participating Teams, work items, milestones, Scrum records and lifecycle. You need the relevant Group and Project permissions; creating a charter also requires an eligible position for its Lead Team. Team participation alone does not grant record access.

Create a Project charter

1. Open Project charter and choose Create Project.
2. Enter the Project Code and name, select the Owning Department and Lead Team, and set the applicable CAPEX/OPEX classification. Complete any required OPEX category.
3. Choose standard, scrum or hybrid delivery and enter the planned dates. Review the accountable Team before creating the charter.
4. Open the Project from Portfolio. Check Charter and participating Teams, then use the permitted actions to add participating Teams or participants as needed.

Organize and update delivery work

1. Open the Project's Delivery board and create a Work Item. Choose its kind, title, priority, assignee, due date and acceptance criteria; select a parent or Sprint where applicable.
2. Use the item's permitted Move Work Item action to move it through backlog, ready, in-progress, review and done as the work actually progresses.
3. For a milestone, record its outcome and reason. For Scrum delivery, complete the Scrum system setup, including the required accountability and Definition of Done, before attempting dependent Sprint or increment actions.
4. Review Risks and Progress and lifecycle history before requesting Project completion. Unresolved work, risks, Sprints or Product Goals can prevent completion.

Accept approved funding

1. Where available, open Funding handoffs and select the current offer for your Group. This view requires both Financial and Project read access.
2. Read the Approved Financial source, including its exact revision, type and amount.
3. In Accept funding into Projects, choose Create Project from Funding and complete the charter, or Link Funding to Existing Project and select a compatible editable Project.
4. Submit and verify the retained acceptance and Accepted Project link. If a response fails, review the existing attempt before creating another charter.

Boundaries: native Project creation does not require a Financial handoff. Funding acceptance never edits Financial amounts; later accepted revisions of the same Budget Request remain associated with its Project. Historical approvals may have no offer, and a newer approved revision can supersede an unaccepted one. If a source or Project version changed, refresh and review it before a new acceptance.