Which methodology / model is more efficient for a team to use in a project, Agile or Waterfall?
Share
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
It really varies by project and also depends on the context. Plus, on some projects it makes sense to combine them and take what is referred to as a hybrid approach.
For projects which need a short delivery timeframe and that need to deliver value quickly and often go Agile. Agile is better suited for requirements around lean documentation and Governance as well.
If the project requires more hard deadlines, hard approvals or stage gates, can’t have variations on scope or deliverables then go Waterfall. Waterfall is better suited for projects that extend over longer periods of time.
In some projects you might go Waterfall during the Planning phase and you might switch to Agile during the Delivery or Execution phase.
Torn between using Agile or Waterfall methodology?
The first question would be, is your product or service a deliverable that will benefit from customer feedback to accommodate adjustments, updates or upgrades during the project/product life cycle? If your project falls in this category then use an iterative and incremental process of AGILE.
Agile..No doubt in it.. go for it