the disadvantage list is actually much longer.
essentially, `agile software dev' methodologies are apt to guide to focus on lack-foresight work and to result in low quality software in the long run---design-insufficient and occasional-solution-full products.
of course, that may be accused to bad practice of experienceless teams. are there experienced teams that really embrace `agile software dev'?
in real world, the primary `advantage' of `agile software dev' methodologies is convenient for `micro-management', which is mainly employed by a business expecting lowcost-running---hiring untalented coding monkeys to fill product managers' backlog lists. software developers' proactivity is suppressed much, as is inconsistent with true software development, which essentially is `craft'.
You can solve the problem of low software quality via your non functional requirements and setting quality requirements in your team.
When you combine your User Stories with your non functional requierements, the team assures that the software that is beeing build keeps its standarts of quality.
"in real world, the primary
advantage' ofagile software dev' methodologies is convenient for `micro-management', which is mainly employed by a business expecting lowcost-running"Absolutely not. In a agile environment you are avoiding micromanagement by letting the team manage itself. It is responsible for the endproduct and its quality.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit