Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I am leading my seventh initiative on this matter. Critical for success is to undestand that each thing you do inside the organization will impact the whole organization. The answer to your question has to be find in the framework of busines analysis. I wrote an article time ago that has been published and reference as "best practice". Is a practical process to answer your question. Perhaps it helps: http://www.projectmanagement.com/blog-post...-right-solution Saving Changes...
AKSHAY JAINPlanning Group Leader| YOKOGAWA, BahrainGwalior, Mp, India
Agile methodology is very useful where issues of project are dynamic and needs to be addressed on daily basis, specially where project is technically complex or any such situation. Agile methodology is useful where timeliness, quality and cost control is very critical and needs frequent addressing. Projects where activities are routine and do not changes very frequently traditional approach can be more effective. But I think now a days in more than 80% projects agile approach is must. Saving Changes...
Will there be many unusual features?
Who is the customer?
What are the business drivers?
Are skilled critical resources available?
Are the team members co-located? Saving Changes...
Wade HarshmanScrum Master| GDITIndianapolis, In, United States
To add to "all of the above," you must consider your corporate culture. If your organization does not value your people or trust your teams, or if it fears change and punishes failure, then it cannot be Agile.
If you try to implement any Agile framework into a bureaucratic, management-heavy organization that does NOT have an Agile culture, it will likely fail. Agile must have support from the top, or those middle-managers will disrupt your workflow and interfere with the people who are creating value.
The characteristics of your project also matter. If you know what you're trying to accomplish and have the expertise available to plan your scope, budget, and schedule, then a waterfall approach can eliminate waste by planning your project up front and eliminating costly mistakes. However, if you're uncertain exactly what you're building and need to explore, test, and adapt, then an Agile approach can eliminate waste by distributing that planning across the life of the project.
That's an over-simplification, but I hope it helps. Saving Changes...