Create and manage a project¶

Use Projects to establish a delivery record, find it in the portfolio, and manage its overall lifecycle.

This is the intended journey from the inspected Final Screens. The frontend is still being connected. The current preview uses sample projects; its local controls and demonstration states do not confirm a saved project or lifecycle change. The steps below need a connected implementation and a successful saved-state check before they can be accepted as a live operating guide.

Before you begin¶

Confirm that you are in the intended workspace and have permission to view projects. Creating, changing setup or changing lifecycle requires project-management permission. Your job title, project ownership or participation is not a substitute for that permission.

Prepare a meaningful reference and title, the intended outcome, the delivery approach, any known dates and the responsible organization. A reference is entered by the creator; this path does not generate one for you. References are stored in uppercase and must be unique within the tenant. Use at most 64 characters for the reference and 256 for the title.

If both dates are supplied, the target must be on or after the start. A missing date is allowed by the backend; it should not be interpreted as an agreed deadline. The description's stored limit is 2,000 characters. Confirm timezone handling in the connected application before relying on a date near a day boundary.

Find and inspect a project¶

1. Open Projects under Delivery & Casework, then the Portfolio view.
2. Enter a reference, title term or description term. Select the relevant status and delivery mode, then choose Apply filters.
3. Compare the result count and summary with those selected filters. Use the page controls to inspect further matches when the connected list supports them.
4. Choose Open project on the intended row. Confirm its reference, title and workspace before taking an action.
5. In Overview, review the saved setup, owner, organization, dates, participants and current state. The intended primary tabs are Overview, Execution, Milestones, Deliverables, Repositories and Report.

The search implementation does not search owner names. A no-match result is also different from a failed or restricted load. Clear an overly narrow filter and confirm the workspace before asking for help; do not create a replacement project solely because a record failed to load.

Overview is intended to combine several sources of delivery information. A missing card, unresolved person name or unavailable evidence section is not proof that the corresponding work does not exist. The complete composition and recovery states still need verification.

Create a draft¶

1. From Portfolio, choose New project.
2. Enter the project reference, title and description. Choose Agile or Plan-driven for the primary delivery mode.
3. Add start and target dates when known. Check the order and the intended local meaning of those dates.
4. Select the owning unit, sponsor position and accountable delivery position where appropriate, using the available organization choices. These organizational fields are optional in the inspected backend; do not invent selections when a lookup is missing or incorrect.
5. Review the setup and choose Create project. The intended Final Screen submits from this form. The frontend preview's extra review navigation is not a verified additional product requirement.
6. After a confirmed save, reopen the saved record and check its identity, Draft state, owner, dates and organization. The creator should be the owner and an initial participant. Creation also adds an initial sprint or phase for the chosen delivery approach.

The inspected setup context offers no project templates. Use direct setup. Although the design mentions adding a template later, this draft cannot promise a template catalog or an available later selection journey.

Leaving the unsaved form is different from cancelling a saved project. No verified unsaved-change confirmation was found in this screen intake. Preserve the information you need before navigating away.

Activate a draft¶

1. Open the saved draft and use its Activate project entry.
2. Review the saved setup, responsibility and dates in the activation screen. Verify the record rather than relying on sample values.
3. Choose Activate project. Activation does not ask for a note in the inspected contract or Final Screen.
4. After a confirmed result, reopen the project and check that it is Active. Agile delivery starts from the intended Board workspace; plan-driven delivery starts from Timeline.

The activation screen also offers Cancel with note, which concerns the saved project. Use it only for a decision to cancel that project. It is not a way to return from the activation page without changing the record.

The saved owner remains the creator, even when another authorized person activates the project. Activation does not itself confirm that a sponsor has approved the project or that separate governance work is complete.

Change setup or lifecycle¶

The backend supports changing the title, description, organizational assignments and dates while a project is Draft, Active or On hold. It does not change the reference, owner or primary delivery mode. A dedicated setup-edit journey and its saved/unsaved states have not yet been verified in this Final Screens intake, so exact button steps are not claimed here.

For an active project, the inspected Overview includes Project actions, an optional Project note, and Put on hold, Complete and Cancel actions. Confirm the project and your intended decision before using one. A note describes that specific action; it does not replace review or approval of the decision.

• Put on hold: record why delivery is on hold, then verify the saved On hold state. Coordinate any required changes to tasks, schedules and linked systems separately.
• Complete: review outstanding work, deliverables, milestones, approvals and evidence first. Record an optional completion summary, then verify the Completed state and closeout information. The action does not enforce that whole checklist for you.
• Cancel: establish the cancellation decision and required follow-up, record an optional reason, then verify the Cancelled state. Do not expect this action to erase the project.

On-hold projects can be activated again, completed or cancelled in the backend. The resume-specific screen and confirmation/result companions still need verification. Resuming clears the current hold reason and preserves the original activation date; that date is not a reliable timestamp for the latest resumption.

There is no verified reopen, archive or delete action in this surface. Completed and cancelled records cannot be setup-edited or reactivated through these controls.

Recover from a problem¶

For support, provide the workspace, project reference, intended action, approximate time and the visible result through an authorized channel. Avoid including confidential project descriptions or personal information in a public request. Support should reconcile the actual saved state and available activity evidence before recommending a retry.

The project overview explains ownership, state meanings and how managers and executives should interpret portfolio counts. Continue with Plan, deliver and review project work for groups, work items, responsibility, completion requirements and review. Governance, repository evidence and other remaining delivery surfaces are still being reconciled.