User stories · Persona 4 of 5

Project Manager

Runs one or a few projects day to day as owner or lead, and is also a resource who logs time. Needs to plan and run sprints, keep the team staffed within budget, hold the dates, and keep the status report current, with as little admin as possible.

Goals

A predictable sprint cadence
The right people, at a known cost
Milestones and releases met
A weekly report in minutes

Pain today

Re-keying work from other tools
Sprints planned with unready items
Chasing timesheets and status
Requests arriving by email and chat

Lives in

Project › Board, Backlog, Sprints
Project › Team, Milestones, Releases
Project › Reports and Intake
Timesheets › Team

A sprint in PMO Assist

Plan

Take the suggested scope, run the plan check, fix flagged items, start the sprint.

Run

Daily standup view, board with WIP limits, intake triage as requests arrive.

Review

Sprint insights and burndown; complete the sprint and write the retrospective.

Report

The weekly status generates on schedule; check, publish, present.

Where project managers come from

A Product Manager designation brings the Project manager template, which creates projects under any account. An Account Product Manager, appointed by an account owner, creates projects only under the account where they are Manager. See the walkthrough.

Theme	Stories
Set up and staff	PM-01 · PM-02 · PM-03
Plan and run sprints	PM-04 · PM-05 · PM-06
Commit and deliver	PM-07 · PM-08 · PM-09
Report and time	PM-10 · PM-11 · PM-12

Set up and staff

PM-01

Create a project in one guided step

Asa project manager, I wanta wizard that collects everything and creates it at once, so thatI never end up with a half-configured project.

Acceptance criteria

The wizard has four steps: Details (name, key, description, workflow), Delivery (account, programme, delivery model, workstreams, dates), Integrations, and Review.
Nothing is created until I confirm on Review; a refusal sends me back to that step.
Workstreams (the project, or each epic) are chosen once and can't change.
I become the project's owner; only the owner or an administrator archives or deletes it.

Walkthrough: Chapter 4

PM-02

Bring my Azure DevOps backlog across

Asa project manager whose team used Azure DevOps, I wantto import the backlog with its structure intact, so thatthe team starts without re-keying work.

Acceptance criteria

The connection is tested before the project is created; credentials are stored encrypted.
Hierarchy, area paths, iterations, states, assignees, estimates, tags and dates come across.
Assignees with no account get one and become members, without a login until one is sent.
Re-importing updates what the last import created instead of duplicating it.

Guide: Integrations

PM-03

Staff my project at a known cost

Asa project manager, I wantto add people with hours, dates and a cost per hour, and see how booked they are elsewhere, so thatmy plan matches the people actually available and I know what it costs.

Acceptance criteria

Team › Add people lists people with most free time first and takes project role, access, hours a week, dates and cost per hour.
An allocation that fits is booked at once; one that would overbook becomes an exception for the person's manager.
The Team page shows each member's hours here, how booked they are overall, and what they carry this sprint; Team cost shows planned against actual.
I can ask AI for staffing advice on who should take unowned sprint work.

Walkthrough: Chapter 5

Plan and run sprints

PM-04

Plan a sprint with ready, right-sized work

Asa project manager, I wanta suggested scope and a readiness check, so thatthe team commits to work it can finish.

Acceptance criteria

For a sprint not started, Suggested scope sizes a sprint's worth of backlog work, added in one step.
Plan check flags items with no estimate, no description, too large, or blocked.
I drag backlog items onto a sprint, or use Move to… without a mouse.

Guide: Backlog, sprints and board

PM-05

Run the daily standup from one view

Asa project manager, I wanta person-by-person view of what moved, so thatstandups are quick and consistent.

Acceptance criteria

The Standup view shows one day, person by person, in the same columns for everyone.
The day and person are in the link, so sharing it opens the same round; AI can summarise it.
The board shows column counts against WIP limits and turns red when exceeded.

Guide: Sprints

PM-06

Understand sprint health and close it well

Asa project manager, I wantinsights during the sprint and a clean close, so thatI decide early and lose nothing at sprint end.

Acceptance criteria

Insights shows headline figures and the decisions that need making, each with its items.
The Plan view shows burndown against the ideal line and velocity per sprint.
Complete sends unfinished work to the backlog or next sprint and opens the retrospective.

Guide: Sprints

Commit and deliver

PM-07

Commit milestones and keep a baseline

Asa project manager, I wantto commit dates, update forecasts and re-baseline deliberately, so thatleadership sees honest schedule variance.

Acceptance criteria

New milestone takes a name, workstream, committed date, forecast and an optional link to a release, epic, feature or sprint.
Re-baseline asks for a reason and keeps the old date; Mark achieved records the actual date.
Every project member can read the schedule; changing it needs a lead.

Walkthrough: Chapter 6

PM-08

Plan releases that fill themselves

Asa project manager, I wantreleases with dates that collect their own work, so thatnobody maintains release lists by hand.

Acceptance criteria

New release takes a name, workstream, start, release date and description.
Every open item sits in its workstream's next planned release; Release moves unfinished items on.
The weekly status reads release details from the release, so a shipped date is never retyped.

Walkthrough: Chapter 6

PM-09

Take requests through a form

Asa project manager, I wanta public form that lands in a triage queue, so thatrequests stop arriving by email and chat.

Acceptance criteria

I publish forms with their own questions, and links that expire or never expire and can be revoked.
Every report waits in the queue until a lead accepts it, marks it a duplicate, declines it or marks it spam.
Accepting creates a work item, filed under the epic I chose for the form; the reporter follows progress on a tracking page.

Guide: Intake forms

Report and time

PM-10

Get the weekly status without writing it

Asa project manager, I wantthe report generated on a schedule from what the team did, so thatI spend minutes checking it instead of hours writing it.

Acceptance criteria

I set the weekday, time and time zone the week closes on; only work that moved appears.
Figures are computed; AI writes the highlights and each person's lines. I correct release details and narrative, and arrange or hide workstreams.
The week is a draft until I Publish it; then I present it, export PDF, PowerPoint or Excel, or share it.

Guide: Weekly status

PM-11

Write a delivery report for stakeholders

Asa project manager, I wanta report of where we stand against what was promised, so thatthe client's sponsor gets a clear, honest picture.

Acceptance criteria

Reports › Delivery reports › New report asks only for the period; the facts fill in from the project.
I call the status and write summary, achievements, risks, decisions and next steps; Draft with AI proposes each section.
Each publish is a numbered revision; I share a link for 7 to 90 days or download a PDF.

Guide: Delivery reports

PM-12

See and correct my team's time

Asa project manager, I wantevery member's week on my project, so thatlogged hours are complete for reporting, cost and billing.

Acceptance criteria

Timesheets › Team shows each active member's totals for the week on the project I pick.
I open a member's week and edit, delete or log on their behalf, locked months included.
The project's billable default sets each new log's starting value.

Guide: Timesheets › Team