2025 | PMO Goals and Priorities


1. Implementation

Goal

Measurement

Priority

Deadline

Support projects

  1. Support portal

  • Support portal in Jira is set up.
  • Develop instructions for PMs.
  • Develop instructions for clients.
  • Support portal is used by clients and support PMs by the end of the year.
  1. Documentation – creare/maintain documentation of support projects (where relevant)

  • Develop the structure of standard set of documents for support projects
  • Develop templates and instructions
  • Implement the procedure with the support PMs.

TimeTracker

  • Implement Projectrack functionality in the internal TT to make reporting more automatised and efficient.
  • Implement more detailed stats in the TT functionality.
  • Finish the development of the estimator.
  • Finish the development of the finance system.
  • Create a storage for general passwords that are not related to a specific project.

Reccurent performance reviews for the PM team

  • Create a KPI system for the team and define a set of metrics to track

Data-driven decisions

  • Define a set of project metrics to track (for the dev team) and implement the process
  • Strart using diagrams and other tools to monitor processes on the projects
  • Create a general complain approach on what diagrams should be used and how
  • Prepare instruction on the tools and process

2. Processes

Goal

Measurement

Priority

Deadline

Jira

  1. Configuration

  • Develop a set of standaridised workflows, screens, layouts for different types of projects.
  • Develop an instruction for configuring projects at the start.
  • Improve the tasks management flow
  1. Templates

  • Unify tickets layout and fields, add convenient and useful templates
  •  
  1. Data clean-up

  • Update the existing boards, resolve old tasks, and keep updated the future ones

Estimation

  1. Estimation process

  • When the estimator is finished – standardise points and/or services that must be included into the estimation
  • Develop documentation for the pre-sale phase of the projects, detailing the steps on documents, payments, etc.
  1. Team

  • Improve the estimation procedure, make it more accurate, including using estimates by exact developers or using coefficients.
  • Develop a procedure of forming the project team, according to the projects complexity and developer’s competencies.

Risk Management

  • Develop general structured approach to risk management

General

  • Develop templates and checklists for every stage of the project

Project Management

  • Document all project management-related documents and instructions
  • Implement unified way to write and store project documents
  • Classify developer’s skills – level, experience with integrations, tech stack, etc.

QA process

  • Develop a process of QA
  • Develop a document-explainer for clients on our process

Projects

Agreements

  • SOW for every project
  • Client briefing to get all the info on requirements, design, etc.

Projects set up and flow

  • Jira templates with filled tasks
  • Agree on the template for different issue types
  • Tasks decomposition – structure, issue types, etc.
  • Implement the procedure to leave comments for every status change
  • Implement risks metrics

Documents

  • Develop project documents for every stage of project
  • Renew the template of project passport and keep it in TT
  • Rate matrix, finance info to calculate COGS

Inside the team

Team

  • Team traditions – monthly calls

Calls

  • Change the structure of dailys, to get everyone more involved
  • Different techniques for hosting daily

Workshops

  • Tech workshops
  • Finance workshops
  • Case studies about projects

Performance review

  • 1-1 for team, performance review

Clients

Communication

Metrics

Documents & Agreements

Comments

Leave a Reply