Meisterplan
Key Info:
Meisterplan is project portfolio management software for prioritising initiatives, comparing scenarios, balancing resource capacity and communicating portfolio decisions.
Details
Portfolio planning scope
Meisterplan is project portfolio management software for organisations that need to select initiatives, balance demand with resource capacity and communicate an approved portfolio. Its current official feature set covers project intake, prioritisation, scenarios, portfolio views, roadmaps, financial planning, capacity planning and management dashboards. It is positioned as a portfolio layer rather than a replacement for every team delivery tool.
Evaluation scenario
Import or create a representative portfolio containing proposed, approved and active projects. Add strategic contribution, costs, milestones, dependencies and role-based resource demand. Compare at least two scenarios, approve one plan, then introduce a budget reduction or specialist bottleneck. The trial should show whether planners can explain trade-offs before commitments are changed.
Intake and prioritisation
Test the portfolio-level intake flow with initiatives of different maturity, value and urgency. Configure criteria that reflect the organisation's actual strategy, mandatory work and risk appetite. Review how rankings, manual adjustments and decision notes are preserved. A useful process makes the evidence behind a priority visible instead of presenting a score as an automatic decision.
Scenarios and resource capacity
Create alternatives using different start dates, staffing assumptions and budget limits. Model roles, teams, named people and available capacity at the level that can be maintained. Test part-time availability, shared specialists and delayed hiring. Confirm that overloads can be traced to projects and time periods and that scenario comparison does not overwrite the approved plan prematurely.
Roadmaps, finance and reporting
Build a roadmap with milestones and dependencies, then test how a delayed initiative affects dependent work and strategic outcomes. Add portfolio budgets and project costs, and reconcile totals with the finance system that remains authoritative. Configure dashboards for executives, portfolio managers and resource owners. Reports should reveal stale or incomplete inputs rather than imply unsupported precision.
Integration and governance
Review integrations with existing project and work-management systems against actual ownership rules. Test who can create scenarios, change priorities, approve the plan and edit capacity. Reproduce a decision change and confirm that the rationale is recoverable. The portfolio layer should reduce duplicate reporting while allowing delivery teams to keep appropriate operational tools.
Rollout checkpoint
Start with one portfolio and one real governance cycle. Measure reporting effort, decision lead time, unresolved data issues and late capacity conflicts. Expand only when planners can repeat the process, reconcile finance and resources, communicate an approved roadmap and avoid shadow spreadsheets becoming the practical system of record.