Why do developers at Google consider Agile development to be nonsense? (2016) (quora.com)

Article summary

The article discusses why developers at Google consider Agile development to be nonsense. However, the article's content is not available, and the discussion is based on the comments. According to the comments, Google's development process is highly flexible and adaptive, with no single prescribed methodology. The company's size and diversity of teams contribute to this approach.

Main themes

• Agile development
• Google's development process
• Flexibility in software development
• Kanban vs Scrum
• Bureaucracy in software development

What commenters say

• Google's development process is highly flexible and adaptive, with no single prescribed methodology, which may be why some developers consider Agile to be nonsense.
• Agile development can be bureaucratic and may not be suitable for all types of projects or teams.
• The Agile manifesto is flexible and aligns with Google's development principles, but its implementation, such as Scrum, may not be effective for all teams.
• Some teams at Google use Agile methods, such as Scrum, while others prefer a more flexible approach, like Kanban.
• The value of long-term thinking and planning is lost on management in many organizations, leading to a focus on short-term goals and bureaucratic processes.
• Agile development can be effective for customer-facing products, but may not be suitable for complex, low-level technical infrastructure projects.
• The distinction between 'agile' and 'Agile' development is important, with the former referring to a flexible and adaptive approach, and the latter referring to a specific methodology or framework.