Which of the following helps ensure that requirements remain aligned with business objectives throughout a project?

Requirements traceability is a crucial practice in ensuring that requirements remain aligned with business objectives throughout a project. It involves tracking each requirement from its origin through the development process to the final implementation. This practice allows project teams to understand how requirements connect to business goals and objectives, ensuring that all developed features serve a strategic purpose.

By maintaining a traceability matrix, project teams can continuously validate that the requirements reflect the intended business outcomes as they evolve. If a business objective changes or if there's a new requirement introduced, traceability allows teams to assess impacts and adjust accordingly, minimizing the risk of divergence from business intent.

While other options may have their own roles in project management and can contribute to keeping a project on track, none offer the systematic tracking and validation that requirements traceability provides. Monitoring scope creep helps manage the project scope but does not inherently assure alignment with overarching business goals. Daily stand-up meetings facilitate communication and can highlight any issues, but they don't directly ensure requirements align with business objectives. Implementation of feedback loops is valuable for incorporating user input and improving products but doesn’t specifically track alignment to business objectives over the long term.