Contents
Why are Agile approaches often preferred to the waterfall approach?
An Agile methodology is a superior choice when the client is uncertain about requirements or wants to be closely involved in the development process, and if timelines are short and they want rapid delivery. Waterfall is superior if there are complex dependencies, but Agile is preferable when dependencies are minimal.
Why is Agile approach better?
Why Should I Use Agile? Agile has become the go-to framework for helping app startups and development agencies maintain a focus on delivering a quality app ー quickly and efficiently. Agile maximizes value throughout the development process and significantly reduces the overall risk of any given project.
When is agile approach used as an excuse?
In my professional work, I keep ending up at companies where an “agile” approach is used as an excuse as to why no effort was put into an up front design; when the requirements are well understood.
Who is to blame for poor agile development practices?
Cowboys will always be cowboys, no matter what process you give them. Agile is no more to blame for poor development practices than BDUF. The problem lies with the discipline, or lack thereof, in applying the practices. The purpose of BDUF practices is to identify the direction of the project and determine risks beforehand.
Is it good to have a good agile team?
Agile is fine as long as it is working for your team. Far too many are selling it as a way to turn a bad team into a good team, and it just doesn’t work that way. You can’t take bad people and apply a process to suddenly make them useful.
What should be the effect of agile implementation?
Agile when done properly should have the effect of reining in “cowboy” technical leads and “hero” programmers. If you don’t observe this effect, that may be a sign that something important is missing from your agile implementation.