Incremental Development - Agile or Plan Driven -


i'm confused in incremental software methodology main difference between incremental development adopt plan driven approach , 1 adopt agile approach ?

can explain me difference between 2 , if choice project?

learning @ core of agile approaches. embraces fact impossible have enough information make detailed plan front. instead implementing, or possibly trying implement, first feature trigger valuable learnings. both implementation , usage , actual needs in field.

i'm not sure "documentations important" means, dividing implementation along module boundaries cause number of unwanted effects:

  • you can learn usage of complete system after modules done, a.k.a. late. drive unknown remaining amount of work after thought done.
  • how know first module done? presumably based on guesswork should do, might right @ least wrong, causes unknown late modifications
  • integration problems show after third module supposed finished

all 3 drive late realizations problems , unknown amount of work left end.

agile focuses on driving out these learnings , information forcing feedback, such integration (as there skeleton 3 modules), user feedback forcing implementation of 1 user level feature @ time demos of them hty ready.

it strategy minimizing risks in software endeavours.

in mind, should have gone agile aproach.


Comments

Popular posts from this blog

gridview - Yii2 DataPorivider $totalSum for a column -

java - Suppress Jboss version details from HTTP error response -

Sass watch command compiles .scss files before full sftp upload -