Common Misconceptions About Agile

Common Misconceptions About Agile

This IDC study, written for CIOs and VP- and director-level executives, identifies and corrects 15 of the most common misconceptions about Agile. Overcoming these misconceptions can accelerate your organization's digital transformation by leading to better choices about approaches to project delivery. While most firms recognize the need to improve agility to compete in this era of digital transformation (DX), some continue to be reluctant to use Agile for many types of projects because of its perceived higher risks and lower quality."IT leaders that fail to question their organization's long-held beliefs about Agile will find themselves lagging behind as competitors that have achieved expertise in Agile move to the next levels of agility," says Susan Martin, adjunct analyst with IDC's Research Network. "They risk hindering their organizational transformation by unnecessarily leaving entire segments of their organization behind, forfeiting the opportunity to achieve enterprise agility."

IDC Opinion
In This Study
Situation Overview
Misconceptions About Agile
Misconceptions Relating to Organizational Standards and Methodologies
Misconception 1: Agile Is a Lightweight Methodology or Process That Lacks Important Steps for Many Types of Projects
Misconception 2: Agile Has No Standards, Resulting in Lower Quality
Misconception 3: User Stories Are the Only Type of Documentation Allowed When Using Agile
Misconception 4: Agile Discourages Planning, Making It Impossible to Report Status
Misconceptions Relating to Project Characteristics
Misconception 5: Agile Cannot Be Used for Large Projects
Misconception 6: Agile Cannot Be Used for Applications with Multiple Interfaces to Other Systems
Misconception 7: Agile Cannot Succeed Unless Development Team and Product Owner Are Colocated
Misconception 8: Projects Utilizing Outside Vendors Cannot Succeed with Agile
Misconceptions Relating to Project Constraints
Misconception 9: Agile Is Only Appropriate for Projects Facing High Uncertainty Such as When Scope Is Ill-Defined or Expected to Change or When Budget or Schedule Is Flexible
Misconception 10: Agile Is Useful Only Where Speed Is Important or Fast Time to Market Is Required
Misconception 11: Agile Achieves Speed by Sacrificing Quality
Misconceptions Relating to Application Type
Misconception 12: Agile Is Not Appropriate for Regulatory or Compliance Projects
Misconception 13: Agile Is Appropriate for Systems of Engagement But Not for Systems of Record
Misconception 14: Agile Cannot Be Utilized for Legacy Applications, Especially Those Built on Older Technologies
Misconception 15 Agile Is Only for IT
Future Outlook
Essential Guidance
Learn More
Related Research

Download our eBook: How to Succeed Using Market Research

Learn how to effectively navigate the market research process to help guide your organization on the journey to success.

Download eBook