Agile Project Management

Masters answered everything, Nothing left for me.


You Should Use Waterfall If…
Your client knows exactly what they want, and you’re very confident that there won’t be any major changes in scope throughout the project. Waterfall works great for building software for clients who have clearly defined requirements that aren’t likely to change throughout the life cycle of your project—think government contracts or legacy systems. When projects are simple and predictable, you can benefit from Waterfall’s inherent stability and linear development path.

You Should Use Agile If…
You’re building a new product in an uncertain world and you have a real need for speed. If you don’t have a lot of information up front, enforcing strict requirements and planning at the beginning of your project can lead to costly mistakes further down the line. Agile was designed to reduce the cost of change and uncertainty—which is why it’s no surprise that many startups swear by the methodology. Agile excels when you don’t have a clear picture of the end goal and requirements are constantly changing.

Do not worry Adnan. From 1998 up to date (I mean including my actual work place) organizations hired me to implement Agile and I spent time to helping them to understand that Agile is not what they think it is. I prefer that they say "so, we do not continue" instead being "Dead On Arrive". BUT I do not own the truth then I am spending time here to learn from others comment (people that have written comments above helped me a lot to do that). Then take a look to references like PMBOK Guide V6, Rick Dove´s "Response Ability" book, Manifesto for Agile Software Development if you work with software, "Business Agility Manifesto" recently published, individual works published by Manifesto authors that you can apply to any type of products like Arie Van Bennekum, etc.