Common Agile Product Development Myths

Abstract:

Agile began as an iterative, collaborative, value-driven approach to developing software. It was originally conceived as a framework to help structure work on complex projects with dynamic, unpredictable characteristics. But since then, it has evolved into somewhat of a philosophy or world view, with a set of well-articulated values and principles common between Agile’s many varieties. But we have noticed that many times people are misinterpreting some concepts in Agile.

 

Key Takeaways:

  1. Myth #1: Isn’t Agile Just for Software Development?
  2. Myth #2: Can’t stakeholders introduce change whenever they want?
  3. Myth #3: Doesn’t everyone need to be a generalist on an Agile team?
  4. Myth #4: I’ve heard that Agile teams don’t (or can’t) plan.
  5. Myth #5: Don’t Agile teams create products with no architectural plan?