Leadership walkthrough · The story
From sign-in to the client's weekly status
One story, told in eight short chapters. An account owner signs in for the first time, sets up a client account, hires a project manager and a team, starts two projects, staffs them at a cost per hour, plans releases and milestones, gets the work moving, and sends the client a status deck. Each chapter shows where to click, what to fill in, and who is allowed to do it.
The cast
The people and the client are made up. The screens, fields and rules are PMO Assist 2.5.2's own.
Heads retail delivery. Holds the Account owner template. Has no resource profile: Asha oversees and logs no time.
Hired by Asha with the Account Product Manager designation, then made a Manager on the account. Runs day-to-day delivery and logs time.
A developer, a tester and a designer. Created by Asha, reporting to Ravi. They work the board, log time and book leave.
Sales lead for the client. Invited by an administrator, then given the Viewer role on the account. Reads health, plans and published reports.
The account. Its programme is Digital Commerce, with two projects: Card Checkout and Loyalty App.
The chapters
- 1Getting inThe invitation email, choosing a password, signing in, and what Asha sees first.
- 2The account and its programmeAccounts › New account, then Add programme. Asha becomes the account's Owner.
- 3People, and the project managerNew resource for Ravi and the team, reporting lines, logins, and the account's Members.
- 4Creating projectsAsha creates Card Checkout; Ravi signs in and creates Loyalty App. The four-step wizard from both seats.
- 5Staffing, allocation and cost per hourAdd people with a role, hours a week, dates and a cost per hour. Overbooking and Team cost.
- 6Releases and milestonesWorkstreams, releases with planned dates, milestones with a committed baseline.
- 7Work items, sprints and timeEpics to stories, assigning people, the first sprint, the board, and logging time.
- 8Reporting and oversightWeekly status, publishing, the client deck, delivery reports, health and the dashboard.
When you need a quick answer rather than the story, Who does what puts every step against the person who may do it.
Before chapter 1: one step for an administrator
Nobody can make themselves an Account owner. An administrator, or anyone who holds both the right to manage logins and the right to grant permissions, does it once:
- Open People and choose Invite stakeholder. A stakeholder is someone who follows the work and logs no time, so they never appear in capacity, leave or timesheets.
- Fill in Asha's first name, last name and email.
- Under Permissions, choose Account owner. This is the template Asha starts with.
- Leave Send login now on, and choose Invite. Asha receives the invitation email.
If the account owner also logs time, create them with New resource instead and apply the Account owner template from the Access tab on their page. A resource profile also lets them see every resource in the organisation, as every resource can.