Projektplanen

Projektplanen, or the project plan, is a formal document used in project management to describe how a project will be executed, monitored, and closed. It outlines the project’s objectives, scope, deliverables, constraints, assumptions, governance structure, and success criteria, and it serves as a reference and commitment for both the project team and stakeholders.

The plan typically includes the work breakdown structure, a schedule with milestones, a resource plan, a budget, a quality plan, and risk management details. It also defines the communications approach, stakeholder engagement, procurement needs, and the change management process. Baselines for scope, schedule, and cost are established to enable performance measurement and control.

Development and lifecycle: the projektplanen is created during the planning phase after the project charter and is refined as more information becomes available. Once approved, it serves as the baseline for execution and monitoring. It is updated through a formal change control process to reflect approved changes and revised forecasts.

Relation to other artifacts: the project plan references and aligns with documents such as the project charter or mandate, the statement of work, the risk register, the schedule, the budget, and governance guidelines. It provides a comprehensive framework for decision making and performance tracking.

Usage across methodologies: in traditional waterfall projects, the projektplanen tends to be comprehensive and relatively fixed. In agile or hybrid environments, it may be lighter and complemented by product backlogs, sprint plans, and roadmaps, but it remains a central reference for direction and coordination.

Overall, the projektplanen aims to clarify what will be done, by whom, when, and at what cost, and to establish control mechanisms to manage scope, quality, and risk.