Plan Driven Developement

Plan Driven Developement

Plan-driven development is an approach to software engineering, where the development process is planned in detail. Plan-driven development is based on engineering management techniques and in the traditional way of managing large software development projects.

A project plan is created that records the work to be done. Who will do it? And the development schedule and the work product.

In a plan-driven approach, iteration occurs within activities with formal documents used to communicate between stages of the process. For example, the requirements will evolve and, ultimately, a requirements specification will be produced. This is then an input to the design and implementation process. In an agile approach, iteration occurs across activities. Therefore, the requirements and the design are developed together, rather than separately.


  1. Requires personal knowledge at the beginning.

  2. Appropriate for big software development projects.

  3. Predictability -The project timeline and cost can be more accurately estimated.

  4. Documentation, expensive documentation is produced at each phase, adding to understanding and future maintenance.


Rigidity -Changes to requirements are often difficult to accommodate once the project underweighs certain changes. Late feedback, Comprehensive process fix the feedback delayed.

Now let us learn about the difference between agile development and plan-driven development.

AspectAgile DevelopmentPlan-Driven Development
Development ApproachIterative and IncrementalSequential and Linear
FlexibilityEmbraces changes throughoutChanges are minimized
RequirementsEvolves during developmentDefined upfront and fixed
Customer InvolvementContinuous collaborationLimited involvement during development
DocumentationEmphasizes working software over comprehensive documentationComprehensive documentation is crucial
Delivery TimeFrequent, small releasesTypically longer release cycles
Risk ManagementAdapts to changes, mitigates risks iterativelyDetailed risk analysis and management plans
TestingContinuous testing throughout developmentTesting at the end of the development cycle
Team StructureCross-functional, self-organizing teamsSpecialized roles and hierarchy
Progress TrackingRegularly assesses progress and adapts plans accordinglyStrict adherence to predefined plans
CommunicationEmphasis on face-to-face communication and collaborationFormal communication channels and documentation
Customer SatisfactionPrioritizes customer satisfaction through early and continuous deliveryFocus on meeting predefined requirements
FeedbackFrequent feedback from customers and team membersLimited feedback until the end of the development cycle
AdaptabilityEmbraces change and adapts quickly to evolving requirementsResistant to changes once the plan is established

Both approaches have their strength and weaknesses and the choice between them depends on factors like project size, complexity, customer involvement, and the level of flexibility required.

This is all about plan-driven development.