Hadrone PPM is a ready-made (out-of-the-box) product, meaning its implementation is significantly simpler than custom-developed software or even platform-based software solutions. The focus of the implementation process is on meeting the business needs of the organization rather than the technology itself, which is already in place and functional. The entire configuration of the Hadrone PPM software is done through the user interface, meaning no technical skills are required for this process.
A best practice in IT system implementations (not just Hadrone PPM) is defining deliverables with acceptance criteria, as well as clarifying the involvement of both the Customer and the Contractor. This approach ensures that the Customer knows exactly what to expect as the outcome of the Contractor's work, and how much time and other resources the Customer’s team must dedicate to complete these tasks. While the Contractor is heavily involved, the Customer also has important responsibilities.
Below is an outline of our approach to implementing the Hadrone PPM software, focusing on the IT solution itself (and the rules for its use within the organization). It is important to note that effective implementation also requires managing human change. The final implementation project should also include "additional" tasks, especially on the Customer side, for which the Contractor may provide support.
Another separate consideration involves organizational changes, which may sometimes be required. These include adapting or developing project portfolio management methodologies/processes, as well as adjusting responsibilities and organizational structures. When planning the scope of the implementation, this area should also be analyzed.
Scope and duration of implementation
A typical Hadrone PPM implementation involves the following stages:
- Stage 1: Project preparation,
- Stage 2: Software analysis and configuration,
- Stage 3: User training,
- Stage 4: Projects migration,
- Stage 5: Production launch.
The typical time required for the implementation of Hadrone PPM ranges from 1 to 3 months (including trainings and project migration). For additional services (dedicated integrations, data warehouse building, custom reports, and dashboards), the implementation duration can be longer. In the case of complex implementations with extended additional services, the timeline can even extend to a year or more. This article describes a "standard" implementation without additional services, which always requires individual analysis and planning.
Below is a breakdown of the stages of the implementation process and the deliverables for each stage.
Stage 1: Project preparation
The scope of work in Stage 1 includes:
- delivering Hadrone PPM software and support in its installation (On-Premises model) or launching the software in the cloud (SaaS model),
- preparing the project plan and assembling a project team from both the Customer and Contractor sides,
- conducting a kick-off meeting.
As a result of the work carried out in Stage 1, the following products are delivered:
- P1.1: Hadrone PPM software with documentation (On-Premises model).
- P1.2: Project plan and kick-off.
- P1.3: Installed Hadrone PPM software on the Customer’s infrastructure (On-Premises model).
- P1.3: Activated access to Hadrone PPM in the cloud (SaaS model).
The following tables present descriptions of the delivered products provided in Stage 1.
Table. Description of the product „P1.1. Hadrone PPM software with documentation (On-Premises model)".
Description of product delivery by the Contractor |
|
Customer's role in delivering the product |
|
Acceptance criteria for the product |
|
Table. Description of the product „P1.2. Project plan and Kick-off".
Description of product delivery by the Contractor |
|
Customer's role in delivering the product |
|
Acceptance criteria for the product |
|
Table. Product description „P1.3. Hadrone PPM Software installed on the Customer's infrastructure (On-Premises model)".
Description of product delivery by the Contractor |
|
Customer's role in delivering the product |
|
Acceptance criteria for the product |
|
Table. Product description „P1.3. Activated access to Hadrone PPM software in the cloud (SaaS model)”.
Description of product delivery by the Contractor |
|
Customer's role in delivering the product |
|
Acceptance criteria for the product |
|
Stage 2: Software analysis and configuration
The scope of work performed in Stage 2 includes:
- analysis of the available Customer's documentation regarding project, program, and portfolio management,
- preparation of the configuration project for Hadrone PPM software,
- configuration of Hadrone PPM software according to the project,
- implementation of the integration between Hadrone PPM and MS Active Directory or MS EntraID, if required by the Customer.
As a result of the work carried out in Stage 2, the product „P2.1. Configured Hadrone PPM software" is delivered.
The table below presents the product description of the work delivered within Stage 2.
Table. Product description „P2.1. Configured Hadrone PPM software”.
Description of product delivery by the Contractor |
|
Customer's role in delivering the product |
|
Acceptance criteria for the product |
|
Stage 3: User Training
The scope of work performed in Stage 3 includes:
- preparation of training materials,
- conducting user training sessions.
As a result of the work carried out in Stage 3, the following products are delivered:
- P3.1. Prepared training materials,
- P3.2. Conducted training sessions for Hadrone PPM software users.
The table below presents the product descriptions of the work delivered within Stage 3.
Table. Product description „P3.1. Prepared Training Materials”.
Description of product delivery by the Contractor |
|
Customer's role in delivering the product |
|
Acceptance criteria for the product |
|
Table. Product description „Conducted training sessions for Hadrone PPM software users”.
Description of product delivery by the Contractor |
|
Customer's role in delivering the product |
|
Acceptance criteria for the product |
|
Stage 4: Projects migration
The Contractor's support in migrating the Customer's projects is optional. Some Customers choose to manually enter projects by Project Managers. This manual work is also an opportunity to organize and standardize project descriptions (including schedules and budgets).
However, if the Customer decides that the current projects need to be migrated, we use our proven migration method, which allows project data to be transferred without disrupting users' work. Typically, structured project data is provided to us at the end of the day on Friday, and by Monday morning, the organization can work in the new environment filled with its project data.
The scope of work performed in Stage 4 includes:
- preparation of Excel sheets to collect data for project migration, along with instructions for filling them out,
- (optional) preparation of rules for creating project schedules in MS Project format for migration,
- migration of data for current projects into Hadrone PPM software.
As a result of the work carried out in Stage 4, the product „P4.1. Migrated Projects" is delivered.
The table below presents the product description of the work delivered within Stage 4.
Table. Product description „P4.1. Migrated Projects”.
Description of product delivery by the Contractor |
|
Customer's role in delivering the product |
|
Acceptance criteria for the product |
|
Stage 5: Production launch
The scope of work required for the production launch depends on the software usage model (On-Premises or SaaS) and the procedures in place at the Customer's organization. In the simplest case, this is just a summary and documentation of the implementation work results. Some organizations conduct acceptance tests and security tests during this stage. Acceptance tests (also known as UAT) aim to confirm that the software has been implemented according to the business needs of the users. Security tests aim to verify and confirm that the implemented software does not have vulnerabilities that would prevent its safe use.
The scope of work performed in Stage 5 includes:
- preparation of test case descriptions for acceptance tests (UAT),
- removal of any critical and high vulnerabilities, if they are discovered during the Hadrone PPM software security tests,
- preparation of post-implementation documentation.
As a result of the work carried out in Stage 5, the product ,,P5.1. Hadrone PPM software production launched” is delivered.
The table below presents the product description of the work delivered within Stage 5.
Table. Product description „P5.1. Hadrone PPM software production launched”.
Description of product delivery by the Contractor |
|
Customer's role in delivering the product |
|
Acceptance criteria for the product |
|