In a plan-driven process, how is progress typically monitored?

In a plan-driven process, progress is typically monitored against a pre-defined project plan. This approach emphasizes detailed documentation and planning prior to the actual work being done, where measurable milestones and deliverables are established upfront. As the project progresses, the actual outputs and timelines are compared to these initially defined metrics to ensure that the project is on track.

This method allows for structured oversight and provides clear benchmarks for evaluating progress. Regular check-ins against the project plan facilitate identifying deviations from expected outcomes early, making it easier to manage risks and adjust resources or timelines as needed. The focus on a well-defined plan is central to a plan-driven methodology, distinguishing it from more agile approaches that rely on adaptability and iterative progress tracking without strict adherence to a pre-set plan.

The other methods mentioned—customer satisfaction ratings, user acceptance testing, and code reviews—play important roles in the software development process but do not serve as primary metrics for progress monitoring in a plan-driven approach. Customer satisfaction pertains more to the end-user experience after project completion, while user acceptance testing occurs later in the project lifecycle as a means of validating that requirements have been met. Code reviews are an essential part of quality assurance during development but do not provide the comprehensive oversight that a project plan can.