Guideline#

This document describes the general guidances for Platform Management based on the concept which is defined Concept Description.

General Hints#

A template of the Platform Management Plan for <Project> is described in the Platform Management Plan Template.

An iterative and incremental development model shall be used.

The project life cycle model shall consider three phases: Concept, Development and Maintenance (compare: Lifecycle concept) Within each phase iterative working model shall be applied.

The traceability shall consider the Traceability concept based on the Building blocks concept.

Templates#

The content of the Platform Management Plan shall consider the Platform Management Plan Template.

Activities for Platform Management Plan#

Create/Maintain Platform Management Plan#

The platform management is created and maintained by the Project Lead (rl__project_lead). As it is a container, this activity is valid for all addressed plan documents.

It may consider:

  • Identifies activities to be performed

  • Identifies the expected, and actual, start and completion date for required activities against progress/completion of activities

  • Identifies dependencies between activities and critical path

  • Has a mapping to scheduled resources and input data

  • Identifies resource allocation, resource workload, and critical resources

  • Information needed to perform

  • Documents ownership for activities e.g., by domains

  • Documents critical dependencies to other work packages

  • Defines/Identifies work products to be generated

  • Documents input and output work products

  • Documents the critical dependencies between defined work products

  • Integration of third party deliveries

  • Applicable standards and legal requirements

Especially for the Project Management Plan, the following topics may considered:

The scope of the work is defined. The scope may include:

  • Roadmap - Main features to be realized including

  • Schedule - target delivery date and major milestones

  • Release dates including major summary of deliverables

  • Operational environment, infrastructure

  • Reference Hardware, Project Samples

The stakeholders/stakeholder groups and organisation are defined. These may include:

  • Involved parties

  • Weight/importance of each stakeholder (group)

  • Representative(s) for each stakeholder (group)

  • Information needs of each stakeholder (group)

  • Required competences, skills, knowledge

Communication and reporting pathes are described. These may include:

  • E-mails

  • Collaboration tools, like Slack, Teams, etc.

  • Meetings and Meeting Notes

  • Blog

  • Webpages

Escalation pathes are described. These may include:

  • Defined mechanisms to report and confirm escalation relevant issues

  • Identifies stakeholders to be included in the escalation path

  • Identifies levels of escalation

Training pathes are described. These may include:

  • Tutorials

  • Training materials

  • Online Trainings, Video material

Monitor/Improve Platform Management Plan#

Project Lead (rl__project_lead) is responsible for the monitoring of the work products and activities against the platform management plan. If deviations are detected, the plan must be adjusted. Deviations may include estimates, resources, schedules, plans, interfaces, etc. as defined in the scope of work.

The status of the project is regularly reported.