Author Topic: Agile & Traditional Models  (Read 525 times)

Bhanu Teja Nukala

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Agile & Traditional Models
« on: August 24, 2018, 02:27:05 am »
What are the differences between agile and traditional project management models?

1181279905

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Agile & Traditional Models
« Reply #1 on: August 27, 2018, 07:52:06 pm »
Traditional project management specifically emphasizes on conducting a long and detailed upfront planning for all projects irrespective of whether the requirements are known or not.While Agile is a general approach used for software development, agile emphasizes on teamwork, frequent deliveries of working software, customer collaboration, and time boxing events and allowing the ability to respond to change quickly.

Adithya Mahendra

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Agile & Traditional Models
« Reply #2 on: February 25, 2019, 10:09:35 am »
Traditional SDLC models such as Sequential, Iterative and Evolutionary have the product being completed in the end of the project, though the Iterative and Evolutionary portray a prototype of the product at end of each phase, whereas in AGILE the product is delivered instantly (depending on the timeline of the SPRINT). There is no documentation in  AGILE as requirements may get manipulated through this process due to the presence of a middleman, hence giving the developers a better understanding of the requirements. And since the requirements are delivered in a very short period of time, there is no concept of a change request management. If there is a change request from the client then the SCRUM team shall take it up in the next SPRINT.

1191940001

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Agile & Traditional Models
« Reply #3 on: March 30, 2019, 02:46:25 pm »
                     Agile                                                                                             Traditional

No Clear Idea about the final Product                                  Very clear idea about the final product.
 
Providing an increment is given more                                   Quality is given more importance than producing the result quickly.
importance than quality.                                        

Change is expected and hence can be                                 Change is supposed to be avoided or controlled as change can  completely
added in future as needed.                                                   affect the baseline of the project."