Deployment of pmo365 is iterative. That means each deployment (or iteration) is a solution which meets all the essential requirements agreed to with the product owner. Whilst all the essential components (and the entire pmo365 Solution Library) are deployed in the initial sprint, many organisations want to focus on a particular area and then build the solution outwards. For example, the primary focus of fairlife was to bring together project data and user applications on to one platform. Other aspects of the organization, like its financials, have been set aside for a later date.

The iterative approach allows for a gradual implementation, but also provides ample opportunity for consultation and feedback from all stakeholders. Each three week sprint thoroughly tests and reviews the current solution before the work environment is updated. Between sprints, ‘user stories’ record all responses and suggestions from project managers, employees and product owners to maintain and improve your solution. We deliver as many sprints as required to achieve the required functionality. The following represents a typical approach:

Sprint 1: an initial three-week sprint mobilises your key organisational representatives on the platform. The key deliverables are the initial use case (created with the product ‘Owner’, PMO, and Project Managers) deployed to the Power Platform, along with the complete pmo365 Solution Library.

Subsequent sprint cycles (2-x): an additional sprint cycle (or cycles) implement additional solution functionality via consultation with your DevOps Squad (including requests gathered from users and managers in the work environment). pmo365 subscribers have the option of deploying each new iteration directly to the work environment (workplace) or continuing with the test environment. The first step in each subsequent sprint is addressing a log of ‘user stories’ cases. These stories are curated and scheduled for each development cycle according to their priority and the client’s user story points. See our pmo365 Solution Guide for more information.

pmo365 is published on MS App Source as a Microsoft preferred solution. It is not hosted by a commercial partner or owned by a vendor, but deployed to your own Microsoft 365 tenant. The solution is managed and owned by your own internal IT resources with assistance from the pmo365 DevOps and Management Services Teams as required.

A subscription to pmo365 is a single, fixed monthly fee. There are no set-up fees or hidden costs and everything (the IP and all the data) is owned by you, even after your subscription expires. There are three levels of subscription, which may be changed at any time: A Self-managed option (where you manage the entire solution in-house), Co-managed (where one of our DevOps teams remains directly assigned to you and continues to configure and refine the solution to your needs, and provided ongoing training and support), and Fully-managed (where Management Services are provided by pmo365 to help you to maximise pmo365’s capabilities and build the strategic potential of your organization). 

See our pricing page for the latest information, and read our pmo365 Solution Guide to find out more.

Next, fairlife is looking to exploit more of the capabilities of pmo365 by looking into the integration of financials within project management, and perhaps developing its Resource Management capabilities with the appointment of a new Resource Manager later in 2023.

For the moment, however, its ‘lessons learnt’ and assessment documentation is an area of focus, and the PMO is using Reports and Dashboards for regular ‘health checks’ on progress. The auditing functionality was also recently switched on and has been providing useful feedback on user behaviour in the new system – helping to build adoption and showing how it may develop the solution further.