PMO Assist · Docs
V2.5.2

User stories · Persona 1 of 5

Account Owner

A leader who runs one or more client accounts end to end. Needs to set up an account, put the right project manager and team on it, and see how every project under it is doing, without depending on a central admin for each step and without seeing the rest of the organisation.

Goals

  • Stand up a new client fast
  • Hire and staff the team directly
  • Know cost and health per project
  • Brief the client with confidence

Pain today

  • Waiting on admins to create things
  • Staffing and cost in separate sheets
  • Status assembled by hand
  • No single view of the account

Lives in

  • Accounts › the account
  • People
  • Project › Team and Plan
  • Portfolio and Dashboard

A first month in PMO Assist

Day 1

Create the account and programme. Create the project manager and the team. Give the PM the Manager role.

Week 1

Create a project, add people with hours and a cost per hour, set releases and milestones.

Weekly

Read health and needs attention on the dashboard; send the client one deck for every project.

Monthly

Publish an account report for the client sponsor, drafted from the projects' own reports.

How to read these stories

Each story says who wants something, what they want and why. The acceptance criteria describe how PMO Assist 2.5.2 behaves, so they double as an onboarding checklist and a demo script. The Leadership walkthrough shows the same journey as one story.

ThemeStories
Set up the accountAO-01 · AO-02
Build the teamAO-03 · AO-04 · AO-05
Run the projectsAO-06 · AO-07 · AO-08
Oversee and reportAO-09 · AO-10

Set up the account

AO-01

Create a client account and own it

Asan account owner, I wantto create the client's account myself, so thata new engagement starts the day it is signed.

Acceptance criteria
  1. Accounts › New account takes a name and a description.
  2. I become the account's Owner automatically.
  3. I see only the accounts I hold a role on, never anyone else's.

Walkthrough: Chapter 2

AO-02

Group the account's work into programmes

Asan account owner, I wantprogrammes under my account, so thatrelated projects are read and rolled up together.

Acceptance criteria
  1. Add programme on the account's card creates one under that account only.
  2. The new project wizard offers only the chosen account's programmes.
  3. A programme or account still in use is retired rather than deleted; its projects keep it.

Walkthrough: Chapter 2

Build the team

AO-03

Create the people who work on my account

Asan account owner, I wantto create resources and send their logins, so thatmy team can start without a central request.

Acceptance criteria
  1. People › New resource takes name, email, designation, manager and joining date; Import takes a spreadsheet.
  2. Send login now emails a link to choose a password; it can also be sent, resent or revoked later.
  3. People lists only the resources I created, and I manage only those.

Walkthrough: Chapter 3

AO-04

Appoint a project manager for my account

Asan account owner, I wanta project manager who can create projects under my account and nowhere else, so thatI can delegate safely.

Acceptance criteria
  1. I can give the Account Product Manager designation; it carries no template of its own.
  2. Adding that person to the account as Manager lets them create projects under it, lead what they create and read the rest.
  3. I can't give designations that carry organisation-wide rights, such as Product Manager; PMO Assist names what I lack.

Walkthrough: Chapter 3

AO-05

Set the reporting line when I hire

Asan account owner, I wantto choose each person's manager from the people I created, so thatleave and overbooking go to the right person.

Acceptance criteria
  1. The Manager picker offers the people I created.
  2. A manager holds the Line manager template automatically and approves their reports' leave and overbooking exceptions.

Walkthrough: Chapter 3

Run the projects

AO-06

Create a project under my account

Asan account owner, I wantto create projects under my accounts, so thatnew work starts in the right place.

Acceptance criteria
  1. The wizard offers only accounts I may create under; with one, it is chosen for me.
  2. I choose the workstreams (the project, or each epic) once; it can't change later.
  3. I own what I create. The delivery model is set by a delivery manager, a workspace manager or an administrator.

Walkthrough: Chapter 4

AO-07

Work on any project under my account as its lead

Asan account owner, I wantto step into any project under my account, so thatI can fix staffing or the plan without being added to each one.

Acceptance criteria
  1. The account's Owner role lets me edit each project, its work items, sprints, time and settings.
  2. I can add people, change their access and remove them on every project under the account.
  3. Archiving and deleting a project stay with its own owner.

Walkthrough: Who does what

AO-08

Staff a project and know what it costs

Asan account owner, I wanteach person added with hours a week and a cost per hour, so thatI see the team's planned and actual cost.

Acceptance criteria
  1. Team › Add people takes the project role, access, hours a week, dates and cost per hour, and shows the weekly cost as I type.
  2. An allocation that fits is booked at once; one that would overbook goes to the person's manager.
  3. Team cost shows planned cost, actual to date, still to spend and the blended rate, only to those who staff the project.

Walkthrough: Chapter 5

Oversee and report

AO-09

See my account's delivery at a glance

Asan account owner, I wantone page per account with every project's health, so thatI know where to look before the client asks.

Acceptance criteria
  1. The account's Delivery tab lists every live project worst first, with one status, its next milestone and release, and the latest published weekly status.
  2. Health and warnings carry their reasons; the dashboard's key figures say what changed since last week.
  3. Brief me on this account gives a short spoken summary when there are more than three projects.

Walkthrough: Chapter 8

AO-10

Give the client one view of the whole account

Asan account owner, I wantone weekly deck and one periodic report for the whole account, so thatthe client hears one story.

Acceptance criteria
  1. Portfolio › Weekly status exports the selected projects as one file, or shares one public deck.
  2. An account report is drafted from the projects' own published reports, worst first, and published as a numbered revision.
  3. Links can be withdrawn at any time; drafts are never shared.

Walkthrough: Chapter 8

PreviousAccess & governance