voke defines the "Agile Dilemma" as the inherent risk and confusion created by the business desire for speed and flexibility misinterpreted as a mandate to participate in the developer-centric movement called Agile, which may not be appropriate for all organizations or projects.
voke surveyed over 200 participants from diverse technology and non technology companies about their use of Agile development and the results they experienced. The Market Snapshot report about Agile Realities presents and analyzes their responses about the use, general perceptions, challenges, and benefits of Agile.
This analysis provides organizations a context for evaluating whether or not to participate in the Agile movement, and identifying how, when, or whether or not Agile practices make sense for their organizations.
The concept of the Cost of Quality, that is, the cost of rework to remove defects, is that the later in the lifecycle a defect is identified, the more expensive it is to resolve the issue. With its shift in requirements ownership from the business to developers who will discover requirements through changes to the source code, the Agile movement is effectively pushing requirements definition to later in the lifecycle. Applying models for the cost of rework to Agile projects reveals the hidden costs of the late definition of requirements.
voke's Strategic Brief on the Cost of Rework for Agile and Non-Agile Projects provides economic models for evaluating project results and selecting the most appropriate practices.
Read Reducing the Cost of Rework, the follow up to voke's provocative rework models, with action items to reduce the cost of defects in your organization.