Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Waterfall v.s Agile
Transcript of Waterfall v.s Agile
Wojciech Wiśniewski Waterfall = a stage by stage approach for product building. Process 1 Process 2 Final Process Agile = the creative process that anticipates the need for flexibility Process 1 Process 2 Final Process http://setandbma.wordpress.com/2009/04/14/what-is-the-definition-of-%E2%80%9Cagile-methodology%E2%80%9D/ We can take real life examples for a water fall model like an automobile company.
When making a car:
The requirements are fixed or predicted.
No change in the requirements during the process.
Once we complete a stage, we proceed to the next one.
If there is any change in requirements, we have to change our complete system.
That requires extra time and extra money. http://wiki.answers.com/Q/Three_examples_of_waterfall_model We can link the Agile method to Software Development.
When making software:
The requirements are always changing.
Updates are constantly required.
You need to adapt to the the external changes.
If there is any change, you retrace your steps and fix the problem rather than the whole system.
Its cost effective, but may still cost time. One long-term plan changing requirements
change = new start One final product no feedback from customer
no visible progress http://www.slideshare.net/voximate/introduction-to-agile-project-management-and-scrum http://www.projectsmart.com/articles/waterfall-v-agile-how-should-i-approach-my-software-development-project.php Communication Adaptability Forget Waterfall, go Agile