A baseline in project management is a fixed reference point used to measure project performance. It represents the approved version of the plan, including the project scope, schedule, and cost, against which actual work is compared. Once these elements are approved, they become the standard for tracking progress, detecting variances, and deciding whether changes require formal change control. This allows you to assess whether the project is on track and manage any deviations effectively, sometimes using methods like earned value management. The other options aren’t baselines: a risk register is a log of identified risks and responses, not the performance reference; a stakeholder list is a communications or stakeholder register; a vendor contract template is a document used for procuring goods or services, not a baseline for measuring performance.

Managing a product through its entire life requires guiding its strategy, development, and ongoing improvements from idea to retirement. This is what product management does: it defines the product vision, sets a roadmap, prioritizes features based on value to customers and the business, and coordinates with design, engineering, marketing, and sales to deliver and iterate on the product over time. The role stays with the product as market needs, competitive conditions, and technology evolve, ensuring the product continues to meet customers’ needs and drive business outcomes. Projects, in contrast, are temporary efforts with specific goals and timelines, not the sustained ownership of a product’s lifecycle. Lifecycle management is often about overseeing processes and data across stages (design, production, support, retirement) but the function that owns and drives the product’s life story and value delivery is product management. Portfolio management focuses on a group of products or projects and prioritization at a higher level, not the end-to-end lifecycle of a single product.

In earned value management, schedule performance is assessed by the ratio of what you’ve earned to what you planned to earn. This is captured by the Schedule Performance Index, calculated as EV divided by PV. If the value is 1, you’re exactly on schedule; above 1 means you’re ahead of schedule; below 1 means you’re behind. For example, if the earned value is 60 and the planned value is 50, SPI is 1.2, indicating ahead of schedule. If EV is 40 and PV is 50, SPI is 0.8, indicating behind schedule. The other metrics relate to cost or to a raw difference rather than a ratio: Schedule Variance is EV minus PV and shows the amount of schedule deviation, but not the rate of progress. Cost-based metrics (CPI and CV) focus on cost performance, not schedule.

Governance and oversight responsibilities that keep initiatives aligned with strategic objectives. Approving actions, monitoring progress, and ensuring alignment are the hallmarks of a governance role: you authorize what will be done, track how it’s progressing, and continuously check that what’s happening matches the intended strategic goals. This keeps resources and efforts moving in the right direction and allows timely adjustments if things drift. In practice, signing off on actions ensures work proceeds only with proper authorization. Regularly monitoring progress means watching milestones, budgets, and risks so you can intervene when needed. Checking alignment with strategic goals ensures that every step reinforces the broader objectives, not just the local tasks. This contrasts with providing resources and direction, which centers on supplying what’s needed and setting overall guidance but not the ongoing governance discipline. Providing business direction and insight focuses on offering strategic context and analysis, not the formal approval and tracking loop. Helping the team solve problems and work smoothly emphasizes collaboration and issue resolution rather than the governance cycle.